The below applies specifically to the Engineering & Product departments. I can't speak to the experience of other departments: - The higher-ups (Directors and above) have an idea of the "perfect way to do things", and they get frustrated and upset when something doesn't exactly fit that mold. They seem unable to understand that their way of doing things is not necessarily the best way of doing things. The company will never be able to grow if you force your employees into following this specific path without ever considering that there might be a different path that will lead to better results. It is very much an old-style software company management style, even though it is a relatively new company.
The higher-ups believe that their way is the best and only way of doing things, and are incapable of understanding that there might be better ways of doing things. - The higher-ups view the work being done through a frosted glass window, and again, get frustrated and upset when that frosted glass window makes it seem like the work is being done in such a way that doesn't exactly match their idea of the perfect way to do things. This results in constant conversations explaining why something needed to be done differently than how they envisioned, even though the task still produced the same results.
They don't seem to understand that software development doesn't always go as planned, and that one of the concepts of agile software development is being able to quickly adjust your way of doing things in order to better benefit not only the product, but the team as a whole. This makes you feel like less of an engineer, and more like another code monkey who is just listening to marching orders from above. This also quite literally results in making engineers second guess how they're doing their work, with the fear of getting talked to by upper-management because they could potentially be doing something in such a way that does not match management's perfect process mold.
Advice to upper-management: Let the engineers be engineers, let the PMs be PMs, and keep the micromanagement out of it. Learn that you are not the engineers, and you are not the PMs. Learn to accept that your way is not always the best way of doing things. Learn to accept that your employees might have a better idea of how to do something than you do. Learn to accept that it is totally okay if work is done differently to what you envisioned as the perfect "path", and in fact, that it might be beneficial to the product and company morale. The company has had multiple people leave due to cultural issues, and while the company is actively trying to improve these issues (which is great), there's still a ways to go.
The higher-ups need to learn to let their employees do what they do best: build software. This is the lowest common denominator. I'll say it again: this is THE lowest common denominator, and if this can be addressed, you will have a company with not only great software, but great culture as well.
Let the engineers be engineers, let the PMs be PMs, and keep the micromanagement out of it. Learn that you are not the engineers, and you are not the PMs. Learn to accept that your way is not always the best way of doing things. Learn to accept that your employees might have a better idea of how to do something than you do.
Learn to accept that it is totally okay if work is done differently to what you envisioned as the perfect "path", and in fact, that it might be beneficial to the product and company morale. The company has had multiple people leave due to cultural issues, and while the company is actively trying to improve these issues (which is great), there's still a ways to go.
The higher-ups need to learn to let their employees do what they do best: build software. This is the lowest common denominator. I'll say it again: this is THE lowest common denominator, and if this can be addressed, you will have a company with not only great software, but great culture as well.
I applied online. The process took 3 months. 1. Zoom meeting with the hiring manager 2. Zoom meeting with a Junior Designer 3. Zoom meeting with 2 Product Managers 4. Whiteboard challenge (over Zoom) 5. Zoom meeting with SVP of Product and Engineeri
Was short and canceled, interviewer sounded full of themselves and they canceled the position after 2 rounds... company seems to be a mess tbh would not recommend, everybody seemed full of themselves.
I applied online. The process took 4 weeks. They had two rounds of interviews with me, where they claimed I was juuuuuuuust what they were looking for. They asked me some nondescript, nonremarkable questions. Each interview seemed more friendly than
I applied online. The process took 3 months. 1. Zoom meeting with the hiring manager 2. Zoom meeting with a Junior Designer 3. Zoom meeting with 2 Product Managers 4. Whiteboard challenge (over Zoom) 5. Zoom meeting with SVP of Product and Engineeri
Was short and canceled, interviewer sounded full of themselves and they canceled the position after 2 rounds... company seems to be a mess tbh would not recommend, everybody seemed full of themselves.
I applied online. The process took 4 weeks. They had two rounds of interviews with me, where they claimed I was juuuuuuuust what they were looking for. They asked me some nondescript, nonremarkable questions. Each interview seemed more friendly than