I asked a friend who had worked there for seven years to share my resume. He forwarded it to his ex-boss, who then passed it to HR. After an initial conversation with HR, I was scheduled to interview with the hiring manager.
This was the WORST interview experience of my eight-year career.
The interviewer started with no introduction and immediately asked:
At this point, I interrupted and asked, "I applied for a DevOps role. Why are the questions about Java?"
He then shifted gears and asked:
To which I answered, "As far as I know, Lambda can help set this up."
His next question was: "How would you handle mapping in ECS for the same port number in Docker but a unique one on the host for a service?"
After I provided a few solutions, he quickly ended the call, saying, "Thank you. I think there's been some miscommunication here."
The interviewer started with no introduction and jumped straight into questions.
"You know Java, right? Explain Java reference types."
Question two: "Explain blocking versus non-blocking in Java."
This time, I interrupted and asked, "I applied for a DevOps role, so why are the questions on Java?"
He said, "Okay. Explain how you would feed ELB access logs and parse them in real-time instead of using S3."
To which I answered, "As far as I know, Lambda can help set this up."
Question two: "How would you handle mapping in ECS for the same port number in Docker but a unique one on the Host for a service?"
I provided a few solutions. He quickly ended the call, saying, "Thank you. I think there's been some miscommunication here."
The following metrics were computed from 1 interview experience for the Autodesk Dev Ops Engineer role in San Francisco, California.
Autodesk's interview process for their Dev Ops Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Autodesk's Dev Ops Engineer interview process in San Francisco, California.