Gorgias (CA) Interview Questions
& Process

I got applied through a headhunter. There were clear, understandable milestones that I had to pass: screening, interview with the Hiring Manager, Tech Design, Live-coding, and the final with the CTO. I passed all of them except the CTO step. The interviewers on the first steps were friendly and polite, well-prepared, and skilled. The hiring manager interview was pretty common but still left a good impression. Tech design was also a common high-load system design, but it had some interesting questions. Many disappointments came with the live-coding step. They sent me a zip file with the project and asked me to check and run it. The codebase was extremely outdated, and the task looked very dull. I came to the interview, and the interviewers, instead of introducing themselves, started defining my Tech Design task. I stopped them and said that it had to be live coding. That was unexpected, and instead of preparing a project, they sent me a new task, which is ok, but why did I spend time on the zip archive? The task was also very boring, but nothing difficult, any Junior can pass that step. After that, the recruiter asked about my experience, and I provided an honest opinion. I guess that was my mistake that ended my interview process. I was declined due to lack of collaboration and adaptability; how they evaluated that in live coding only God knows. The interview process was good until it faced low-qualified people, which ruined the overall experience.

The process starts with a recruiter screening, then an interview with the hiring manager. After that, I had to submit a case study, followed by a mock discovery call/demo on Gorgias. Then there was a group interview, a leadership interview, and finally, the offer. They ask straightforward questions related to the role, but they really expect you to know the product well and speak about it with confidence during the interviews, which isn't the norm for other companies. I thought showing my sales skills would be enough, and that it would be okay not to know the product deeply during the mock demo/discovery call, but I was mistaken. This is the only place I’ve interviewed where they seemed so focused on product knowledge, which was a surprise because most companies care more about the skills you bring and assume product knowledge will be learned on the job. The instructions were also confusing because they asked for a mock demo but then said in the description that there were only 20 minutes for discovery. A discovery call and a demo are different, and they didn't provide a sandbox to actually demonstrate the product, so the unclear instructions could be an issue. It would be best to clarify what they want beforehand. If I had received an offer, I would have been hesitant to accept because they were so fixated on product knowledge for a product I haven't been hired to sell yet. It makes you wonder if the product training on the job might not be great.

I got referred by an existing employee and had a quick screening call with a Team Lead, which was pretty relaxed. After that, I got a case study to work on for 5 days, which I had to present in the next interview using Google Slides. The case study had 3 parts, but I only got to present the first two during the interview due to time limits. They used the rest of the time to ask about my experience. They didn't ask about the third part of the case study, which was a bit confusing and frustrating since I put a lot of time into it. A few days later, I got an email saying they decided to go in a different direction, with no further details. I asked for feedback to help with my job search, but never heard back.

The interview had 4 steps. It started with an HR call, then an online coding challenge. After that, there was a live coding session with a manager and other engineers. Finally, there was a CEO interview. I didn't pass the third step, even though the coding part seemed okay, but also a bit strange. They asked me to add a fully working feature to an existing project in under 30 minutes. However, their evaluation criteria were different. The feedback after my rejection indicated they were looking for a specific tier of engineer, and my profile was one tier below what they needed. Despite the outcome, the process was friendly. Knowing more about their specific selection criteria would be helpful.