Doble Engineering Company Interview Questions
& Process

The recruiter interaction was great. Then I met with the engineering director and that went well, they seemed happy with my background. The hiring manager also felt good about me. However, the head of the software group next door...not so much. I really felt like that technical interview with him was a joke, especially the whiteboard coding part, which just isn't my thing.

This process took forever, like over 3 months, no cap. HR called first to see if I was even interested, then said the hiring manager would call to talk about technical stuff. Then there were long gaps, like weeks of silence between each step. The hiring manager did call for a technical phone interview. After another long silence, a technical interview happened. Then, a coding assignment was given, which they said takes 2 hours but actually took me like 8 hours. They tried to make me feel bad about the time it took. More silence. Then, an in-person interview with 5-6 people, back-to-back for hours, no breaks, no water, nothing. It went way over the scheduled time. After that, more silence for like a month, with them saying they really liked me and were talking to management, which felt like BS. I suspect they already picked someone and were just keeping me on hold.

It was a pretty thorough interview process. The interviewer was sharp and conducted themselves professionally. They seemed genuinely curious about my journey into development and my motivations, which was a nice personal touch. As it's an engineering company, they're keen on developers who are comfortable with core languages, minimizing reliance on external frameworks or APIs, at least at their Tulsa office. The interviewer covered a wide range of topics, with a particular focus on my full-stack development background. My impression is that the role likely involves a web application rewrite of a challenging legacy desktop application. Based on helpdesk data, their current server-centric solution appears to be facing scalability and support issues, prompting a shift to a web app architecture. Consequently, many interview questions revolved around this theme. Overall, based on this interaction, it seems like a very good company.

The interview process went smoothly, but the job offer stage was problematic. I had clearly stated my salary expectations, and they confirmed it was within their budget. However, the final offer presented a significantly lower salary than what we had previously discussed. When I inquired about negotiating a higher salary, I was told it was the maximum for the role and, given my current company's impending closure, I should accept it as it's better than nothing. I found this extremely rude and declined the offer. A month later, I secured a position at a fantastic company, closer to home, with my desired salary. It was a much better outcome than what was offered.