Pros
- Decent compensation and benefits (including dental, eye, mental health, commuter, education, office lunch and snacks, travel insurance) - Opportunity for remote if not close to an office - Very talented coworkers, opportunity to learn a lot of technical skills from watching senior engineers - Very users focused - it is easy to see the positive impacts of the work you are doing with Stripe's customers, and engineers have the opportunity to do user interviews - Lots of opportunities to travel to other offices for inperson team and broader org events. - Generous time off policy, though people still work/are available during their vacation time
Cons
- Poor WLB; teammates generally work long hours including on evenings and weekends. Culture of always being available - Poor culture; lack of team cohesion, social/networking opportunities, and mentorship - Poor managers -> not supportive in helping juniors advance their careers and skills. Lack of feedback from managers about how you are doing. - In office policy of about 50% of the days, but teammates are not colocated - Oncall can be heavy; 24/7 on call means that you can get paged at any time and have to work at a moment's notice - Stress and burnout seem to both be common - PIP culture -> PIPs and firings are common for perceived low performance - Office politics include backstabbing and making others look bad - Culture of very fast pace results in overload, burnout, cutting corners on projects (hence leading to more trouble down the line) and lack of attention to observability or code maintenance - Relating to previous point, many simple tasks at Stripe take too long to do because of the convoluted and tangled up codebase, particularly the FE codebase