Use Of Reddit Software To Brighten Up The Future Of Your Marketing

I admit that most of the businesses still unknown to the perk that Reddit marketing brings to them. But, this is not the truth, Reddit will be ruling over the advertising world after ten years. Those…

Smartphone

独家优惠奖金 100% 高达 1 BTC + 180 免费旋转




Our Engineering hiring process at Teads

In this article, rather than giving you a recipe, we will describe our process, and let the different people involved detail what they are looking for during the interviews.

In fact, we are not looking to fill a specific position prior to meeting someone, we try to find the best fit within our organization depending on the candidate’s wishes. This flexibility gives room for open discussions and avoids applying too many constraints.

On average we welcome 3 newcomers every month in the engineering team. It requires quite some work and we have built and refined a standardized, yet tailored workflow to accommodate different seniority profiles.

We chose to have an in-house team of recruiters which helps in keeping up with our hiring needs in a fast-paced environment. This team is based in Montpellier (south of France) but we also hire for our two other engineering hubs in Paris and Bucharest.

In this context, it’s a challenge to ensure a consistent experience considering the number of candidates we have. If you add the fact that we frequently have new opportunities it can be even harder to keep our process as short as possible as new positions might open along the way.

Hanging out and sharing convivial moments is truly part of our culture.

We care about our candidate experience and we know our process is quite thorough. Our goal is to make sure that we are not wasting their time. This is a real tradeoff. We constantly assess if we should go further in the process and take up more precious time from applicants.

Our recruiters constantly sync with each feature team to stay up to date when it comes to their culture and needs. This way, we are always ready and few things need to be discussed when we open a new position.

During this first short conversation (about 30 min) — preferably by phone, video conferencing or face-to-face — we mostly try to get to know each other, understand the candidate aspirations, motivations, and desires.

It’s also a moment when we take time to give an overview of Teads and figure out if the person we are speaking to has questions about our business.

Following this step, we send a debrief note to the managers involved.

We include a recap of the candidate’s experience, its strengths as well as topics that should be discussed further in the process.

We also have weekly meetings to share about candidates that are in process.

We usually ask our candidates to do a small home exercise. Depending on the candidate, we will send a coding or machine learning test. We encourage her/him to do the exercise using their preferred language and tools. These shouldn’t take more than a few hours to complete. Sometimes a technical test is done during an interview instead.

We know that this step can be heavy on the candidate, but it gives a great basis for a technical discussion with a peer.

In each feature team, we have voluntary software and machine learning engineers that can review these exercises.

Regarding the software engineering test, we expect the candidate to produce a project that works exactly as the problem states it. The code should be buildable and executable without modifications.

Cyrille Dubarry is one of the Machine Learning reviewers :

One important thing for us is that the outcome of the previous step isn’t a harsh Go/NoGo. During the technical debrief, the candidate is expected to explain the solution logic. We mainly focus on the solution weaknesses to give the candidate a chance to improve it with the help of the reviewer.

We know that this step can be stressful. But there is no trap and we encourage candidates to use all the help and guidance they can get from the reviewer.

The debriefing is also a moment where we discuss with the candidate about his/her background, experience, and an opportunity for him to ask questions about Teads with another software engineer.

If the results are below our expectations we do our best to give honest and transparent feedback on what the candidate can improve and work on. As a recruiter, it’s sometimes a challenge to debrief these technical points in depth.

Otherwise, we move forward with the process and will ask if he/she wants to join us for a day.

Organizing a day with the team is important to us. It’s a way to meet everybody and really put the candidate in a situation where he can tell if he/she would like to join us. During this day we concentrate on software craftsmanship and culture fit.

The first thing we do is ask the candidate to have a feedback about the onsite. Then we gather everyone involved in the process to come to a decision. All points of view are taken into consideration.

The offer/rejection step isn’t easy. But in any way, we ask the candidate about his/her personal experience going through our process and all suggestions are welcome to enhance it!

Having an offer from us is only the beginning of the journey at Teads. And it doesn’t stop once job contracts are signed.

Once aboard, newcomers from the past weeks will gather for a comprehensive program. During several days, they will discover the mission and challenges of each feature team.

This session is launched by our Chief Technology Officer and Chief Product Officer. It’s a great way to share the culture, vision, and strategy. It’s also an opportunity for everyone to ask questions about it. During this program, participants will also get an introduction to the AdTech industry.

Unfortunately, nothing is ever perfect. While we were growing, we noticed a few hiccups for some candidates (late feedback or steps that would take too long).

Keeping up with this growth is challenging for the team but we learned, reacted and will keep an eye out on these pitfalls.

Add a comment

Related posts:

Compile your own embedded Linux system

Learn how to build you own custom Linux embedded system from source using Yocto

Sales season is on

You could call me a hipster…or maybe you could call me a yuppie. I believe I have trouble with fitting boxes, but maybe even this reinforces the paradigm I struggle with. I read (not that much), I…

How to navigate the catastrophe of life

This world is toxic and it is sick. I hate watching the news, reading the newspaper or even interacting with my neighbors. I don’t want to appear antisocial. I genuinely love people. But this world…