I applied through a recruiter. The process took 1 day.
The recruiter reached out to me over LinkedIn. The first interview was just a technical screening round about my current project, a problem-solving question, and the general questions on how the internet works. The interviewer had no idea about the role he was interviewing me for, which is a RED FLAG for me.
I'm working at a very large organization with 4.6K employees comprising of at least 20-30 engineering teams. And the interviewer grilled me over why all the teams don't work with the same technology, design conventions.
To me, this sounds like a pretty baseless question as anyone as an individual cannot really answer on the behalf of other teams. The interviewer had NO KNOWLEDGE of GraphQL and kept asking me why do I not use SQL instead of GraphQL.
I got tired of explaining to him that both technologies have different use cases and have NO COMPARISON! Even though if I do clear this interview, I might not proceed with a 2nd one as I had a pretty frustrating experience with the 1st one alone.
• Questions about the current project • Difference between GraphQL and SQL • How is scalability handled at my organization • How does the internet work when I enter a URL • Explain a time I handled a critical production issue • Add two 100 digit numbers in an environment that supports numbers up to only 10 digits
The following metrics were computed from 11 interview experiences for the BrowserStack Senior Software Engineer role in Mumbai, Maharashtra.
BrowserStack's interview process for their Senior Software Engineer roles in Mumbai, Maharashtra is very selective, failing most engineers who go through it.
Candidates reported having good feelings for BrowserStack's Senior Software Engineer interview process in Mumbai, Maharashtra.