JPMorgan Chase

All this being said, if you end up with a good manager who knows the ropes and you don’t work on anything too custom, it’s worth sticking around at least a couple of years. You’ll learn something, they invest in staff training, and it’s a great bullet point on your resume.

The pay is easily 10-20k lower than what you could get elsewhere.

Although the retirement benefits are nice.

They’ll do whatever it takes to hire you, but then once you work there, you’re just a number.

Once the project is done, teams are chopped up and divided amongst existing teams with little to no warning. You can walk in one morning and abruptly be told you’re on a new team.

There’s tons of red tape. Confusing custom processes mean a lot of re-work and re-submitting tickets. The documentation that does exist is often outdated. While that’s normal in a tech role, often times you’re blocked because you’re working with a custom process (or code), the docs are outdated, and anyone with knowledge has moved on (either being reassigned to another team or leaving the firm).

There’s always something to do, and don’t forget required learnings and timesheets (even if you’re full time).

You’re frequently reminded that you’re just a number. Expect to take on work that isn’t scoped in the sprint. You’re ramping up then ramping down and frequently reprioritizing.

It’s a real challenge to juggle it all, and the requirements process is a total mess. Expect at least some of your work to be “throw away”.