commercetools Interview Questions
& Process

This was a total waste of time and effort, beware! It involved seven interviews, including two C-suite conversations and two in-person meetings. I also built a full talent strategy and case study on my own time. Just when I thought an offer was coming, I got an email saying they weren't ready and needed to 'get things in order first.' After all that effort, their decision came via email, with no follow-up call or accountability, and zero regard for what they asked of me. This isn't just a hiring mistake, this is who they are. Seeing how disorganized they are from the outside during the interview process makes me wonder what it's like internally. They've had three CEOs in two years and reports of layoffs suggest a lack of strategy. These aren't just growing pains, they're signs of an organization with zero accountability. They took real strategic work and my proprietary thinking without compensation and ended the process by email. I had to formally request in writing that my work remain confidential. The fact that I even had to ask says it all. Bottom line, if you're a high-caliber candidate who values your time and expertise, this process will make you feel like neither matters. And if it's this broken from the outside, save yourself. I know I dodged a bullet, and you can too.

The overall interview experience was a waste of time. It started with a 60-minute phone call with the Talent Acquisition Partner, who was fantastic. This was followed by a 60-minute technical interview with a Senior Architect and a Senior Frontend Developer. During this second stage, I encountered two very hostile interviewers. We discussed my professional background and accomplishments. The interview then shifted to numerous technical questions about React, code bundling, transpilation, and APIs, which felt like an interrogation. Some questions were vague, like 'How would you build a React app' and 'How would you convert JavaScript to TypeScript?', with little to no feedback provided. When I asked if they were satisfied with my answers at the end, the response was just 'yes'. Despite answering all technical questions successfully, it seemed the Senior Frontend Developer felt threatened, while the Senior Architect seemed enthusiastic. I was rejected via email the next day, with the reason given being that my answers weren't in-depth enough.

Started with a recruiter call that was chill and went over the company and job. Then had a competence-based interview, though the interviewer seemed unprepared, just reading questions and trying to rush through them. It wasn't too bad though. The third interview was about collaboration with 3 interviewers, felt like a lot of people. Some questions were a bit too technical for a designer role. That was the last interview. They told me I didn't pass, and I asked for feedback but got no response, which felt disrespectful and like a waste of time since I don't know what to improve.

First off, there's a screening with HR to see if you're a good fit generally. Then, you'll chat with the team you might be joining about technical stuff. After that, there's a round to make sure you vibe with the company culture. Finally, you'll talk to people from other teams to check out your broader technical skills and how you work across departments.