How To Scale Your Engineering Team

How To Scale an Engineering Team Like a Boss

November 15. 2021

10 min read

High demand is a long-life dream for every business. But one of the most epic pitfalls is the inability to keep up with rapidly growing demand. Before you know it, you've lost your customers, vendor relationships, and a good reputation too.

Every company looking forward to a bright future should be ready for growth. Today we'll talk about scaling an engineering team that is crucial for every digital company.

You'll face several important questions to consider. What team structure fits your project? What roles do you need? How to maximize the effectiveness and minimize costs without compromising the quality?

<medium>Spoiler<medium>: there is no formula, panacea, or one-stop solution that will make everyone happy and successful. The most experienced entrepreneurs make missteps, learn from them, and innovate their approaches.

So, you just need to be prepared and be aware. Forewarned is forearmed! (we love rhymes and proverbs so much)

Engineering knighthood: Team structure and core roles

What is an engineering team in software development? In short, it's a group of tech and often near-tech specialists (including developers, QAs, managers, etc) responsible for the building of the given service or product. These guys are the ones <medium>carrying out all sprints and working on features, updates, and bug fixes.<medium>

Tech companies have <medium>vastly different business needs and therefore vary engineering roles<medium> from one to the next. They support one another and collaborate closely throughout the production process.

So there is no canonical software engineering org structure. It can be various combinations of <medium>developers, software architects, managers, team leads, designers, QA specialists<medium>, and rest.

Let's highlight key engineering roles and figure out why are they so important for your product development.

Where to look for engineers to scale up?

"I'm not the smartest fellow in the world, but I can sure pick smart colleagues". A good team is a key to success. <medium>Mindset matters. Software engineering culture matters.<medium> And putting together the right team is the real art of management.

Where to look for engineers to scale up? Let's highlight the <medium>3 key approaches: dedicated team, internship, and freelancers.<medium>

Softmate is wanted: hiring the right people

No matter how smart and driven you are, your success depends on your ability to:

create a team
inspire a team
work well together toward a common vision

For advice, we turned to Tim Howes, an American computer scientist, angel investor, and entrepreneur. This scaling guru pivots companies, onboards whole teams, expands them in the shortest possible time, and perfroms it masterfully.

In this section, we start considering five dimensions of scale by T. Howes — <medium>the five key points you need to know to scale like a boss.<medium>

PEOPLE: Be an expert on your team (especially its weaknesses)

The strength of the team is each individual member. So let's consider here some interesting team archetypes according to T. Howes:

The oracle VS the prophet

Almost every team has that character — a <medium>bearded battle-tested engineer<medium> who has been there since the beginning. Such an oracle to whom people come for advice.

But not by beard alone: wise programming sensei is undoubtedly invaluable, but you also need people "who are more like a prophet", Mr. Howes says. Companies are interested in the evangelical style of someone who doesn't sit back and wait for people to come to them.

<medium>Reading moon letters on Thrór's Map or prophesying like a Velva — talent to predict future tendencies is anyway a unique skill<medium>. Sharing new ideas with a team and building a development strategy are great benefits for a company. It helps to create an innovative, open-minded company culture and expand business horizons a lot.

The firefighter VS the fire marshal

Engineering teams are very good at putting out fires. And those merry men who respond quickly and keep a grip on themselves are appreciated.

But If you want to get out of such a reactive mode and prevent issues and force majeure in the best possible way, <medium>you need to expand your fire brigade staff<medium>. "As an organization matures, you understand the need for a fire marshal".

As you scale your engineering team, find specialists who are eliminating the causes of fires, not just putting them out.

There is room in your company for different roles: multi-armed Shiva, inspirer and prophet, wise elder, and rebel. <medium>Don't be too conservative and be ready to reevaluate your business needs and adjust your organization's hierarchy.<medium>

HIRING AND ONBOARDING: Don't ignore your biggest investment

The ability to focus on every stage of hiring, from searching to integration, will save your time and energy. However, not all companies give due consideration to it.

To quote Tom Howes, <medium>many businesses often put the hiring and onboarding on autopilot<medium>. Thus, the vital company processes that can't possibly go perfect become even more chaotic and ineffective.

Your key task is to structure these processes as smart as possible. Make it a talking point in meetings and demonstrate its value. You need to:

Structure interview panels
Analyze data from your hiring funnel
Make integration thoughtful and keep an eye out for hiccups in your onboarding process to understand employee's dissatisfaction before it becomes critical

<medium>Important:<medium> Here you can download Freshcode's eBook "Fast Track Developers Onboarding" for free and find some tips that will help you.

Long live the team: How to keep growing

ORGANIZATION: Cultivate order early to bypass chaos

No doubt, leading a team of 10 people is very different from leading a team of 100+ people. The more people you have, the more crucial it is that you <medium>organize them consistently.<medium>

When it comes to scaling engineering teams, T. Howes advises vertical teams and so-called units.

<medium>Vertical is not the only way to go<medium>. The horizontal organization can be effective in other situations. The main thing is to <medium>formalize the role of management and fill it thoughtfully<medium>. Equip every team to get a product off the ground, from engineering to QA to product management to marketing.

COMMUNICATION: Make peace with repeating yourself (Ad Nauseam)

<medium>Communication is what makes teams strong<medium>. Communication is what builds trust. At the same time, maintaining effective communication is one of the most difficult tasks in the company.

The time will come when you'll reach a size when coworkers won't all know each other. In a team of 8-15 people, communication is interactive. You spend less time crafting your epistle message because you deliver it in a dynamic way. <medium>But then things change.<medium>

Scaling communication is not just about your morning dispatches to the team. As growth picks up speed, you need to foster regular interaction, including both formal and informal opportunities.

Vary internal formal communication with code reviews, architecture reviews, and demo days. It helps the company know how things ear going on.

What about informal events, they are no less important. "Once your organization passes a dozen, the whole team isn't having lunch together anymore". Brown bag sessions, beer bashes, theme parties, quizzes, and travel activities — just <medium>think outside the box for unusual ways to improve your team interaction.<medium>

QUALITY: Don't leave it to chance

Finally, the 5th dimension of scale, Her Majesty Quality. With scaling up, keeping a close eye on quality becomes exponentially more challenging.

Howes recommends the following rules to every engineering leader:

<medium>Gather feedback about product/service quality<medium> via sending emails to all who had quality problems that day/week.
Make a <medium>release checklist<medium>
<medium>Codify an ever-increasing pool of knowledge<medium> into a checklist, a set of boxes each product team must check before any release
<medium>Implement code reviews, functional tests, unit tests<medium> to structure the code well

Sound of the horn: When is time for scaling team

Either your <medium>customer base is growing, or the stakeholders have new goals they want to implement as soon as possible<medium> — anyway, sooner or later, you will get to the point where you need to scale up.

To know how to build a team that fits your needs at scale, you should understand the as-is state of your business.

<medium>If you own an outsourcing company<medium>: The size of your team directly depends on the demand level. If you understand that there are more customers' orders than your existing team can address it's time to think about scaling and hiring tech specialists.

<medium>If you are a product company owner<medium>: Your team and its technical expertise determine the speed of product delivery and its unique value proposition. Product companies might require scaling when more human resources are required to keep on track and don't miss timelines.

So put together your Fellowship of the Ring where every team member complements each other.

Takeaway

<medium>If you're scaling your engineering team, it's because either your product is getting bigger or you're adding new products/services/features. Either way, you'll be <medium>juggling many different teams working on many different things<medium>. And the main thing is to do it harmoniously and cleverly without dropping any of them.

At Freshcode, we are helping business unleash their potential through open ways of working and collaborating. And we have expertise that helps us to find individual solutions for every company regarding its needs and opportunities.

We are ready to consult you on how to scale your engineering team — please, fill our contact form.

FAQ

What is an engineering team?

A software engineering team is a group of tech specialists responsible for the building of a given service or product. It carries out all sprints and works on features, updates, and bug fixes.

Different engineering team structures have different benefits and drawbacks. There is the so-called triad of main team patterns:

<medium>Technology Team<medium>

focused on a waterfall approach
emphasis on technical specialists over a more cross-functional team
slower speed to market for new products and updates

<medium>Product Team<medium>

an agile approach to production (Scrum)
emphasis on a cross-functional team setup
fast deployment time

<medium>Matrix Team<medium>

closer collaboration within the cross-functional team
improved time-to-market
deepening the team's business domains knowledge

Nowadays, companies are "tweaking the triad" and customizing team structures to fit their business needs.

What is outsourcing in software engineering?

Outsourcing software engineering empowers businesses to connect with the best tech specialists, no matter how many miles and time zones lie between them. Outsourcing can be a suitable solution both for short and long-term projects (even if you have an in-house development team).

<medium>The common benefits of outsourced software engineering are the following:<medium>

Cost & time savings
Reduced Time-To-Market
New tech knowledge pool
Minimized risks and recruitment costs
Clear outlined deadlines and outcomes

How Freshcode can help you scale your team?

Every partnership is a unique process and we prepare an individual scaling strategy for clients.

Initial consultation with a Freshcode representative is free. It allows you to get basic recommendations on how to scale your engineering team and gain a better understanding of your business needs and perspectives.

<medium>Key facts about Freshode:<medium>