This is from an interview I had two months ago.
The first two technical rounds were each 1 hour, with 2 interviewers per round, and both interviewers asked questions.
Each round had one question, both original LeetCode Easy problems — one was checking whether two trees are the same, the other was valid parentheses. Then you had to write test cases.
Probably because I was using Java, the interviewer knew it really well. They asked a lot of Java-related follow-ups — things like rewriting the code based on new requirements, how to handle a large amount of data, and knowledge related to collections, generics, exceptions, etc., along with rewriting the code accordingly.
I heard that candidates using other languages got 2 questions per round.
After passing the first two rounds, you'd move on to the third round.
The third round was 1 hour, with the same two interviewers from the first round. They called it a BQ interview, but actually 80% of it was verbal technical questioning — the interviewers kept probing on technical points, since after all it was technical interviewers doing the BQ round. Both interviewers asked questions.
Questions like:
- New skills I've learned
- Conflicts from working within a team
- How did I integrate the frontend and backend APIs in my past projects?
- How was the team divided up? How did you collaborate?
- How did I debug to pinpoint where a bug was?
- Do I use AI tools?
- Do I read documentation regularly?
- Did my projects have tests written?
- Was there documentation written?
- Reason for switching careers?
I prepared for the BQ round in the traditional way, and I failed at the third round.
Discussion
Loading comments…