There’s a great sense of community in Engineering, which is separately managed across all products. There are a wide variety of opportunities, from full stack to system-level, performance-critical systems.
Open source is widely used these days, and dedicated internal teams offer supported infrastructure. So, you can use this to develop solutions with low operational burden. There are also developer experience teams offering integrated build and deployment tools.
If you are a high achiever who takes ownership of problems and is flexible in finding solutions, you can do well. The company will show loyalty and value your contribution. The company is also very active in its philanthropic work. Being privately owned carries benefits like free entry to many museums, galleries, and other sites the company sponsors.
There is a healthy internal job market for moving to new teams without leaving the firm.
Having been a successful company for a long time, some teams have to deal with quite large quantities of legacy code, which takes a very long time to modernize incrementally.
Focus on rewarding high performers means low and mediocre performers may well get zero pay rises.
Being closely aligned with the finance industry, fully or largely remote work is generally not an option, which may be a deal-breaker for some people.
Production deployments typically require at least team leader approval in many teams, or higher approval for non-standard cadences. This helps ensure the stability of the system but can be frustrating for those used to rapid continuous deployment.
Engineers are all expected to be on an out-of-hours on-call rota for no extra compensation, although the frequency with which this occurs varies wildly between teams.
In some teams, technology choices are limited by running on older platforms.
Put more focus on dealing with technical debt and legacy systems. These not only add friction to ongoing development but demoralize engineers working on them.
Reconsider the ban on remote work, at least for engineering ICs. You rule out some good candidates this way.
Offer more transparency about the annual evaluation process. It's fair, but a lack of transparency can make it seem less so.
It's a classical interview process. It started with an HR round, in which they wanted to know you. After that, there was R1, a coding interview, where they asked one LeetCode medium question. In R2, they asked another LeetCode medium question for cod
Round 1: Initial 30-minute Zoom call with recruiter. Round 2: 1-hour HackerRank session over Zoom. Round 3 and 4: 1-hour HackerRank session followed by a system design session. Round 5: In-person interview.
1. HR interview. 2. Leetcode interview with engineer. 3. 2-hour interview consisting of two parts: a. Leetcode easy interview. b. General technical knowledge around networking. 4. Supposed to be an interview with the manager, but HR kept ghos
It's a classical interview process. It started with an HR round, in which they wanted to know you. After that, there was R1, a coding interview, where they asked one LeetCode medium question. In R2, they asked another LeetCode medium question for cod
Round 1: Initial 30-minute Zoom call with recruiter. Round 2: 1-hour HackerRank session over Zoom. Round 3 and 4: 1-hour HackerRank session followed by a system design session. Round 5: In-person interview.
1. HR interview. 2. Leetcode interview with engineer. 3. 2-hour interview consisting of two parts: a. Leetcode easy interview. b. General technical knowledge around networking. 4. Supposed to be an interview with the manager, but HR kept ghos