JPMorgan Chase is a "target-rich" environment for technologists -- there's always something to fix, or something to break and then fix again.
The benefits are good, the pay is very good, the Columbus facilities are nice, and they have a lot of money to throw at shiny new toys.
Some programmers and engineers have more stressful lives than others, but there is nothing like the horror stories one hears from game development shops.
You can come across the occasional diamond in the rough or guru while working there, and it is a good place to network for future job prospects.
JPMorgan Chase is not a technology company. There is little respect for technical analysis or input. Management often overrules or ignores the actions of the technical staff, and there is almost never any effective recourse.
There is little room for advancement for someone not interested in management or finance. As a multinational bank, JPMorgan Chase must be one of the largest users of technology in the world. Yet, as a rule, they give their janitors and their engineers roughly equal influence over the direction of IT.
Design by bullet point is a pervasive practice at JPMorgan Chase, since half of the people there are apparently functional illiterates. Death march projects are common. Often, projects exist or proceed the way that they do solely to perpetuate various middle management fiefdoms.
Don't believe anything your direct reports or their direct reports tell you. Come all the way down to the trenches if you would like to learn truthful information.
First, a take-home coding question with a time limit. LeetCode easy, I think. After that, a three-hour session. The people I spoke to were not really talking with me and only asking minimal questions, expecting me to fill up the rest of the time talk
Easy to follow and the instructions were very clear. The questions were not too hard, and they gave you time to explain your code, so you did not only just code.
The interviewer went through my resume and experience for 10 minutes, and the rest of the 30 minutes was for a coding question. The question was stated by the interviewer instead of being shown on the screen, so I used a lot of time to clarify the qu
First, a take-home coding question with a time limit. LeetCode easy, I think. After that, a three-hour session. The people I spoke to were not really talking with me and only asking minimal questions, expecting me to fill up the rest of the time talk
Easy to follow and the instructions were very clear. The questions were not too hard, and they gave you time to explain your code, so you did not only just code.
The interviewer went through my resume and experience for 10 minutes, and the rest of the 30 minutes was for a coding question. The question was stated by the interviewer instead of being shown on the screen, so I used a lot of time to clarify the qu