Onboarding Engineers 2/2

In the first part I have described the preparation for new joiners and how is important to have structured onboarding during the first weeks on a new job.

In this part we will go into more details of a personalized space.

Week 1

As the first day is about welcoming and meeting our team and getting comfortable to our office, the rest of the week will be a structured guideline to the role and more engineering topics.

We believe that transparency and communication are key values that help engineers to get integrated into an organization.

Having a personalized space as guideline helps you as a new engineer to understand technology and processes we use.

In general section you will learn more about your role as QA Engineer, understand the responsibility and expectations. You will get familiar with regular events in your calendar and understand the importance of it.

You will work on installing and configuring necessary tools for everyday tasks. Of course, if you are unfamiliar with them there are workshops on how to use these tools.

Configuring database and github access will help you in the first week to learn about infrastructure and environments where the software lives.

And then, you will meet many team leads and get introduced to our products and tech stack. How do we build the bank world loves to use.

Week 2

It is quite possible that not all the meetings will happen in the first week, but that is not the point of having a structured onboarding, it’s a guideline and not a strict rule. Plans can change and be adjusted, the important is that for you as a new engineer in the organization things are clear and understandable.

The second week brings some hands-on work where you can use your previous experience and learnings you have got so far to contribute to your team.

You will get introduced to our products and how you can test them. There will be sessions about our quality processes and technical documentation which can help you to understand and use tools and assets to perform different types of testing.

As this will take most of the time from the second week and you will be involved in team ceremonies, you will actually have already some experience and feedback to give.

Week 3

Writing a short page as a feedback for our onboarding and first weeks in general will help us to improve the whole process.

You will also work on pairing with other engineers, learn about our deployment and release flows, test automation and also contribute to them with small changes.

This will help you to learn about our technical infrastructure but it will also be fun as in the end, we are engineers, having to read a lot without putting some hands-on work is not so satisfying.

What is next?

First, we should celebrate as you unlocked the next level!

We believe that having a centralized place where a new engineer can find everything necessary to learn and how to contribute to their team is very important.

Structured onboarding gives a great welcome to our company culture and provides clear expectations for a new employee.

As with building the software, you iterate and improve all the time, that is the same with our onboarding, we collect the feedback and make improvements.

If you are interested in testing our onboarding process, have a look at the roles we are looking for.