Jacobs Software Engineer Interview Guide

I started with a thirty-minute initial screening call, which felt pretty low-key. The interviewer was friendly and used it as a chance to get a sense of who I was and what I'd done in my last role. They asked about my experience working in teams and where I saw myself going in my career — pretty standard stuff, but they seemed genuinely interested in hearing my answers rather than just checking boxes. After that passed, I was invited back for a longer technical and behavioral conversation that ran about two hours. My interviewer turned out to be someone I'd actually met at a conference, which made the whole thing feel more like a real conversation than an interrogation. We talked through examples of how I'd collaborated on projects, and they asked me some specific questions about my knowledge of tools and technologies mentioned in the job description. The questions weren't adversarial or trying to trip me up; they felt like they were exploring whether I'd be a good fit and genuinely interested in what I could contribute. What struck me most was how relaxed the whole process felt. Both interviewers — there was a panel of two for the final part — had this nice, approachable energy that made it easy to be myself. I wasn't stressed about saying the wrong thing because the conversation flowed naturally. They walked me through what the company does and what the role would involve, so it felt mutual, not like I was being interrogated. I left feeling like I'd had a real dialogue with people I could actually work with, and a few days later I got the offer.