Kymeta Interview Questions
& Process

The interview process at Kymeta involved an initial HR chat, followed by two technical phone calls, and then an onsite interview. After that, there was a final chat about what could happen next, which felt like it might lead to an offer, but it ended up being a rejection. They took two weeks after the interviews to let me know via a Team call that I didn't get the job. It felt more like they were just evaluating me extensively rather than really intending to hire.

The interview process started with a phone screening with the recruiter, followed by a call with a colleague. Next, I had to give a demonstration to a group of peers, some of whom would be interviewing me. The final stage involved four in-person interviews with the hiring manager, Max (the PM I'd be working with), Crystal, Makhala, and Amy. It was inspiring to interact with such talented individuals at Kymeta. Max's questions were very job-focused and detailed. Crystal focused on cultural fit and offered advice for the initial days. Makhala, with her extensive experience, was a great source of information. Amy, the hiring manager, was direct and no-nonsense, creating a comfortable environment for open communication.

So, there were like 3 steps in the interview process. First, I had a 1-hour chat with the tech lead, then an interview with HR, and finally, a long 5-hour one-on-one with the whole team. What was kinda unexpected was a 30-minute power point presentation where I had to talk about my accomplishments, which I thought could be tough for programmers since they might be shy or not great at public speaking. The team itself seemed really cool, and I'd suggest it to folks who like that close-knit, start-up vibe. The main person interviewing me was honestly one of the best I've ever met; super thorough and asked really on-point questions. Overall, great people and a solid process!

The interview had 4 rounds, mixing technical and behavioral questions. It started with a PowerPoint presentation for introductions. The technical parts were fine, though there was an instance where an engineer insisted on an incorrect solution, making me wonder if it was a test of how I'd handle disagreement, but he just seemed stubborn. The team seemed to have significant organizational issues. Despite that, the people were nice. The role has been open for about 6 months.