<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tony Conteiro on Medium]]></title>
        <description><![CDATA[Stories by Tony Conteiro on Medium]]></description>
        <link>https://medium.com/@tony.conteiro?source=rss-e4b717c44599------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6MXYvCNd0JdDuc7Y</url>
            <title>Stories by Tony Conteiro on Medium</title>
            <link>https://medium.com/@tony.conteiro?source=rss-e4b717c44599------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:53:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tony.conteiro/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How do we manage the onboarding of more than 100 people by month ?]]></title>
            <link>https://medium.com/doctolib/how-do-we-manage-the-onboarding-of-more-than-100-people-by-month-b84be5436cb?source=rss-e4b717c44599------2</link>
            <guid isPermaLink="false">https://medium.com/p/b84be5436cb</guid>
            <category><![CDATA[doctolib]]></category>
            <category><![CDATA[scaleup]]></category>
            <category><![CDATA[agility]]></category>
            <category><![CDATA[onboarding]]></category>
            <dc:creator><![CDATA[Tony Conteiro]]></dc:creator>
            <pubDate>Wed, 18 May 2022 14:35:39 GMT</pubDate>
            <atom:updated>2022-06-07T15:18:51.939Z</atom:updated>
            <content:encoded><![CDATA[<h3>How do we manage the onboarding of more than 100 people per month?</h3><p><em>When I saw the reaction of my friends and family to whom I told that we boarded an average of 100 people per month, I realized that this was not insignificant and that it would be interesting to share our organization in order to, I hope, inspire some colleagues.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJBmHXbokoZ4fGMZtShKrA.png" /></figure><p><em>Disclaimer: this article only deals with IT part of Onboarding.</em></p><p>It’s not a secret that Doctolib has experienced a crazy growth in a short period of time: from a few tens to a few hundreds of collaborators to reach today 2500 collaborators and it’s not over. Following our latest fundraising, Stanislas, our CEO, has announced 3500 new hires in the next 5 years. We’re not done onboarding Doctolibers.</p><p>Spoiler alert: the secret is the synergy between the teams involved in the recruitment process, which makes the industrialization of onboarding possible. Now that you know everything, you can stop reading my article and go back to the matrix.</p><p>Joking aside, I must introduce you to these different players:</p><p>The Talent Partner: these are the recruiters, the hunters always on the lookout for the nugget that will strengthen the ranks of doctolib. They are the ones who are at the entrance of the onboarding pipeline, they enter the selected candidates on our production line</p><p>HR: they take care of all the administrative formalities and validate the arrival of the candidate. They are in charge of a crucial part of the production chain: the entry of the Doctoliber into the Human Resources Information System (we will come back later to what an HRIS is).</p><p>IT Engineering: this is the team that implements or creates the tools necessary for this production chain to work at its best. Their objective is to automate everything that can be automated.</p><p>IT Operations: the end of the production chain, they are the ones who contact the New Joiners (NJ), prepare their material and fine-tune the last details.</p><p>Back to the past without DeLorean to tell you how the teams managed it</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*arqCkSk7IgRO93ph" /></figure><h3>In the beginning the Talent Partner created … a G-Sheet.</h3><p>At the beginning I wanted to call this chapter “aie ça pique” because it was so tedious and everything was done by hand, which inevitably led to mistakes and therefore lost time. Keep in mind that I’m not making any judgment: any process has its beginnings before reaching a certain maturity, it’s quite natural.</p><p>So, at the very beginning at Doctolib, our team of recruiters fed a G-Sheet document with the future Doctolibers that HR had validated. IT would retrieve the information, still in the G-Sheet document, and prepare the PC by hand. That is to say, take the PC out of the box, turn it on, pre-install and configure Windows, install the business software with a USB key, install the printer, update the OS and the applications. That’s not all, we also had to create all the accounts: Azure, Google, third party applications. In short! Everything! But really everything was done by hand.</p><p>For the record, IT was also in charge of preparing the building access badges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*pO5iHFU9IFk22Rm_" /></figure><h3>Implementation of the HRIS</h3><p>As the company grew, we had to adapt and change our work methods, which is why we abandoned the G-Sheet and replaced it with Asana, which allows for better ergonomics and simplified monitoring of changes. A quick aside on change, this is also one of the strengths that allows us to manage so many arrivals, our ability to adapt to changes, especially those of the last minute. How many times have recruiters added ten or so profiles the day before the DA?</p><p>We have also added an extremely important brick to the infrastructure: an HRIS, I named Workday. It’s the heart of our onboarding process in that it allows us to streamline the entire process and automate the creation of user accounts. From now on, the onboarding process is as follows:</p><ol><li>HR: enter the NJ in Workday</li><li>IT: Workday synchronize accounts to IDN</li><li>IT: Then IDN sync to Active Directory (AD)</li><li>IT : And finaly AD sync to Azure &amp; Google</li></ol><p>And all this automatically means: no more duplicates, fewer typos and above all a lot of time saved.</p><p>To summarize, this allowed us to dynamically interconnect the 2 big bricks of our infrastructure: Azure and Google Cloud. The users have their “computer” account and their mailbox without us having to do anything.</p><p>Still with the idea of automating and reducing the bandwidth of the support, we have</p><p>implemented the SSO which allows Doctoliber to have only one password for all its applications. Less tickets for the support and more comfort for the users.</p><p>Finally, for the deployment of workstations we switched to WDS, we finally got rid of the manual installation of workstations and once again this means freeing up bandwidth for support.</p><p>The time saved is an important point. Maybe the most important one because it allows the teams to get their heads above water and be proactive. They can think about possible improvements, criticize and review the process in place. And it’s by rethinking the process over and over again that we have reached this level of industrialization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*4G1XO4M9_PQ8R5In" /></figure><h3>Auto provisioning</h3><p>There was one major point left: the creation of application accounts. We have dozens of applications used by our employees, and managing all of them was taking a long time. It was tedious for the Support Specialist in charge of these operations: we had to change that. So we used account provisioning on the applications via Azure.</p><p>We also improved the desktop deployment process by replacing WDS with Windows Autopilot, so there was no need to deploy the desktops. When the PC is opened, the end user has his Doctolib work environment and only has to follow the instructions to prepare his workstation himself.</p><p>The user experience has also been improved through the implementation of email notifications allowing the monitoring of the recruitment process and the management of administrative hiring documents, as well as the resetting of the unique password (thanks to the SSO) by the user.</p><p>Finally, an internally developed script allowed Support Specialist to receive onboarding notifications on Asana automatically. Each new hire created an entry on Asana which increased the reliability of the information entered in Asana which was the cornerstone of the organization and saved time for the teams.</p><h3>Reorganization</h3><p>Touching the limits of the product, we made the decision to replace Asana with Jira. It brought us features that better fit our needs such as notification of changes in the onboarding date, the ability to create scheduled tasks according to configurable triggers.</p><p>In short, a more powerful and ergonomic tool to save us time.</p><p>Spoiler alert: we are working on adding a new brick: an identity manager. We are not done innovating and there will always be aspects to improve.</p><h3>Conclusion</h3><p>Here are the key points that allow us to industrialize onboarding:</p><ul><li>synergy between teams</li><li>the ability to adapt to changes</li><li>reduce manual and non-automated tasks as much as possible</li><li>choosing the right tools</li></ul><p>This is how we manage the arrival of 100 people, on average, every month at Doctolib.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b84be5436cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doctolib/how-do-we-manage-the-onboarding-of-more-than-100-people-by-month-b84be5436cb">How do we manage the onboarding of more than 100 people by month ?</a> was originally published in <a href="https://medium.com/doctolib">Doctolib</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>