Jama Software Software Engineer Interview Questions
& Process

I had a great experience with the whole hiring process. I first talked to a recruiter at Jama to learn more about the job and company, which led to a 1-1 phone interview with the hiring manager. After those two phone interviews, I had an on-site interview that was 2.5 hours long. I met five software engineers there. This interview had three parts: a behavioral question part, a technical challenge, and a final meeting with the hiring manager. I also got a tour of their office in Portland. Everyone I talked to or emailed at Jama was really nice and helpful. They all spoke highly of their jobs and coworkers. Even though I hadn't heard of the company before, I really hoped I'd get an offer after my last interview. The only downside was not getting info on how to prepare for the on-site interviews. Other than that, I really recommend checking out Jama Software for your next job.

The process started with the recruitment team. This was the start of what became a very unprofessional interview experience. The recruiter would often say they would schedule something but then there would be long waits with no response. When I followed up, I'd find out a phone interview was scheduled but they didn't confirm the time. After some disorganized phone interviews (and many follow-up emails asking for updates), we moved to the onsite interview, which was even worse. It began with easy HTML/CSS questions. Then came programming questions that felt like they were trying to trick me to boost their ego. After that, the interview was pretty much done. The interviewers seemed disinterested and like I was wasting their time, giving deadpan looks and huffs even when I answered correctly. The whole thing felt like a joke, asking trick questions about edge cases and then dismissing candidates. This, combined with their clear disinterest, made it a huge waste of time and the worst interview I've had.

So I had a bunch of panels, each with like 2-3 interviewers, lasting about 45-60 mins. They covered technical stuff, product sense, culture fit, and leadership. This happened multiple times.