Pros
Some of the pros of working at Rippling has been - 1. A lot of learning, since the company is fast paced and also the problem statements which we are working on complex so pretty often we get a chance to stumble upon something new and learn from it. And particularly for me since I have been working on the "Device Management" product it has been a great learning for me to deep dive into the behaviour 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 had any industry experiences accept my internships, and from that period of time till now I have met so many individual and everytime I had something to take from them, especially the engineering team here are really solid. A lot of senior engineers in 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 works never goes unnoticed, and also the results of someone's hard works shows results pretty quickly, wether it's a new feature or fixing a bug , within days or weeks we start getting positive feedbacks from the customers and that's generally the ultimate result for everyone in the company. The leadership in the company also doesn't fail to recognize the individuals who are putting in their best and they get rewarded too. 4. Company's leadership being quite visible, this is really an important trait to be present as this helps individuals to get to a top to bottom view around how's the company is operating, what's the business plan, what's the overall engineering roadmap 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 help the company expand it's business.
Cons
1. Working in Rippling sometimes gets hard, we can find ourselves in a situation where we need to ship a feature but there has been an unknown which came out and now we can't extend the deadline so in those case we need to push a bit hard and get things done, but again the 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 in order for us to have the customer's trust on Rippling. 2. One other point which might bug sometime is the timezone difference, as a product team some members of the time 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 minimise it by trying to get most of the work done by async messaging.