I applied on their website, talked with a recruiter, and then spoke with an engineer. I was subsequently given a technical take-home task. The task involved implementing a semi-complicated message delivery queue using microservices and many different technologies that were not on my resume at all. They stressed that documentation and build files were as important as the code.
I spent a long weekend completing the task, creating extensive build scripts, and heavily documenting everything. I fulfilled every requirement, as well as many optional items. I didn't hear back for a few days before receiving a boilerplate rejection late at night.
Looking back, they asked me to implement a semi-complicated, message-driven microservice architecture, complete with a CI/CD pipeline and extensive documentation, using technologies not on my resume. They also specifically said, "We won't use your code or anything," which was odd. None of my coding friends think it makes sense.
Implement a semi-complicated message-driven microservice architecture, complete with a CI/CD pipeline and extensive documentation, using technologies not on your resume. Heavy emphasis on extensive build files and documentation.
The following metrics were computed from 1 interview experience for the Loft Orbital Dev Ops Engineer role in San Francisco, California.
Loft Orbital'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 Loft Orbital's Dev Ops Engineer interview process in San Francisco, California.