The mission is fantastic and there are people who genuinely care about the mission.
Many of my colleagues were among the best people I've ever worked with. I learned a lot from some great engineers.
If you learn how to play the system, there is room to grow and take on projects that interest you.
The technology needs a lot of work. The focus is on building new systems while not maintaining legacy systems, and then leadership seems caught by surprise when those legacy systems fail. ICs are then expected to change their behavior and processes because leadership doesn't want to fix the problems.
The sales team likes to sell products and services that we haven't built, leading product and engineering to scramble to change priorities and build things quickly. This hurts both the new features/products (which are not always built as cleanly as they should be) and existing projects that get deprioritized.
Individual performance is measured by how much more you do than those around you. There's no way to know if you're doing well because there are no objective metrics, it all depends on the people around you. So performance review season can come with some bad surprises.
I can't speak for other departments, but within engineering, our diversity does not reflect the population we serve. Engineering leadership has strongly deprioritized diverse hiring, insisting that "industry standard" diversity (in an industry where the population we serve is heavily underrepresented) is good enough. It's not.
Forced return to office for those located near the NYC office, even if the rest of your team is not in the office. Yes, the office is a great space for collaboration, but some people work better outside the office - respect that.
While there is an official "Unlimited PTO" policy, some teams strongly discourage taking PTO. I was told at one point that taking more PTO was a "bad look."
Take a good hard look at your leadership team and policies. Fire people who are making things worse instead of better.
Listen to your employees who remember when Maven was a good company and want to bring that back. Growth does not have to equal decline in culture.
Bias training for interviewers and for performance reviews. Everyone has biases. The only way to build a company that is vaguely fair is to understand that and learn how to accommodate for it.
Technical phone screen, then onsite: 1, coding, 1 technical deep dive, 1 design, 1 leadership interview, 1 behavioral interview. Both coding interview were multi-part problems. Based on feedback from interviewers, company raised engineering bar, that
It was good. I was reached out to by a recruiter and I had a short simple call with him. He asked about my prior relevant experience and talked about how that may be relevant to the role.
1. Phone screening with recruiter: Went very well. Discussed projects I had worked on, I work at a competitor in the telemedicine space so most of it was around digital clinic experience. 2. Interview with Engineering Manger: Went very well. Again di
Technical phone screen, then onsite: 1, coding, 1 technical deep dive, 1 design, 1 leadership interview, 1 behavioral interview. Both coding interview were multi-part problems. Based on feedback from interviewers, company raised engineering bar, that
It was good. I was reached out to by a recruiter and I had a short simple call with him. He asked about my prior relevant experience and talked about how that may be relevant to the role.
1. Phone screening with recruiter: Went very well. Discussed projects I had worked on, I work at a competitor in the telemedicine space so most of it was around digital clinic experience. 2. Interview with Engineering Manger: Went very well. Again di