Purpose

Why have we created this role in our organization?

As a software engineer, your purpose is to bring the platform to life and to keep it alive and healthy.

Goals & mission

What goals do I pursue with my work? Which key figures or indicators can be used to measure the success of my work?

Your goal is to be an autonomous driver of change. Although this may seem a bit abstract, as a software engineer you have a lot of power to define and shape the future of our platform and, at the end of the day, how the company runs.

So your goal is not to develop and deploy features, your goal is to define, adapt and evolve the foundation stone of this company.

To measure the success of your work you will look into the team's and customer’s response to the job you do. What value is your work creating for the teams and our customers?

Responsibilities

For which products and results am I responsible?

You are responsible for the success of the team.

The success of the team can be measured in different ways:

• The value our solutions are creating for customers
• The experience our customers have with our products
• The impact our team has on the company
• The ability to adapt our product’s architecture

This makes you responsible for the whole product development, from planning to deployment, from defining the problem to testing the solution, and helping the rest of the team work with what we develop.

It is also your responsibility to keep the software architecture at a sustainable level.

Not responsible for

What am I not responsible for?

The following things are some responsibilities that are not part of the software engineer role itself but you might want to explore them at some point, just let the team know to look for opportunities.

• It is not your responsibility to manage the team.
• It is not your responsibility to take care of the well-being of the team members.

Decisions

What decisions do I make?

You have the power to make any decision that may make the team and yourself more successful.

To make this more concrete, you can make decisions about:

• What do you want to develop into
• How does your own development look like
• What kind of rituals and processes does the team have
• What kind of people does the team need
• What problems are worth solving and which ones are not
• What solutions will we build for customer problems
• What kind of user experience our customers are gonna have with our products
• How is the software architecture gonna look like
• How to test and evolve the software architecture

Main tasks

What tasks does my work involve?

• Join shaping meetings to create the projects we will work on Your goal during shaping meetings is not only to determine the effort of doing something but also to challenge the team to explore options, make everyone aware of the impact of the decisions we make, and come up with solutions we all feel comfortable with
• Build the projects we created during the shaping meetings
• Take part in UX discussions of solutions
• Design the architecture that will support the solutions we come up with
• Maintain and develop QA processes and tests
• Review and merge pull requests
• Evolve and maintain the existing documentation the team is responsible for
• Mentor the rest of the team

Tasks that are not part of my role

Things that are explicitly not part of my role.

"Everything which is not forbidden is allowed”

There is nothing specifically that you cannot do just because it’s not in the definition of the role. If you wanna try something out let the team know and we will explore what opportunities exist in the company for you to try out.

Skills and know-how

Knowledge, skills, and precious experience are essential to perform this role.

• Respectfully and openly speak your mind and give your opinion
• Pair along with your teammates to push projects, as well as learn from them and mentor them
• Give clear and constructive feedback
• Diagram solutions and communicate them effectively
• Write useful, clearly readable, and concise documentation
• Solid knowledge of software architecture
• Effective debugging and troubleshooting
• Testing strategies and setup

Sharing with

With whom are you working a lot, and with whom do you need to talk a lot to share information. Stakeholders, committees, ...

You will be working mainly with everyone in your product team, this includes other engineers, PMs, and people from customer success.

Since you will be part of the engineering community you will be regularly bonding with the rest of the people in the community and getting their’s buy-in for decisions that affect every engineer.