Great functional challenges. In Bloomberg, you work on many "small" problems and see how clients use them.
Many teams have their clients in the same building, which makes the development cycle much smoother.
Pay is way above the market, and raises are far, far away from the average.
Company culture. You really feel empowered and protected. They take care of everything they can to facilitate your life. For example: If you have a child, you have 10 "emergency nannies." Just call, and someone comes home to help you with the kids.
Work with many smart people. The average is pretty high.
Private company; stop worrying about shares, investors, and other crap. There is money to fund any project that is good in the short, medium, and long term.
Flexibility. If you do the job, no one questions what you do.
Flat structure: Speaking about a project with top management or the founders is not something you see in all companies, but it feels sh*t good when a guy among the richest in the world feels proud of your work and tells you about it.
Philanthropy. When you have a bad day, you can just think that you are working for a company where all the profit goes to charity :)
When you do, the company treats you even better, which ends up in a cycle that results in you working 12 hours a day. (That said, no one controls how much you work).
The company needs more advertisement in the tech world, outside of financial cities.
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