Benefits, including salary, vacation, sick leave, and health insurance, were great.
Workplace culture included a lack of go-getters, people willing to think outside of the box, and people willing to challenge any status quo. "We've always done it this way" would perfectly summarize a lot of the technical and business leadership.
Software engineering expertise in general is extremely lacking, with many people having only cursory computer science / software engineering knowledge (but good problem domain / product knowledge). To make the point, if people's opinion on how important unit testing code is were polled, probably only half of the respondents would even know what it is, let alone have opinions on it.
Think about the future. Don't let decades-long career engineers continue to keep technological processes stuck in the early 2000s.
They follow the STAR format; it's very simple and direct about your experiences. If you study up on the style of questions and prepare your answers, you will do fine.
The first screen is your resume. The first interview was behavioral. Two weeks later, they asked for a technical interview with some of the team leads of the project. Basic common sense questions for the behavioral and average skill for the technica
I was interviewed by the program manager and a senior engineer.
They follow the STAR format; it's very simple and direct about your experiences. If you study up on the style of questions and prepare your answers, you will do fine.
The first screen is your resume. The first interview was behavioral. Two weeks later, they asked for a technical interview with some of the team leads of the project. Basic common sense questions for the behavioral and average skill for the technica
I was interviewed by the program manager and a senior engineer.