I received a referral from a friend for a Software Engineering position on the client platform team (front-end).
I had an initial call with the engineering director, where he mostly explained the company's structure and its business.
I believe that due to my past experience and the referral, I was invited for an onsite interview directly after that call. I scheduled it a month later to allow for adequate preparation.
The onsite experience was pretty great overall. I had four hour-long interviews and a lunch with the engineering director for the team I was interviewing for.
The interviewers were all super nice. They definitely did not try to ask trick questions or anything unreasonable. All of the questions they asked covered important JavaScript concepts. I recommend reading a couple of JavaScript books before interviewing for front-end positions; it helped me a lot.
Consequently, I was able to solve the problems in each interview and had time to ask the interviewers questions about themselves and the company.
Overall, the conversation went really well. Definitely be yourself during those conversations. Tell them about your passions and your ultimate career goals.
I can't talk about specific questions because of the NDA. But as I said, read JavaScript books. "JavaScript: The Good Parts" is a good start.
Concepts like closure, scopes, and callback functions will be tested in any front-end interviews.
The following metrics were computed from 93 interview experiences for the Splunk Software Engineer role in United States.
Splunk's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Splunk's Software Engineer interview process in United States.