MongoDB is the most mature company I've worked at, in a number of ways.
First, I find the people I work with easy to get along with. People are interested in doing excellent work, but it's a low-drama environment, which I appreciate.
Second, the company itself has a mature vibe. I really appreciate our CEO's demeanor and focus at our All Hands calls. In general, it seems like the executive team is focused on long-term success, not short-term wins, which is great.
I also find the work I'm doing pretty interesting, and there's a lot of potential to learn. The work-life balance is good, and the compensation is excellent.
We're a mature company.
I think the big downside here is that we're big enough that we're not always super agile. In particular, when we need things from other teams, it can be hard to get things on their schedule (no doubt they say the same of my team).
I think this comes from being a large company that is trying to be fairly organized and plan ahead. That means that every team has a long roadmap, so getting our thing onto that roadmap can be challenging.
This doesn't mean that folks on other teams don't want to help. They're super helpful! But when it comes to larger changes, their hands are tied by the planning process.
Keep up the long-term focus, but find some ways to introduce a bit more agility to individual teams.
Way too many rounds. 1. 15-minute call with a recruiter. 2. Two 30-minute calls: a screening with a tech lead, then a 30-minute React app coding session. 3. A 1.5-hour React coding interview, including tests. 4. System design interview. First, I rec
The interviews were actually a dialogue rather than an exam. This fact alone was a game-changer—instead of being interrogated, I was actually involved in a discussion. Rather than being wrong or right about a specific topic, it was a collaborative di
A recruiter contacted me on LinkedIn regarding a job position. My interview process began with two phone interviews (with the director and hiring manager). Since I was unable to come for an on-site interview, the recruiter arranged two video intervie
Way too many rounds. 1. 15-minute call with a recruiter. 2. Two 30-minute calls: a screening with a tech lead, then a 30-minute React app coding session. 3. A 1.5-hour React coding interview, including tests. 4. System design interview. First, I rec
The interviews were actually a dialogue rather than an exam. This fact alone was a game-changer—instead of being interrogated, I was actually involved in a discussion. Rather than being wrong or right about a specific topic, it was a collaborative di
A recruiter contacted me on LinkedIn regarding a job position. My interview process began with two phone interviews (with the director and hiring manager). Since I was unable to come for an on-site interview, the recruiter arranged two video intervie