🧠 Structured onboarding: Strong early-career training programs like Tech Connect and Force for Good projects help you ramp up quickly.
🏢 Stability and prestige: Working for one of the largest financial institutions provides job security and resume value.
🛠 Modern tech stack (in most teams): Microservices, AWS, Kafka, Spring Boot, and Kubernetes are increasingly common depending on the team.
🌐 Global collaboration: Opportunity to work with diverse teams across NYC, India, London, and more.
👨🏫 Mentorship: Many experienced engineers and managers are open to helping junior devs grow.
🧘♂️ Work-life balance: Generally good unless you're in a revenue-critical area. Hybrid work is encouraged.
🐌 Pace can be slow: Processes and red tape are heavy in certain orgs; it’s not a “move fast and break things” culture.
🔒 Legacy systems: Some teams still operate on outdated tech, which can limit growth or be frustrating.
🏦 Finance-first culture: Product and user experience can take a backseat to compliance or regulatory requirements.
📈 Promotion pace: Advancement to SE2 can feel slow and unclear, especially without proactive sponsorship.
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.
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.
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
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.
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.
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