It was a fairly simple interview with a couple of technical questions and mostly behavioral questions. The interview did last about 15-30 minutes and usually doesn't last longer then that.

Got reached out to by a recruiter after applying, and a meeting was set up with the hiring manager. Took about 1 month to get a decision post-interview, and I had to email the recruiter to update me otherwise I think I would've been ghosted. There was no coding in the interview, mainly just talking about my experience.

The interview was conducted over the phone. The experience heavily depends on the team you’re interviewing with, and I didn’t know the team’s primary programming language until the interview itself. My interviewer was a manager, and the session was almost entirely focused on technical questions. During the interview, it felt like the interviewer lost interest early on and that I never really had a chance at the job. They asked if I had experience with multi-threaded programming, and while I admitted I didn’t, I explained that I understood the concept and mentioned my experience with asynchronous programming as the closest related skill. The interviewer was unfamiliar with asynchronous programming, and I didn't give the best example to explain it. The company appeared to place significant emphasis on object-oriented programming, so I recommend being well-versed in the four pillars of OOP and preparing clear, simple examples. Brushing up on data structures and algorithms is necessary, as you may be asked about general runtime complexities for common data structure operations. From my perspective, having an ex-military background could also be a big plus for candidates. Overall, it wasn't the best experience. I wish I had a chance at an in-person interview with a whiteboard element to share my problem solving and programming skills.