Overall, it was pretty great; the interviewers will help you whenever you get stuck, as they want you to answer rather than make you feel lost.
The emphasis was on AWS and how every service connects with each other. Expect the interviewer to go in-depth with any service you've used the most, for me it was EKS.
I applied online. The process took 4 weeks. I interviewed at Typewise in Dec 2024
Interview
The process was chaotic, and they seemed clueless about what they wanted. In the first round, if you're selected, they send you a TestGorilla assessment with a 1.5-hour DevOps(AWS, Containers, Automation), Python, and critical thinking test. I passed and moved to another 30-minute quick tech interview with a DevOps guy who joined late. He asked basic questions like CIDR ranges, which made no sense since I already answered such questions in the first round.
The "technical round" came next, with a DevOps guy and a Python engineer. The Python questions were reasonable, but the DevOps guy started with AWS-related questions already covered in TestGorilla. When I mentioned having high-level knowledge of DynamoDB, he drilled deeper into it. We wrapped up with a system design question which I probably didn't answered that well.
Honestly, I considered quitting after the second round but stayed out of curiosity. In my five years of experience of doing and conducting interviews are usually about understanding candidates skills, not scoring points.
I mean they've been looking for a DevOps engineer for six months now.
This whole experience reflects poorly on their organizational structure and competence, not to mention the time they scheduled an interview while the guy was on vacation, and no one else showed up.
Unsurprisingly, I didn’t hear back after the final step.
I applied through university. The process took 2 weeks. I interviewed at Typewise (Zurich, NY) in Mar 2022
Interview
Leetcode interview with two challenges to be solved plus technical questions. The coding part had a duration of around 40 minutes. Easy and medium question levels. For the medium, a discussion of the implementation also took place.
