No work-life balance for engineers
No work-life balance for engineers
- Kitchen fully stocked.
- Office is beautiful, and the location is great.
- Product is awesome.
- Stock options are valuable.
• No work-life balance for engineers (management pushes you while saying “you set your own boundaries”) • Office politics • Health insurance is terrible • No 401k match
Mean what you say and be transparent
Was this helpful?
Splunk Interview Questions
Splunk Interview Experiences
Software Engineer
The interview process is pretty straightforward, with three rounds scheduled by HR: * Two rounds of technical questions with a software engineer. * One round with the hiring manager. Most people are friendly and professional. However, the HR de
Software Engineer
45-minute technical interview with a member on the team (LeetCode medium). 45-minute systems design question with a different team member (design Facebook Messenger). CoderPad and shared screen were used, respectively.
Software Engineer
The interview process takes about 3 weeks. It consisted of 3 rounds: back-to-back interviews. Two of these were technical, and the other was behavioral. The first two technical questions were average, focusing on optimization and edge cases.
Software Engineer
San Francisco, California, United StatesAugust 24, 2024The interview process is pretty straightforward, with three rounds scheduled by HR: * Two rounds of technical questions with a software engineer. * One round with the hiring manager. Most people are friendly and professional. However, the HR de
Software Engineer
San Francisco, California, United StatesOctober 14, 202345-minute technical interview with a member on the team (LeetCode medium). 45-minute systems design question with a different team member (design Facebook Messenger). CoderPad and shared screen were used, respectively.
Software Engineer
San Francisco, California, United StatesJanuary 1, 2022The interview process takes about 3 weeks. It consisted of 3 rounds: back-to-back interviews. Two of these were technical, and the other was behavioral. The first two technical questions were average, focusing on optimization and edge cases.
