Taro Logo

Great engineering community, management is evolving

Principal Data Engineer
Current Employee
Has worked at Zalando for 2 years
August 7, 2024
Berlin, Germany
5.0
RecommendsPositive OutlookApproves of CEO
Pros
  • Very software and data-driven company.
  • Great technical challenges for any type of engineers.
  • Well defined tech lifecycle management process with enough restrictions and permissions to drive the big changes.
  • Relatively low bureaucracy, sometimes too low.
  • Inclusive engineering community that will support you with your ideas, provide challenge and expertise.
  • Great SRE practices and continuous operational efficiency improvement.
  • If you are a leader - you will have enough opportunities to show yourself.

Main point - you can really influence the delivery of great things and change the way the company works. It is still possible thanks to Zalando internal culture and non-overburdened processes.

Cons
  • Engineering teams have not aligned in terms of grades. For example, some teams might have very strong Senior Engineers with matured ownership and cautious decision making, and in the others you might find a Senior Engineer who acts like a toddler. Salary is same though.
  • Mechanism to really make the level of your contributions transparent is still in the "emerging" state. You can set "Focus areas", commit and achieve the goals, but grading your contributions is non transparent at the moment. Thus, career perspectives are not always clear.
  • Somewhat great strategical visions not always backed up by a particular responsible executive person. Waiting until data strategy will implement itself is not very efficient tactics to achieve the goals. Same happens with some company-wide engineering process which is assumed to autonomously adopted by teams (like risk-management), but it's not always the case.
Advice to Management
  • Obligatory planning for focus areas that are linked to company goals. Commitments should be linked to some bonus/malus system in whatever form - if you fail the commitments, you should learn something and have motivation to be better next time. Repeating same errors in planning, estimation and delivery every year is possible today, and I doubt that everyone receives deserved feedback (as it is frequently not even analysed retrospectively).

  • Demand from all those people who ask for money (funding ideas/products) to commit on bringing measurable result and track it regularly. And then see above. I would be happy to see more matured management who acts very pragmatically when it comes to commitments: either doesn't make one, or hold the responsibility.

  • OFMs are great, but to be honest - they are severely overlapping each other, and we all might benefit from simplification for internal needs. Like 3-5 most important principles we follow.

Complexity here creates a lot of opportunities to cheat and misinterpret the OFMs as it is subject to confirmation bias: we tend to back up our decisions by finding positive features.

E.g. engineer deploys to production skipping the tests that would fail in testing environment. Code fails in production, he fixes it and deploys again - it works. Is it good? No, we discourage such behaviours, thank god it was not creating the incident.

But engineer might sincerely think that he "Keeps it simple, Sherlock" or that he "Thinks big, acts fast".

Or that saying "Yes" to even the dumbest ideas from stakeholders and go to implementation phase without understanding the purpose and consequences is about "Start with Yes".

Additional Ratings

Work/Life Balance
5.0
Culture and Values
5.0
Diversity, Equity, and Inclusion
5.0
Career Opportunities
4.0
Compensation and Benefits
5.0
Senior Management
3.0

Was this helpful?

Zalando Interview Experiences