top of page




If you work at Blue Rhizome you need to be technically excellent, have expert knowledge about at least one subject, have a good idea about Computer Science in general and what’s happening in the field. You should be flexible in terms of what kind of tools you choose instead of sticking only with what you know.

When given a well-defined task, you can independently deduce what needs to be done.

But if it’s unclear you know how to clarify the requirements or know how to ensure that the risks of unclear specifications are understood by the customer.


You clearly communicate about architectural possibilities or challenges and have a minimalistic approach to code (less is better). 


Most important you take responsibility for the work that has been given to you and also responsible for overcoming external problems like a customer not responding to requests for supplying logos or getting your Pull Requests merged.

IN THE BEGINNING, you’ll be working with the technology you primarily were hired for and we focus on how well you perform within your expected comfort zone, how you take the ownership of your work, and most importantly what did you get done and with what quality.




First, there’s the technical path. We do not believe people should have x years of experience in a certain field before they’re allowed to touch it. Rather we believe that people that are good learners and understand the underlying CS concepts well can learn a new skill really quickly with great results, while other people with 10 years of experience in one skill could still be considered bad programmers. So if we see you’re doing great with one skill and are really interested in learning another skill we rather allow you to learn it than trying to find somebody else.


The second growth path is on the communicative side. It’s very important to be able to get the resources you need from the customer, to maintain a healthy codebase, and ensure that in case of problems nothing will escalate more than necessary. If you show communication skills, have the language skills, and understand the business side of things better, you can move into a role where you interact more directly with the customer.


The third path is leadership. At first there’s just being on top of your own work and coaching your colleagues, but once a node grows to a certain size there will always be one person that helps people onboarding, finding a workspace and so on. Also there is the technical lead role where you ensure PR’s are merged, how work is divided and completed and have the final say about technical decisions that affect the whole team and project.

bottom of page