It's been a couple
Ultimately, I left for several reasons:
Pay. Even after multiple raises and a promotion, I was making less than market value.
Two words: Change management. The sheer amount of process behind releasing software is maddening. There were efforts to improve this before I left, but it's not uncommon for something to take several months to make it to production. I simply could not deal with the hoops we had to jump through just to release something. There were "Release Engineers" (I can't remember the exact name) whose sole job was to help navigate State Farm's software release process, and a Change Advisory Board (CAB) full of some people who don't really contribute much other than adding even more steps to an already bloated process.
The icing on the cake here was a member of a DevOps team refused to be flexible at all during a first time deployment due to a mistake on some form. We were ultimately able to release that night due to a bug in State Farm's proprietary deployment software that allowed us to bypass a step.
Many upper level "Architects" haven't written code in 10+ years. These are the people, who haven't written a line of code since COBOL was the dominant language, responsible for making architecture decisions.
Very real possibility to work in old or proprietary tech that will not be transferable to anywhere else. When I started out, I worked primarily in Spring and Thymeleaf. By the time I left, SF had purchased some obscure Oracle product with its own DSL that was entirely database driven. Due to the above points, I was teetering on the edge of leaving, but as someone who enjoys writing software, I want to write software.
When there was adoption of the Oracle product, writing any customizations required architectural approval. They basically wanted software developers that didn't write software. Shortly after the training and project started with this Oracle product, I left.
1st Interview (Phone) - Behavioral questions with recruiter (1 hour) 2nd Interview(On-site) - First part behavioral second part technical with managers and developers (1 hour) I received an offer the next day after the interview and the timeline for
The process began with a recruiter screen, followed by a very tough HackerRank-style assessment. After passing that, I had a 3-hour virtual panel interview. The first hour was a live coding session where I was asked to write code for a complex algor
I talked to some representatives at my university's career fair. They signed me up for an interview right then and there for the next week. The interview itself was on campus, at my school's career center. I was interviewed by two people at once, and
1st Interview (Phone) - Behavioral questions with recruiter (1 hour) 2nd Interview(On-site) - First part behavioral second part technical with managers and developers (1 hour) I received an offer the next day after the interview and the timeline for
The process began with a recruiter screen, followed by a very tough HackerRank-style assessment. After passing that, I had a 3-hour virtual panel interview. The first hour was a live coding session where I was asked to write code for a complex algor
I talked to some representatives at my university's career fair. They signed me up for an interview right then and there for the next week. The interview itself was on campus, at my school's career center. I was interviewed by two people at once, and