First you'll get a recruiter screen that is pretty vanilla. Then they tell you that it's a five-round process 1. You'll have a coding interview with another engineer (they may have another engineer shadow as well). They'll ask you something akin to a "leetcode medium", but really it's just to build a program from scratch that doesn't have much to do with their work in mental health (mine was to build Conway's Game of Life). Weirdly enough, you need to have your OWN development environment (they don't coderpad you). You also cannot you any AI tools (so no github copilot), which is also weird since every developer uses them these days. The engineer did not say much during this process, and you only get 5-10 minutes at the end to talk to the engineer (which means you don't actually get any info out of them) 2. Technical Architecture comes next, which is just a system design. In this interview, you will be assembling and integrating various components of technology to construct a functional system, with the ultimate aim of resolving a specific issue. Also weirdly enough, you have to use your OWN whiteboarding software (I recommend Google Jam) Tip: they expect you to be extremely extremely thurough with what you design. Leave no stone unturned. 3. For some reason, there is a SECOND coding interview, because apparently the first one is not enough. Same rules apply 4. A "reverse system design", where you are basically a storyteller for a project you worked on. This honestly should seem like an experience talk, but to be fair they way they have it set up is to just be a good salesman for a project you worked on. Same rules apply as the system design, where they expect extremely extremely detailed responses to everything you ever did. Honestly write notes on one screen and read off of that as you talk to the other engineer. 5. A meeting with a hiring manager (not necessarily YOUR hiring manager). Mostly a culture fit interview. In all honesty it ended up being a place that didn't know how to interview