Pros: - Great base pay. - If you consider work as your life, then this is the company for you. - You can always do something, and you'll get recognized for it. - No micromanagement, flexible work timing (though you'll be working always). - Nice office, free food and snacks. - Recently added cab service. - 7 lakh health insurance without sublimit.

Cons: PIP culture. Everyone's performance is monitored continuously, so it's a rat race. If you work like any normal person, you'll be PIPed to oblivion. No WLB. Focusing on pace rather than code quality. Push shoddy code to prod, but ensure the feature works. Handle hundreds of prod issues later; that's the strategy.

Pros: - I feel like I have a lot of autonomy over figuring out what to work on and how to implement it. - Growing really fast, the future looks bright, which I think keeps most people motivated to do a good job. - I think basically everyone on engineering is trying to do a good job and usually has the skills to back it up. - It's a relatively younger-leaning crowd, which is something that I've enjoyed over other older-leaning companies I've worked at, culture-wise.

Cons: 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.

Pros: Some of the pros of working at Rippling have been: 1. A lot of learning, since the company is fast-paced and the problem statements we are working on are complex. Pretty often, we get a chance to stumble upon something new and learn from it. Particularly for me, since I have been working on the "Device Management" product, it has been a great learning experience to deep-dive into the behavior of the operating systems of macOS and Windows devices, and it has taught me a lot. 2. Really solid engineers. I joined Rippling straight out of college after completing my Bachelors in 2019 and I didn't have any industry experience except my internships. From that period until now, I have met so many individuals, and every time I had something to take from them, especially the engineering team here, they are really solid. A lot of senior engineers on the team have been previous co-founders, and they come with a diverse experience set, and it's not just engineering. 3. One other great thing about Rippling has been that the efforts an individual puts down for a particular stream of work never go unnoticed. Also, the results of someone's hard work show results pretty quickly, whether it's a new feature or fixing a bug. Within days or weeks, we start getting positive feedback from customers, and that's generally the ultimate result for everyone in the company. The leadership in the company also doesn't fail to recognize individuals who are putting in their best, and they get rewarded too. 4. The company's leadership being quite visible. This is a really important trait to have, as it helps individuals get a top-to-bottom view of how the company is operating, what the business plan is, what the overall engineering roadmap is, and other things. And this has been the case with Rippling from the start. It makes everyone be on the same page and then operate as required, which ultimately brings in more success and helps the company expand its business.

Cons: 1. Working in Rippling sometimes gets hard. We can find ourselves in a situation where we need to ship a feature, but an unknown issue has come out. Now, we can't extend the deadline, so in those cases, we need to push a bit harder and get things done. Again, the impact of such features is quite big. The same can happen with an escalated customer for a support ticket, so it becomes important to resolve the issue for us to have the customer's trust in Rippling. 2. One other point which might bug sometime is the timezone difference. As a product team, some members can be in a different timezone. So, for folks in IST, some meetings can be a bit late in the evening. In our team, we have been trying to minimize it by trying to get most of the work done by async messaging.