I never received the role name from anyone involved. I guessed DevOps or Systems Engineer.
First, a phone call with the manager to discuss your background, values/goals, and essentially see if it would be a good fit.
Disclaimer: I skipped this step, but this is how it wad explained to me by the manager. Next is a technical phone screen, with a shared session/coderpad or something similar to analyze scripting skills. Any remaining time is meant for mock troubleshooting or general experience/"what would you do if..." type questions.
If you pass that screen (or skip) you will be invited on site for a 5 hour interview panel, with one or more person each. Recruiter provides an informational PDF with team info/links, their values, and what to expect.
The manager and other current employees told me things would be very conversational, with some emphasis on whiteboarding/scripting.
In my case i was told they were hiring for systems engineer/admin type background, on a dev heavy team, and was told by the manager that programming would not be the major focus.
Despite this, more than half of the panel focused entirely on scripting. With maybe two exceptions (see questions), I was not asked in depth questions about linux, monitoring/alerting, networking, or config management. Disappointing. I was not able to display my strengths, and feel I was improperly evaluated. Perhaps this is a side effect of the role not being well defined? Or a sign of poor interview practices? I am not sure.
- First panel was with a dev, typical fizzbuzz on whiteboard and asking situational questions.
- Second was conversational with manager + lunch. Would have preferred a break or social time to meet the team, see cubicles etc.
- Third was whiteboard challenge with a dev focused on string manipulation in json format.
- Fourth was conversational from a non dev, discussed my background and was asked situational questions.
- Fifth was coding quiz on a laptop focused on sorting of data sets
