Rippling

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.

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.