Detroit Labs Interview Questions
& Process

The hiring process was disorganized, with procedural steps lacking consistency and alignment. After completing the interview process, I was offered a position in writing. During the negotiation phase—where both parties were actively engaged—the company unexpectedly rescinded the offer and informed me they had hired someone else. This decision was not only abrupt but also raises concerns about the company's negotiation practices and integrity. I found the process lacked transparency and professionalism, as key aspects of the negotiation were misrepresented. Such practices do not align with the principles of good faith or ethical business conduct. I strongly recommend others approach opportunities with this company cautiously and ensure clarity at every stage of the hiring process.

So after this questionnaire thing, the first interview was like a speed dating type thing, super behavioral. They grouped us into like a dozen applicants and we went around to tables with two people from the company. We had to switch every few minutes and answer like 1-2 questions. You could ask questions if there was time, then a bell would ding and you'd switch. Questions were like standard interview ones such as conflict resolution, and some fun ones like favorite superpower. It was a bit stressful with all the movement and noise, but I did okay since I had practiced common questions beforehand. Then came three technical interviews. The first two were pair programming with another applicant, solving easy problems like basic math functions or string manipulation. We had limited time, and an extra problem if we finished early, which I didn't but later figured out. We used replit to code and test, and since it's an apprenticeship, they didn't expect JavaScript knowledge, but encouraged Googling or pseudocode. They did say beforehand that the technicals would be in JavaScript, so I researched it a bit. Company people watched us, probably checking teamwork and problem-solving. We emailed our code after. The second pair programming was remote due to the pandemic, different partner but same idea. The third technical was also remote, done alone, a bit harder but not too bad. They encouraged more JavaScript research, so it made sense it was more involved. They didn't expect perfect code, and pseudocode was fine if the thought process was good. I know someone who got accepted didn't finish everything, but I think I did, which likely helped.

I applied online for the QA Engineer role and completed a detailed application form which included questions about past failures and team dynamics. Following this, I had an initial phone screening. The recruiter asked about my background and my knowledge of Detroit Labs, along with a couple of technical questions and a behavioral question about giving feedback to a teammate. This call lasted about 20 minutes, and I asked some questions about the role and clients. Three days later, I received an email stating they wouldn't be moving forward with my application because they were looking for someone with more technical experience. Interestingly, they didn't ask any difficult technical questions during the interview but cited a need for a more technical candidate.

The interview process was pretty straightforward. After filling out a survey, I got an email about a week later inviting me to a first-round interview, which was done via video since I'm not in Detroit. I heard back within two days about a technical interview. I flew myself to Detroit for that one. It was a 2-hour roleplay and went really well because I did a lot of research and had good practice from my job. Everyone there was great to work with. Within a week, I got an offer. We had some trouble with salary expectations though. My advice is to ask about salary upfront, as they don't seem to adjust based on your current role or past experience. When researching salaries, don't just use 'delivery lead' as a search term; ask someone at Detroit Labs, they're transparent. It seemed like they were open to my salary expectations at first when the recruiter asked without giving a number. I'd definitely apply again when I'm ready to take a pay cut and just work for an awesome company. This role seems best for someone early in their career or someone looking to wind down.