People are basically nice; conditions are pretty forgiving.
After a few years here, it's kind of a get-what-you-pay-for kind of deal.
I think on some level management is aware they're not expecting a ton, and managers here have been promoted after heading up total failure projects.
There are entrenched figures with tight interpersonal bonds; their favorite people seem to snap up the lion's share of the raise money year after year.
The degree to which you're expected to put out 'extras' if you want a promotion (big raises really only happen with a formal promotion here along a pretty well-defined title hierarchy) is high enough as to not be commensurate with what the promotion will actually bring you.
Enough long-timers here discuss year-over-year raise rates enough to know over-achievers here still aren't getting what they could elsewhere.
At the same time, management is happy to let you coast and still get you at a cheaper and cheaper rate each year as the local tech market salaries grow faster.
As a huge company with never-ending options that moves at its own pace, they kind of know they hold all the cards with a long-term full-time employee.
All in all, it's not a terrible place to work. Just disappointing after several years here.
Self-advocacy here is almost pointless, and I should have moved on after about 2 years (get the name and experience on the resume, then better your career elsewhere).
You have multiple odd birds in senior and management spots at this point, and there's a growing sense of fiefdom where more and more of the serfs are feeling like they really only win if they're helping someone else build their little corner of the office.
1. HR reached out. 2. Answer behavioral questions, questions relating to your resume and past experiences, and role-based questions with the hiring manager. 3. Coding with an engineer. 4. Tech stack questions with an engineer.
I had a phone screening split into two parts. The first part involved Java technical questions and basic concepts such as Overload vs. Override. The second part was a little more difficult, where I was asked a scenario question: What happens if I
Received a call to set up a meeting time. They sent an email to download software for a video call. Questions were mostly about development experience, the software lifecycle, DevOps processes, and some usual technical interview questions.
1. HR reached out. 2. Answer behavioral questions, questions relating to your resume and past experiences, and role-based questions with the hiring manager. 3. Coding with an engineer. 4. Tech stack questions with an engineer.
I had a phone screening split into two parts. The first part involved Java technical questions and basic concepts such as Overload vs. Override. The second part was a little more difficult, where I was asked a scenario question: What happens if I
Received a call to set up a meeting time. They sent an email to download software for a video call. Questions were mostly about development experience, the software lifecycle, DevOps processes, and some usual technical interview questions.