You can coast and do just fine if you're satisfied with the status quo. If you're highly motivated, there's lots of room for growth. Just make sure you find the right team who are aware of your contributions. The pay is ok.
The engineering talent available is not very good. It's difficult to find exceptional engineers who are truly good at what they do and care about their craft. If you're good at what you do, you can easily stand out, though.
The politics, as most others say, is very real. Top-level decisions are often made due to politics instead of maximizing end-user/business value. You can easily get lost in an endless stream of unproductive meetings with no clear objectives.
Be more vigilant in driving business goals as opposed to placating misguided political pressures.
Care deeply about clarifying requirements for your engineers and make at least a little bit of effort before dumping vague, undefined goals on an engineer to implement.
Prioritize your time effectively. Don't let others sap all your time with vague meetings that have no clear objectives. It's a very real thing here. I couldn't even begin to quantify how many employee hours are lost to meetings that could be solved with a simple email or message.
The interview was with 2 people. They didn't seem ready to provide additional training and wanted someone who could jump straight into the work. The interview was more a test of knowledge and React concepts than a test of aptitude. Considering the ro
Good and fair. It had a mix of DSA and language-specific questions, along with design principles. There were three rounds: two technical and one managerial. The interviewers are willing to help you get to the answer.
1. Hackerank Test: 2 LeetCode medium. 2. Technical Round - Remember anything and everything about Java in general. Databases were created so that no one has to go through ledger records every time they want to get any info, but I guess JPMC employee
The interview was with 2 people. They didn't seem ready to provide additional training and wanted someone who could jump straight into the work. The interview was more a test of knowledge and React concepts than a test of aptitude. Considering the ro
Good and fair. It had a mix of DSA and language-specific questions, along with design principles. There were three rounds: two technical and one managerial. The interviewers are willing to help you get to the answer.
1. Hackerank Test: 2 LeetCode medium. 2. Technical Round - Remember anything and everything about Java in general. Databases were created so that no one has to go through ledger records every time they want to get any info, but I guess JPMC employee