I applied through an employee referral. I interviewed at Riverside.FM
Interview
I interviewed for a Customer Success Manager (SMB) role and had a really smooth experience from start to finish! The process had 5 rounds over the span of a week.
1. Initial recruiter screen
2. Hiring manager interview
3. Demo/presentation round with the hiring manager and Director of CS
4. HR conversation
5. Final interview with the VP of Customer Success
Communication throughout was fast, clear, and consistent. I never had to chase anyone for updates, which isn't always the case in interview processes. The recruiting team was organized and made sure I knew what to expect at each stage, which took a lot of the usual interview anxiety out of the equation. Every interviewer was genuinely engaged and asked thoughtful questions that made me feel heard. Overall, it felt like a company that respects candidates' time and takes hiring seriously. Would recommend!
Interview questions [1]
Question 1
- Why do you want to work at Riverside?
- Walk me through your background and experience in Customer Success
- Behavioural questions focused on organization, process, approaching customers, and how I manage day-to-day workflows
I applied online. I interviewed at Riverside.FM in Jun 2026
Interview
The interview followed a live coding format — 45 minutes of coding followed by a review with the interviewer. The live coding portion started with a challenge to build a simplified version of the Jest testing framework from scratch. I had to implement the it, expect, and toEquals functions, making sure that failed assertions would throw an error containing the test name along with a reason for the failure. The interviewer then asked me to extend the implementation to support asynchronous tests using a done callback pattern, with the additional requirement that the test should automatically fail if the done callback was not invoked within 5 seconds. After the coding portion, the conversation shifted to questions based on my CV. The interviewer was particularly interested in my experience with data management approaches, asking me to compare Context API and Zustand — when I would choose one over the other and what trade-offs I considered in past projects. They also asked about my experience with WebSockets, digging into projects where I had used real-time communication and how I handled challenges like reconnection, state synchronization, and scaling. We then discussed frontend performance optimization strategies, including patterns around memoization, rendering, and code splitting that I had applied in production. They also asked about the AI assistants and tools I use in my daily workflow — what my practices are, how I integrate them into development, and how they have changed my productivity. Toward the end, they dug into my career trajectory, asking about the biggest technical challenges I had faced, how I approach architectural decisions, and the reasoning behind some of the shorter tenures on my resume. The tone throughout was conversational and collaborative rather than interrogative.
Interview questions [1]
Question 1
Build a simplified version of the Jest testing framework from scratch — implement the it, expect, and toEquals functions with proper error messages containing the test name. Then extend it to support asynchronous tests using a done callback pattern with a 5-second timeout.
I applied through a recruiter. I interviewed at Riverside.FM (Tel Aviv) in Jun 2026
Interview
Had a 30 minutes call with the Group Leader
Got in for a 90 minutes interview with the Team Leader.
Good experience overall, getting there and going through the interview was fairly easy and the process felt good.
Interview questions [1]
Question 1
* Scenario
* A user logs in to their page and look at videos list
* The user picks a video, and chooses to make a clip out of it with some properties
* The clip itself would be processed for a few minutes, then appear in the "Clips" page
* Question:
* How the structure the backend of a system like that should look like?