1. A company recruiter contacted me over LinkedIn and asked if I'm interested in a position in their growing Melbourne office. She arranged a screening call with an engineer.

2. The screening call was at 10:30 AM via Skype and took about 30 minutes. The engineer was the head of the operation, and it was more technical. The encounter was very professional.

3. I received an email from the recruiter that said the screening interview went well and they wanted to meet me. She also explained the interview process.

4. I had 4 back-to-back interviews with different people in one day. The first one was purely SysAdmin, which I tanked. The second one was more DevOps, and the third one was more Solution Architecture. The last interview was with the director of engineering. It was more about my career choice, etc.

5. At the end of the last interview, I met with the team lead, and he gave me feedback on the interview. The gist of it was, "I didn't do well in the SysAdmin interview. Although he is sure that I can catch up, they have an outstanding operational problem and need somebody that can pick it up right away."

Can you explain Linux SUID, SGID, and sticky bit, and where do you use them? Plus some other general Linux SysAdmin questions, e.g., routes, iptables, etc.

We give you access to a Linux server that runs a program. You don't know anything about this program. How do you figure it out?

A dialog about how I use (mostly workflow) Chef and Docker for deploying infrastructure.

We want to send ten million emails in a day. How do you find a solution?

We have a cache server that is shared between a number of services. How do you solve the concurrent access issue?