The interview process included a take-home assignment. After submitting it, a phone interview was scheduled, which would primarily focus on explaining the submitted code.
After the phone interview was scheduled, the interviewer did not call the first time. I had to inform my recruiter about this, who failed to respond immediately. After several emails, my phone interview was rescheduled. It was surprising that for a round entirely about my submitted code, the interviewer had not even looked at it. This suggests a lack of preparation on their part.
Overall, it was not a good experience, especially for a company seeking talented individuals.
Problem: Design an org-chart server.
The server (preferably multi-threaded) reads a sample file containing employee data.
File format:
It is semi-colon separated.
The first field is the employee ID.
The second field is the name (can be space-separated).
The third field is the manager's ID.
The employee ID will be equal to the reports-to-ID for the CEO.
The file can have empty lines.
If the number of tokens is not equal to 3, it should ignore these lines but report a message/warning and continue.
The IDs can be numbers or strings.
Sample file: ########### 1: CEO: 1 2: CTO: 1 3: VP Sales: 1
4: Tech Manager1: 2 5: Tech Manager2:
The following metrics were computed from 1 interview experience for the Splunk Software Data Engineer- Behavior Analytics role in San Francisco, California.
Splunk's interview process for their Software Data Engineer- Behavior Analytics roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Splunk's Software Data Engineer- Behavior Analytics interview process in San Francisco, California.