Developing at Teamleader is all about creating something you are proud of, rather than doing some quick coding. Each and every team member is involved in making product and technical decisions from day 1. We don’t just write code, we also review, refactor and improve.
Your day at Teamleader
We prefer to do it the right way and build good quality code rather than writing code as fast as we can. The management understands what technical debt is and allows the team to refactor when necessary. And even though you’re a developer, at Teamleader you are not behind your screen all day, interaction and feedback are very important factors that make our culture.
We’re not going to lie: we definitely have some legacy code you’ll have to axe your way through from time to time, but because of our microservice architecture, we are still able to work with the latest technologies and play with the latest innovations.
You take ownership and are proud of your work. This means you take initiative in pushing your own code to production and, if you want, present your work at the next demo meeting. You respect your colleagues and love to collaborate. This is reflected in the valuable feedback you provide when reviewing someone else’s code or pair programming. We prefer long term focus over short term fixes. We have a good idea on where we want to be in the far-future, and we go there step by step.
At Teamleader we realise nobody knows everything. As a team, we complement each other. This means that you may ask for help today and coach others tomorrow. It helps if you know PHP, but we are looking for someone who can write elegant, maintainable code in the first place. “Always leave the campground cleaner than you found it” is a phrase you understand and apply.