I went through a structured, pretty fast process that felt organized from the start. First I filled out their forms and answered basic details about my background and communication style. Then I had a recruiter interview where we talked about my recent projects, what motivated me to apply, and how I collaborate in remote teams.
After that, the technical portion came in clearly defined stages: an online code challenge followed by a technical interview. The take-home/assessment work varied in length depending on the piece, but it was definitely time-boxed and focused on practical engineering tasks. In my case, I had more than one technical assessment, including one that took several hours and came with a deadline that felt tight, especially because it wasn’t really clear what would happen next. After I finished everything, the technical interview wrapped up in about an hour, and I left feeling like they genuinely understood what I’d done.
> 1 year
Average Positive New York, NY
My first step was a recruiter conversation about plans and expectations, and I ran into technical hiccups during the call, so they promptly rescheduled and kept things moving the next week. After that, I took a short online test covering JavaScript, AWS, and general web architecture. The next piece was a conversation with a developer where we discussed my results.
Once the interviews were done, I received an offer and there was a negotiation phase around compensation and start date. The process itself felt fast and direct—especially compared to longer cycles I had experienced elsewhere. I also liked that the recruiter kept communication moving and didn’t make everything feel unnecessarily complicated.
> 1 year
Average Negative São Paulo, São Paulo
My process was pretty compact but clearly technical. I went through two interviews and then a technical test that was both fast and straightforward, f…
Unlock every Backend Engineer interview experience
