Interview Process: There were 7 interviews in total, covering a mix of live coding, engineering best practices, and cross-functional interviews with teams like Customer Success and Product. The process moved quickly between each step, and communication from recruiting was clear and timely — up until the very end. 1. Engineering Manager: Introductory conversation covering topics like general JavaScript knowledge and architectural decisions. 2. Code Pairing #1: Two parts — first, scraping an HTML file to retrieve product IDs and count. Second, use a simple Node.js app to send data from a CSV file to Constructor’s API. 3. Customer Success: Questions about how you interact with non-technical stakeholders and real clients. More behavioral than technical. 4. Code Pairing #2: Build and manage a deck of cards. Questions followed about improvements and handling scenarios like API-based state and concurrency. 5. Engineering Best Practices: Situational questions on architecture, caching, cookies vs. localStorage, and bot detection techniques. 6. Product Interview: This was the least engaging part of the process. Interviewers didn’t take time to create a rapport, questions were vague and felt poorly structured. The experience felt rushed and unclear. 7. Code Pairing #3: Transform a simple React app into a tabbed interface. Completed it quickly, so I was asked to improve it. An error occurred in the final minutes, but the interviewer acknowledged it was not critical and likely just a typo. Final Thoughts: After a very demanding process and multiple hours dedicated to this opportunity, I received a generic rejection email three business days later, with no feedback whatsoever. I understand not every candidate moves forward, but after so many interviews, I would have appreciated at least a sentence or two about what didn’t align — especially after investing this much time and energy. It felt disrespectful and disappointing to be left with zero insights on what could be improved. If you're applying here, be prepared for a long and thorough process — but also be aware that you may get no feedback, no matter how far you go.

I went through 7 interviews, only to receive a generic rejection with no feedback, which I find unacceptable after such a time investment. Overall, the interviewers were polite, respectful of time, and came across as professional. However, the process felt very rigid and overly scripted, it lacked any natural flow or human connection, which made it difficult to build real rapport. The technical challenges during the virtual onsite didn’t seem closely related to the actual responsibilities of the role. They felt more like generic assessments rather than tasks that would reflect day-to-day work. Also, during these exercises, the interviewers remained completely silent. This created an uncomfortable atmosphere, rather than a collaborative or pair-programming-like environment, it felt cold and overly evaluative. It’s clear that the team is trying to follow a structured process, but in doing so, they’ve lost a sense of human interaction that’s key to evaluating mutual fit.