Terrible and unprofessional experience. The recruiter is so lame; he emails with an "ABC job position" in the title, but the email description says a completely unrelated "XYZ position."
He reached out and then disappeared forever, even after I sent multiple follow-up emails. I finally received a response only after someone in management, who I had directly emailed, intervened.
TERRIBLE, TERRIBLE, TERRIBLE recruiter!
Then, after an internal contact followed up, I was scheduled for a phone interview. The interviewer was so passive-aggressive. He mentioned he wanted to see my approach to a programming problem. I derived a working solution, but he stated it was "only to see how I approach it" – WRONG! They want coding monkeys who have memorized or slogged through coding questions not related to Test Automation Roles.
He hardly touched upon the numerous technologies mentioned as requirements in the job requisition. I had pretty good hands-on experience and understanding of most of them.
Again, the recruiter did not communicate for weeks after the interviewer mentioned, "See you soon!"
Once again, I had to ping an ex-coworker now at Splunk to follow up, only to find out the "feedback was not positive."
A bunch of time-wasters and a "mafia" who only want to sneak in their referrals.
Unless you have a strong referral from inside, DON'T BOTHER trying. The recruiter won't reply, nor will they give you a fair chance.
Count the occurrence of a character in a nested object. This object could be a mix of lists, dictionaries, strings, etc.
The following metrics were computed from 1 interview experience for the Splunk Principal Software Engineer In Test role in United States.
Splunk's interview process for their Principal Software Engineer In Test roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Splunk's Principal Software Engineer In Test interview process in United States.