DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • How To Boost Your Software Engineer Career: Code and Life
  • Ten Questions About Staff Plus Engineers When It Comes to Technical Career Development
  • Why Your QA Engineer Should Be the Most Stubborn Person on the Team
  • The AI Co-Pilot: How to Lead When Your Team's Best Player Is a Machine

Trending

  • Content Lakes: Harness Unstructured Data for Enterprise AI Readiness
  • Evaluating SOC Effectiveness Using Detection Coverage and Response Metrics
  • Has AI-Generated SQL Impacted Data Quality? We Reviewed 1,000 Incidents
  • Why SAP S/4HANA Landscape Design Impacts Cloud TCO More Than Compute Costs
  1. DZone
  2. Culture and Methodologies
  3. Career Development
  4. The Best Approach I’ve Seen for Hiring Junior Engineers

The Best Approach I’ve Seen for Hiring Junior Engineers

Junior engineers often have a terrible experience. Review an extremely well-thought-out program for hiring and onboarding junior engineers into a company.

By 
Jade Rubick user avatar
Jade Rubick
·
Aug. 29, 23 · Opinion
Likes (3)
Comment
Save
Tweet
Share
2.8K Views

Join the DZone community and get the full member experience.

Join For Free

Hiring junior engineers is challenging. I’ve seen so many junior engineers get hired but then be supported poorly.

There is a lot to write about this topic, but today I’d like to highlight a wonderful writeup by John Hyland on what is the best example of new engineer hiring I’ve encountered.

John set up and ran the “Ignite” program for several years, and shares how it ran. It’s kind of perfect!

How the Ignite Program Works

  1. The junior engineers are hired (either in cohorts or continuously).
  2. They go through a project-based onboarding for two weeks. The project is designed to introduce the basics of working with internal systems: Git, JIRA, standups, code reviews, retros, and so on.
  3. They’re assigned mentors.
  4. They go through several rotations with teams. These last for several weeks. They work on real work for those teams, contributing in a couple of defined ways.
  5. They have various social and networking meetings, such as an alumni event, so new engineers can see what it looks like to be successful and also build social connections within the company.
  6. After a few rotations, they’re placed on a permanent team.

There are a lot of interesting hacks they used to make this program work, so I highly recommend it if you’re interested in the topic!

What I like best about this program is it just seems so effective:

Advantages for Companies

  • Save money: These programs can pay for themselves. It’s less expensive to hire newer engineers. If successful, these programs can make it possible for engineering organizations to tilt hiring towards less experienced engineers, potentially saving significant amounts of money. Companies that are able to more successfully harness less experienced engineers will have a competitive advantage over other companies, due to improved cost efficiency. New engineers can have a higher retention rate than those with inferior onboarding.
  • Better value delivery: Better onboarded engineers will deliver value sooner and better, producing more value. The program increases internal connections within the company and across teams, which can lead to innovation and better collaboration. Onboarding can be a way to address high importance, but low criticality work, like tech debt. This can improve long-term company performance because these things tend to drag down long-term delivery if left unattended. Companies can benefit from greater internal diversity (which has been shown to improve product quality and decision-making).
  • Less disruption: New engineers are better-oriented and less disruptive to their teams. They’re able to contribute almost immediately.

Advantages for New Engineers

  • They are more likely to succeed.
  • They feel more valued because they’re contributing more to the company.
  • They understand engineering processes so feel less disoriented as they join teams.
  • They are a better fit for their teams because they’ve had the chance to see a couple of options.
  • They have a cohort of fellow junior engineers they can network with and get support from.

Advantages for the Industry

  • Creates a better pathway for engineers to succeed and grow: The trades have well-established apprenticeship programs — these could fill a similar niche in software.
  • Improves diversity and inclusion in our field

Applicability

This program is most appropriate for medium-sized companies or larger ones, but it mostly depends on how quickly you’re hiring. At New Relic, we did it when we were well over 60 teams, but it could be done at an earlier stage.

“If you hire at least 20-30 engineers annually, it’s likely that 10-15 of them could be early career, which is easily enough to justify putting some resources into doing a good job with it… That’s a higher ratio of early career engineers than many companies go with, and depending on the specific kind of engineering the company does, that may be reasonable. So, you’ll want to adjust those ratios to whatever you’re comfortable with, and consider what resulting hiring rate is needed to warrant an early career hiring program based on your particular circumstances.”
- John Hyland

That said, a lot of the lessons from this can be applied to earlier-stage companies. I think the design of this program is a really good thing to emulate.

Further Reading

To read John's three-part series, you can start here: "Running New Relic’s Ignite Program, Part 1 - Hiring".

Thank You

John Hyland is a former colleague of mine and the author of the post I feature here. Contact them if you’re interested in further details after reading this post. I suspect they’d jump at a chance to do similar programs at other companies, and even to help others who are doing so.

Engineer career teams

Published at DZone with permission of Jade Rubick. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • How To Boost Your Software Engineer Career: Code and Life
  • Ten Questions About Staff Plus Engineers When It Comes to Technical Career Development
  • Why Your QA Engineer Should Be the Most Stubborn Person on the Team
  • The AI Co-Pilot: How to Lead When Your Team's Best Player Is a Machine

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook