Skip to content
Marcel Lefter

Engineering LogCase study

Scaling the front-end org from 1 to 10

How the front-end team at EBS Integrator grew from one engineer to ten in two years, and why people stayed.

Marcel Lefter2 min read
  • Case study
  • Hiring
  • Teams
front-end engineers in 2 years
1 to 10
people left less often, so no refill hiring was needed
Less turnover
less onboarding time (estimate)
~50%
engineers on the career framework
50+
Role
Front End Lead, then Engineering Manager
Company
EBS Integrator
Period
2021-2023
Org
From 2023: 12 engineers, 3 designers

Context

I became a lead in 2021 and started building my team on my own for our projects. I hired two engineers myself, and the rest of the team came from the internship, which I ran and mentored until interns became full members. That grew the team to 5. Then the tech lead of the second front-end team left, its engineers joined mine, and we were 10.

Before that, there was a period when many people were leaving. In the two years after I became lead and built the team, people left less often, and that gave me room to build processes for the team.

What I did

Hiring and internships

I owned recruitment, onboarding and mentoring for the front-end team, and ran the internship program. I wrote the technical test and the interview questions, which in practice became how we hire front-end engineers. I also defined the internship: what interns build, which lessons they work through to become effective, and which standards they follow.

A career framework

Clear expectations for every level. It started in my team and was later used by 50+ engineers across the company.

Shared processes

A knowledge base, a dev guide, code review practices and a release policy. By my estimate, onboarding time dropped by about half.

Mentoring

5+ engineers grew from intern to mid-level. To learn how someone would work, I gave them no tasks for about two days and watched what they did on their own. Some found something in the project to study and work on. Others didn't want to do anything. That showed me much faster whether the person would stay on the team, because without proactivity it is hard to work together and you can't build a high-performing team.

What I'd change

The transition was the hard part. The tech lead of the second team had a different vision of how projects should be built, including the structure and the code style guide, and it was hard to bring the engineers to one standard.

If I did it again, I'd write it down from the start: how code should be written, what to check in code review, how to test the results and how to structure a project. Then I'd give it to the team as a hand-off.

Subscribe

Get the next entry by email.

RSS feed
Written by
Marcel LefterTechnical Product Lead, SkalX

13 years in software, front-end first. I've led teams of up to 15 and now take products from client need to production.

Open to founding and product engineer roles