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.
Overall, it was a pleasant experience with a fairly simple, practical coding assignment. I was asked to code a partial solution for a delivery app. They allowed me to use an AI assistant and to look up things if needed.
HR Intro Front-end Technical: Leetcode-style problem Behavioral Interview: Project deep dive + roles and values On-site (3 parts): 1. Leetcode 2. Front-end Whiteboarding 3. System Design
They reached out on LinkedIn. We scheduled a phone call, and they were very friendly. They asked a few general behavioral questions. Then, a few days later, I received a rejection email.
Overall, it was a pleasant experience with a fairly simple, practical coding assignment. I was asked to code a partial solution for a delivery app. They allowed me to use an AI assistant and to look up things if needed.
HR Intro Front-end Technical: Leetcode-style problem Behavioral Interview: Project deep dive + roles and values On-site (3 parts): 1. Leetcode 2. Front-end Whiteboarding 3. System Design
They reached out on LinkedIn. We scheduled a phone call, and they were very friendly. They asked a few general behavioral questions. Then, a few days later, I received a rejection email.