Call from recruiter, covering the basics of the job and my current responsibilities.
Two calls with SREs in London. No technical questions were asked; they focused on my background, my current role, and any questions I had about the position.
On-site interview in San Francisco. The company covered the hotel and flight, and I expensed meals, which was appreciated. There was a miscommunication regarding the interview date, but HR managed to resolve it. I spoke with seven individuals, including engineers, product managers, a manager, and a director. Everyone was friendly and answered all my questions. No technical questions were asked, though this might have been due to the unexpected date shift. The interview primarily consisted of behavioral and situational questions. The office was very nice and had a pleasant atmosphere.
After the on-site interview, I received positive feedback from my recruiter. There were essentially three possible outcomes: an offer, a no-offer, or further interviews. My recruiter informed me that additional interviews were necessary, leading to a month-long wait. I received another offer during this time, and they finally communicated that they were re-evaluating positions and had another role available for me. As I did not wish to endure a further waiting period, I ultimately declined their offer.
Overall, it was a positive experience, but I wish the decision-making process had been more efficient, avoiding the month-long wait.
A customer calls you and says they cannot reach a webpage.
How would you go about troubleshooting the problem with the customer?
The following metrics were computed from 1 interview experience for the Splunk Site Reliability Engineer role in San Francisco, California.
Splunk's interview process for their Site Reliability Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Splunk's Site Reliability Engineer interview process in San Francisco, California.