Engineering Manager Interview Experience - San Francisco, California
April 1, 2021
Negative ExperienceGot Offer
Process
The interview process included:
- Initial phone screens with the hiring manager and then recruiter.
- A first panel of interviews, covering system design and managerial background, followed by a recruiter sync.
- A second panel of interviews, which involved presenting a design talk on a system I had built.
Their recruiter made promises about getting back to me, which he didn't keep. He also blew off a meeting he'd scheduled with no apology. Overall, the experience felt disrespectful.
Questions
For system design, we talked about how to build a simple ledger service that would record all transactions sent to it in a reliable and durable fashion.
Was this helpful?
Interview Statistics
The following metrics were computed from 11 interview experiences for the Stripe Engineering Manager role in San Francisco, California.
Success Rate
36%
Pass Rate
Stripe's interview process for their Engineering Manager roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Positive55%
Neutral9%
Negative36%
Candidates reported having good feelings for Stripe's Engineering Manager interview process in San Francisco, California.
Stripe Work Experiences
4.0
Really good at some things, not so good at others
Engineering Manager • Former Employee
San Francisco, California, United States
March 4, 2022
Pros: Very good engineers to work with. The company leadership was outstanding and really cared about both the customers and the employees.
Cons: Middle management was hit or miss. Some of them moved to positions of authority before they knew what they were doing. These were basically growing pains of a hyper-growth startup.
4.0
Experience will be based on the team you join
Engineering Manager • Former Employee
San Francisco, California, United States
January 17, 2025
Pros: Clear vision of product.
Most people have a favorable opinion of the CEO.
Great benefits.
SF office is very nice.
One of the best companies if you value developer (customer) experience.
Cons: As the product has grown, there have been technical architecture challenges. Depending on your role, these can be a great challenge or frustrating.
There is some conflict between work styles, where different tools and processes are used from one team to the next.
2.0
Highly dependent on senior leadership
Engineering Manager • Former Employee
San Francisco, California, United States
January 14, 2023
Pros: Smart, friendly people who are ambitious.
Cons: Leadership is at times short-sighted and often causes thrash by deciding to invest in long-term (9-12mo) projects one quarter, and then pulling resources from it the next quarter.
- 4.0Really good at some things, not so good at othersEngineering Manager • Former EmployeeSan Francisco, California, United StatesMarch 4, 2022Pros: Very good engineers to work with. The company leadership was outstanding and really cared about both the customers and the employees.Cons: Middle management was hit or miss. Some of them moved to positions of authority before they knew what they were doing. These were basically growing pains of a hyper-growth startup.
- 4.0Experience will be based on the team you joinEngineering Manager • Former EmployeeSan Francisco, California, United StatesJanuary 17, 2025Pros: Clear vision of product. Most people have a favorable opinion of the CEO. Great benefits. SF office is very nice. One of the best companies if you value developer (customer) experience.Cons: As the product has grown, there have been technical architecture challenges. Depending on your role, these can be a great challenge or frustrating. There is some conflict between work styles, where different tools and processes are used from one team to the next.
- 2.0Highly dependent on senior leadershipEngineering Manager • Former EmployeeSan Francisco, California, United StatesJanuary 14, 2023Pros: Smart, friendly people who are ambitious.Cons: Leadership is at times short-sighted and often causes thrash by deciding to invest in long-term (9-12mo) projects one quarter, and then pulling resources from it the next quarter.
Stripe Interview Questions
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences
