Constructor Javascript Developer Interview Questions
& Process

There were 7 interviews total, which included 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. The stages were: 1. Engineering Manager: Introductory chat about general JavaScript knowledge and architectural decisions. 2. Code Pairing #1: Two parts - first, scraping an HTML file to get product IDs and counts. Second, using a simple Node.js app to send data from a CSV file to Constructor’s API. 3. Customer Success: Questions about interacting with non-technical stakeholders and clients. More behavioral than technical. 4. Code Pairing #2: Build and manage a deck of cards. Follow-up questions about improvements and handling situations like API state and concurrency. 5. Engineering Best Practices: Situational questions on architecture, caching, cookies vs. localStorage, and bot detection. 6. Product Interview: This was the least engaging part. Interviewers didn’t try to build 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. It was completed quickly, so I was asked to improve it. An error occurred in the final minutes, but the interviewer acknowledged it wasn't critical and likely just a typo. After a demanding process and multiple hours, I got a generic rejection email three business days later, with no feedback. I understand not everyone moves forward, but after so many interviews, I would have appreciated 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, but only got a generic rejection with no feedback, which is frustrating after investing so much time. The interviewers were nice, respected my time, and seemed professional. But the whole process felt very rigid and scripted, lacking any real conversation or human touch, making it hard to connect. The technical challenges in the virtual onsite didn’t feel like they matched the actual job duties. They seemed like general assessments rather than tasks reflecting daily work. Plus, the interviewers were totally silent during these exercises. It made things awkward, not collaborative or like pair programming, felt cold and too much like an evaluation. It’s obvious the team is focused on a structured process, but they’ve lost the human element that’s important for checking if it’s a good fit for both sides.

I had two interviews for the Javascript Engineer role. The first was a screening interview where we discussed the company, the role, and my background. The second interview was a one-hour pair programming session with two engineers. They gave me a coding task to complete within a time limit, allowing me to use Google for syntax and ask questions. After the task, we discussed my solution approach and if I'd change anything. Both interviews included time for my questions. The whole process was well-organized, and the interviewers were friendly and supportive, guiding me through and offering help when I needed it.