Huge variability. The organization is huge, with so many teams. The positive experience I had may or may not be representative of the experience of your average Chase employee.
The team is smart, but there's way too much emphasis on delivering features over fixing technical debt. It seems like no one cares that much about doing things the right way as long as it works (in the short term).
Promotion is more by time than merit (at least for the first few years).
There's too much blind push for AI. Engineers are actually tracked by their LLM usage. No one says it, but we all know it will affect your evaluation. Engineers are flagged for "not using it enough."
AI is great, but please understand that capturing metrics like how often users are using copilot (and then flagging the ones that are not using it enough) is counterproductive.
Best developers use AI to bounce around big ideas and learn about the right way of doing things, not to actually churn out code. Good developers don't even need to spend that much time actually coding, but analyzing.
There's not enough emphasis on code quality. No one ever actually reviews PRs, and with AI slop becoming more of an issue, this is only going to result in more and more technical debt.
Technical debt has resulted in the majority of production-level bugs in the past six months on my team because everything has gotten so brittle. The culture needs to change so engineers care about doing things the right way.
Fair. Ask some questions about RESTful APIs. Ask your behavioral questions and how to process when you have conflicts with your manager. It is a relatively straightforward technical interview.
is hard as tech company interviews, but the annoying part is it’s not standardized like LeetCode is. At least with tech companies, you expect a general format, so studying for one means you study for multiple. JP, on the other hand, will depend on th
I had an interview with the team I'd work with. I had to show knowledge about my engineering stack and show people I would work with that I could be useful.
Fair. Ask some questions about RESTful APIs. Ask your behavioral questions and how to process when you have conflicts with your manager. It is a relatively straightforward technical interview.
is hard as tech company interviews, but the annoying part is it’s not standardized like LeetCode is. At least with tech companies, you expect a general format, so studying for one means you study for multiple. JP, on the other hand, will depend on th
I had an interview with the team I'd work with. I had to show knowledge about my engineering stack and show people I would work with that I could be useful.