Form3 Software Engineer Interview Questions
& Process

I first had a chat with a Form3 recruiter, which was pretty chill and they gave me good feedback later on. Then, I got a technical assignment which was well set up in a Github repo – just had to follow the instructions and code my solution. After that, there were three technical interviews: first, a review of the assignment, then a network-focused interview, and finally, an on-call simulation. The assignment review was pretty easy and the interviewer was super nice. The network one was a bit of a drag; I had to wait and then answer a bunch of exam-like questions about networks and CS. The last one involved a hypothetical scenario where I had to debug a given system in under 10 minutes, along with some behavioral and cultural questions. It wasn't the best experience, especially the debugging part. I got feedback a few days later and then a call with the recruiter with more details. Overall, the process was smooth thanks to the recruiter, but honestly, some interviewers didn't seem prepared or respect my time.

It was a really well-organized interview process. First, a recruiter call, then an offline coding task, and finally three 30-minute interviews with the engineering team, all within a 1.5-hour block. They're pretty open about technology, so even if you're not a Go expert, they're fine as long as you know OOP. It was a friendly, low-stress vibe. They even encouraged me to learn Go at my own pace before the coding exercise and kept in touch to check my interest without being pushy. The coding exercise was relevant, asking me to build an http client library for their payment API. The engineering interviews let me learn about their architecture, design a distributed system, and even debug a simulated production issue like a game. They gave feedback pretty quickly too, within 48 hours.

The interview process was pretty standard: first, a recruiter call, then a technical test where I had to write a client library with no time limit. After that, there was a 90-minute triple header interview. The triple header was the most interesting part, consisting of three 30-minute interviews with different interviewers. The first part covered the company's value proposition, a system design overview, and questions about my coding test implementation choices. The second part focused on my suitability for the role, asking general tech questions like explaining TCP/IP and HTTP, and we discussed the pros and cons of remote work. It also included questions about my experience with cloud computing, IaC, and messaging systems. The final stage was quite surprising: a role-playing exercise to debug an issue. I initially thought I'd have to read logs and fix code without domain knowledge, but it was more relaxed. The interviewer acted as the system, and I asked questions about system metrics or logs based on a system diagram. We then discussed CI/CD implementation for my code submission, and I think my questions came next. Overall, it was a fast and smooth process with great interviewers, avoiding silly algorithm or domain-heavy questions. The debugging role-play was the trickiest part, as I had to rephrase my general checklist into specific queries to the logs/metrics.