Phone screen from hiring manager was about past projects and about some hi-level nosql concepts.
1:1 interviews with 5 people. One was at director level about projects/experience and some big data questions regarding uniqueness.
The 2nd interviewer was an engineer who had a prepared list of java questions. You can find these questions on any java interview preparation site. I got the feeling that at times the interviewer himself did not know what he was asking.
The 3rd interviewer started off by asking formatting questions ( printf ) in C!
He then wanted a non-recursive fibonacci implementation in exactly 4 lines and felt that the question was quite clear and needed no discussion. So he left the room for 10 minutes.
When he came back his version of the solution used one less variable.
He then followed these questions up with some string manipulation questions and linked list questions.
The 4th interviewer was an architect and this conversation was the most mature and meaningful of all the interviews I had that day. Questions were around scaling a website, design patterns, building APIs,etc.
The last interview was with the hiring manager ( whom i had talked to before ). He gave me some vague talk about how they perceived every team member as a leader in his own right.
After all the interviews I got the distinct impression that they were looking for someone with fixed/narrow skills and wanted specific answers to questions. The 2 interviews with the developers were very eye-opening and I was left with the impression that their interviewing skills were too immature/untrained. I also came away feeling there was no career path here and it was every man for himself.
Perguntas de entrevista [1]
Pergunta 1
The era of asking printf format specifications has long passed. Any half-competent programmer will figure out these tricks by repeated use of the compiler. I don't understand what is to be gained by asking these kinds of questions. Also having more lines of code for fibonacci does not matter much due to compiler optimizations ( unless of course you are building embedded systems and such ).
You cannot have questions like these being asked when the position description asks for 8+ years of development experience. At the end of the day, I felt I had wasted time by applying for this position.
Applied through referral after initially applying on the careers page. The process started with a recruiter screen discussing my background, tech stack, and role expectations. This was followed by a 1-hour phone screen with coding questions using the Glider platform. The onsite loop was around 6 hours and included a backend hands-on exercise, system design discussions, and deep dives into my solution and past experience. Recruiter communication was clear and timely throughout the process.
Perguntas de entrevista [1]
Pergunta 1
Coding questions (easy to medium difficulty)
Matrix-based path finding problem
String / hashing problem (similar to Unique Email Addresses)
Backend API design using a CSV dataset
Questions on scalability, system design, and design trade-offs
Discussion around past projects and engineering decisions
Fiz uma entrevista na empresa Intuit (New York, NY).
Entrevista
Online technical coding sessions followed by three different interviews ranging from technical questions, behavioral questions. I had to pass the online technical session first before going to the next round.
Perguntas de entrevista [1]
Pergunta 1
AI experience such as the difference between classification versus LLM
Candidatei-me pessoalmente. Fiz uma entrevista na empresa Intuit (Bengaluru).
Entrevista
screen, could include dsa, technical for an hour
craft round which includes a craft given, and a working applicaiton to be built around ahead of the interview. Then the panel questions on the same during the craft round. Followed by Technical round which includes dsa or lld or hld. behavioural with Hiring manager