Logo Proxmox Server Solutions GmbH

Proxmox Server Solutions GmbH

Established Company

Developer Dev Review

Employee

Engineering

  • Stable Code Base

    The team places heavy emphasis on a high quality and stable codebase.

    4
  • Documentation

    There's a strong focus on comprehensible documentation of the applications.

    2

    Comment

    Documentation in code is sparse, documentation on product structure and where to find what does not exist.

  • Continuous Delivery

    The process from the code commit up to production is well automated.

    1

    Comment

    No automated testing, code is considered 'tested' if it runs on the developers and reviewers machine. Builds are done and published by just a few people in the company.

  • Modern TechStack

    The team is free to work with the most modern technologies and tools.

    2

    Comment

    Using Rust for new components is a plus, but development relies on a mailing list, which makes it really hard to efficiently determine which patches still need review. Patches sometimes just get lost, manually tracking which of their changes already made it to production is left to the developer.

  • Open Source Contribution

    Providing open-source-software to the community is important to the team.

    5

    Comment

    The codebase is fully open source and AGPLv3 licensed. Members of the team often contribute to other projects and prefer to go through the process of making changes upstream

  • Product Participation

    Developers aren't just working off tasks, but also have a voice in the decision making process of the products.

    4

    Comment

    Developers decide themselves what to work on and how to prioritize their work. Product decisions are made by just implementing it and hoping that it gets accepted. Minus points here, because it's rarely communicated what people are working on, and

  • Meeting Efficiency

    Nobody shall be wasting their time in inconclusive meetings.

    2

    Comment

    There are no meetings, which one might intuitively count as a good thing, but since there is no incentive for communication, quite voices die out while confident ones dominate the conversation. Made me miss dailies and weeklies, for the knowledge exchange, knowing what everyone is up to and speaking openly about technical problems that one might be hung up on.

  • Agility/Adaptability

    The team can quickly react to the needs of clients and the market.

    4

    Comment

    If an issue is pressing, usually someone quickly takes the issue and the release can be sped up significantly if it's important enough.

  • Project Management

    Excellent requirements- and project-management is a given.

    2

    Comment

    Requirements (if existing) are usually only communicated verbally. Management is close to not existing, everyone works on what they deem important. The issue tracker is mostly used for external bug reports and feature requests. People sometimes don't assign themselves to an issue while they are working on it, resulting in doubled work, which can be frustrating if one already spend a few hours to days on it. It's not clear, who has expertise on what, which can be very difficult when starting out. Teams in the classical sense don't really exist, collaboration is rare. Code review on can take very long.

Career Growth

  • Technical Training

    The team is always on the current level of technological knowledge.

    3

    Comment

    You can take the time to learn something by yourself, but there is no monetary support for trainings or the like.

  • Good For Junior Devs

    Juniors are always welcome und will get the support they need.

    1

    Comment

    While the company accepts Junior devs, there is no further advice, support or oversight. Juniors are expected to train themselves, or 'grow with the problem' I guess. The complete lack of feedback can really destroy one's confidence and stress handling ability.

  • Career Opportunities

    Be it new technical responsibilities or a complete switch to IT-management, everything is possible.

    3

    Comment

    Hard to say from my time at the company so far, but what I can say is that the procedural and technical skills don't translate very well to other companies.

  • Safe Environment to Fail

    Employees can try out new things and learn from mistakes.

    4

    Comment

    Developers are given the absolute freedom to try and explore new things, I only wish that there would be incentive to share what one has learned with the team, instead of quietly dismissing it, if it wasn't applicable at the moment. Learning from mistakes can be hard without proper feedback.

  • Freedom at Work

    The team provides enough space for people preferring to work on their own.

    5

Workingconditions

  • IT-Equipment

    It's always possible to be working with modern hardware and infrastructure.

    5

    Comment

    Recent and powerful workstation and ultra-wide screens.

  • Work Flexibility

    Flexible working hours as well as remote work are a possibility.

    3

    Comment

    Working hours are flexible, with core hours from 10 to 15 o'clock. Remote work is not intended and frowned upon, even with good reasons like a sick partner at home with a highly contagious disease that has recently kept the world in suspense and a high likelihood that you are also already contagious.

  • Office Equipment

    An inviting interior with good furnishing makes the work environment something special.

    4

    Comment

    Can't complain, current renovations also seem very promising

  • Work-Life-Balance

    Working hours are within an ordinary timeframe, without any peer pressure for extra work.

    5
  • Salary & Perks

    Payment is decent and fair, with appealing extras on top.

    4

    Comment

    Decent salary and benefits like Klimaticket and Jobrad

Culture

  • Teamspirit & Fun

    Everybody is working together and there is a relaxed atmosphere within the team.

    3

    Comment

    It's more like working side-to-side on the same product. Everyone wants it to succeed, but the lack of teams and collaborations sometimes lets one feel like you have to face every problem on your own.

  • Communication Culture

    All of the staff members are always up to date and can openly express their opinion.

    2

    Comment

    Rare communication on what is planned for the future. It feels often like critique is acknowledged but not acted upon, or you get an explanation why your on the spot idea on how to solve the problem is wrong, without addressing the underlying problem. I'm sure there are counterexamples of that, but that's what I've seen in my time so far.

  • Team Diversity

    All team members are diverse with regards to gender, background and age.

    5
  • Appreciation at Work

    One's effort is always acknowledged within the team.

    2

    Comment

    Rarely more than 'thanks, applied!' on the mailing list. Would probably be better if there were any feedback meetings