The soft skills and architecture rounds were solid - fair questions, professional interviewers, real conversations. The two architecture sessions covered a web crawler (~1M users/day) and a survey sending system (~5k users/day) - relatively modest scale, nothing too exotic. The coding round was a different story. The interviewer was adversarial from the start, repeatedly stopping me mid-implementation to question whether I actually understood what I was writing. When I approached the optimal solution directly - based on patterns from their own prep materials - it was treated as suspicious rather than as preparation paying off. The constant interruptions made it impossible to get any flow, and the whole thing felt less like a skills assessment and more like an interrogation. The process is well structured overall, but the coding round experience seems to depend heavily on who you get.

Its 4 stage process - screening, coding and two system design interviews. Screening is mostly to check if you fit the company values and if you have required work experience for the role - I did not have any specific technical questions but this may depend on candidate. Lots of questions where STAR technique is expected to be used - how you dealt with technical challenge, with conflict etc. focus on individual qualities and not teamwork effort - interview is about you and not other people. Coding is two problems two solve, first harder, second easier - the problems are typical medium to hard leetcode problems but usually with extra steps and long detailed descriptions which makes it harder to decompose problem to known patterns. Expect something non trivial like dynamic programming for first problem. System design is like any other system design - they seem to put focus on overall scalability and database design but that is just my impression based on failed attempt. There is only 1h for it but it is expected to cover a lot during that 1h so dont try to spend too much time in requirements part or basic design choices because that wont give them enough input from your side to give you a good grade. The interview process is tough but expectations are very clear, lot can be learned even when failed. Got very good extensive feedback after interview.

Extremely large process and old decade process: First you will be interviewed online by an HR recruiter in mexico to check your background and check if you are able to speak in English, then you will move to a manager call to see if you are a fit with their values "TACOS" is the acronym of those, then if you are a fit, you may guess, "oh I finished" or "there is only 1 coding interview left" but no, you will be invited to take the rest of the process "on site", yes, you are reading right, on site in their mexico offices, then you may guess, "well, maybe I will get a tech interview here and then a manager interview again and then i will get an offer", Is not working like that, you will get 4 "1:1" interviews in a row, 2 of them will be coding interviews (so you will need you laptop) and 2 software architecture interviews, each interview will be 45 mins each and then you will move to another one and so on without any kind of break or feedback. then after you complete all the interviews, they will invite you to exit the building with the promise of hearing their feedback soon, a week later I got a rejection email without any extra comments about their decision. Waste of time, it will be so much easier to take this in remote mode, thank God I was in others processes... My process lasted 1 month.