There's a good amount of tech debt that slows things down and makes things difficult to understand. We're in a heavy growth phase, so this is mostly a backburner issue (probably rightfully so), even though it increases overall workload.
Some teams often make technical decisions which seem very questionable, at least from the outside looking in. This leads to crazy complicated issues that are tough to undo.
There's an infinite amount of work to do, so it's up to you to control and manage it.
The variance in code quality that some engineers/teams have versus others is pretty jarring.
I'm sure everyone who gets promoted has done things to deserve it, but there are times when people at a higher level than me in the eng org do something as basic as not communicating important things to dependent teams in pursuit of a fast timeline. This creates a multi-week fiasco to try to patch it up. Sometimes, it shows that some people perhaps got promoted too quickly to a relatively high role, or are under so much pressure to deliver (often very directly from the CEO) that they forget to do some basic things.
I know the cons list is longer than the pros list, but overall, if you either know or learn to control your career as an engineer, you'll probably be fine, grow a bunch, and make great comp if Rippling IPOs.
Typical process: HR screen, then a coding round (phone screen). Another coding round onsite, and a system design. Then a project deep dive and team match. They allow you to use AI in the coding round, which was strange because it is a typical LeetCod
Two System Design rounds + one coding round. The interviewing engineer looks really busy. They have to conduct three interviews per week. I remember someone told me this in an interview.
They sent a fresher to interview a candidate with 10 years of experience. The problem was very standard, and the interviewer expected only one use case to be implemented. However, the candidate coded all scenarios and was still rejected. Throughout t
Typical process: HR screen, then a coding round (phone screen). Another coding round onsite, and a system design. Then a project deep dive and team match. They allow you to use AI in the coding round, which was strange because it is a typical LeetCod
Two System Design rounds + one coding round. The interviewing engineer looks really busy. They have to conduct three interviews per week. I remember someone told me this in an interview.
They sent a fresher to interview a candidate with 10 years of experience. The problem was very standard, and the interviewer expected only one use case to be implemented. However, the candidate coded all scenarios and was still rejected. Throughout t