Alexandra is a full-stack software engineer at Fellow.app in Ottawa, Canada, where she’s helping to build the future of work and make managers attain their full potential. She’s been working as an engineer for the last 8 years, from startups like Fluidware to large companies like SurveyMonkey. Alexandra regularly publishes blog posts and speaks internationally about tech and teams, all while designing and sewing clothes that incorporate custom 3D printed elements. Alexandra is also the co-leader of the Slack Platform Community in Ottawa, and a Twilio Champion.
When anyone starts on a new team, there’s a ramp-up period where a *ton* of knowledge is transferred: there are new processes, names, tools, frameworks, and so many other different details to remember. Meanwhile, critical new relationships are started, and lasting impressions are formed. New team members that don’t get to follow a defined process during this time are at risk of not receiving all the information they need to be effective *fast*, and of not feeling valued by their team.
As an engineer that loves a good repeatable process, I decided that I’d like to make onboarding engineers a task that is both effective and scalable. If you’re bringing on one new engineer or fifty to your project, having a formalized process in place ensures that they can get up to speed on your project quickly, and receive a fair start on the team.
Whether you’re a manager, a lead, or a developer eager to help out, you’ll learn how to create your own exceptional onboarding process, and hear about my own onboarding failures and eventual success.