The company seems to take reasonably good care of you, with a good compensation package and benefits, and a bright, lively working environment.
There is a lot of expertise around to learn from if your objective is to develop an understanding of financial markets. The work is fast-paced, and you will seldom find yourself bogged down in your job. The ability to handle pressure and look at problems from a business perspective is valued.
Good kitchens.
The codebase is old and can be frustrating at times. Core technical people who want to develop their technical skill set will be put off by the demand to get the solution out to customers, often sacrificing quality. If you're in a team that works on legacy products rather than new ones, the skills you pick up will be in proprietary tech that is not transferable.
The flat hierarchy (3 levels from a new, fresh-from-college hire to the head of R&D) may not leave room for advancement that you can show on your resume.
Understand that even though thinking like a financial services company instead of a software company has paid off so far, there will come a time when the old software core will catch up with the growth rate of the codebase.
For new, young engineers, there is too much that is set in tradition in the manner of working.
The interview was a technical phone screen conducted via video call with screen sharing. After brief introductions, the interviewer asked about my Java experience and previous projects. Then we moved to a live coding challenge where I needed to solve
Traditional interviews start with LeetCode-style interviews, followed by behavioral. Be prepared for hard/medium level problems, even one problem to solve for the entire interview. Interviews were standard, and feedback was provided quickly.
Telephonic interview. The interviewer asked me to write a code for deep copy of a linked list. I did, but I did not get selected for the next rounds. Overall, the interviewer was helpful.
The interview was a technical phone screen conducted via video call with screen sharing. After brief introductions, the interviewer asked about my Java experience and previous projects. Then we moved to a live coding challenge where I needed to solve
Traditional interviews start with LeetCode-style interviews, followed by behavioral. Be prepared for hard/medium level problems, even one problem to solve for the entire interview. Interviews were standard, and feedback was provided quickly.
Telephonic interview. The interviewer asked me to write a code for deep copy of a linked list. I did, but I did not get selected for the next rounds. Overall, the interviewer was helpful.