Pros: Numerous opportunities to make a significant impact due to many unsolved, impactful problems. High visibility within the organization with a transparent nature and accessibility to reach out to anyone. Engaging infrastructure projects such as decoupling, multi-region support, scalability, and performance improvements, providing lots of learning opportunities. Strong focus on individual career development and creating opportunities for growth. Fast-growing, wealth creation opportunity.

Cons: Work can be demanding at times, requiring additional hours to meet our goals.

Pros: Incredibly talented, motivated people: The engineering team is packed with former CTOs and founders. In the past two years, the arrival of a new CTO and several new VPEs and principal engineers has significantly raised the caliber of the engineering team. Many of the best engineers I've worked with in my career are now at Rippling. Growth trajectory: The company's financial growth is remarkable right now, and the ambitious product vision supports continued growth. New product teams and opportunities are frequently popping up internally. Executive leadership: Parker is the best CEO I've ever worked for. He is a product visionary who can anticipate the competitive landscape several steps ahead. Yet he can also dive into technical details with engineers.

Cons: Growing pains: "Hypergrowth" also means growing pains. Some engineering teams struggle with tech debt and the operational burdens that come with it. Company processes, such as performance review cycles, are still being iterated on and change with each new cycle. Work-life balance requires planning: Work-life balance is possible but requires being efficient and setting boundaries with your team. Don't expect a rest-and-vest situation; Rippling operates more like an early-stage startup. RTO: Parker strongly supports a 3 day/week RTO policy if you live near an office, which may not suit you.

Pros: Nice PTO Competent coworkers Decent free food

Cons: Intense, stressful, easy to get fired. Focus on speed, not quality, but you still have to manage quality. Not much engineering learning since most infra stuff is abstracted away. Mostly biz logic if on a product team.