Staff augmentation
Staff augmentation means individual developers join your existing team and work inside your tools, your process and your codebase.

What staff augmentation means
Instead of handing a project to an outside group, you add one or more engineers to the team you already have. They attend your stand-ups, pick up tickets from your board, open pull requests in your repositories and answer to your technical lead.
You keep direction of the work. The people you add bring skills and capacity, and you decide how they are used day to day.
When adding people works better than a separate team
Augmentation fits best when your team already has a clear way of working and simply needs more hands or a missing skill. Typical cases include:
- A backlog that is growing faster than your team can clear it.
- A gap in a specific skill, such as mobile, data work or a particular framework.
- A product with a lot of internal knowledge that is hard to explain to a new group.
- A temporary push before a launch or a migration.
If you would rather hand over a whole area of the product with its own planning and management, a dedicated team is usually the better choice. The guide to engagement models compares the options side by side.
How new developers join
- Role definition. You describe the skills, seniority and the kind of work expected.
- Matching. Candidates are suggested and you speak with them before anyone starts.
- Access and onboarding. Accounts, repositories and documentation are set up in your own systems.
- First tasks. A small, well-defined piece of work helps everyone learn the codebase and the review habits.
- Regular review. You check fit and workload and adjust the size of the group as needed.
What to prepare
A little groundwork saves weeks later. Before the first day, try to have:
- A readme or short setup guide that actually works on a fresh machine.
- A named person who reviews code and answers questions.
- Tickets written with enough detail to start without a meeting.
- Clear rules for branches, reviews and releases.
- Access arranged on the principle of least privilege, with an agreed approach to confidentiality described in security and NDA.
If you are unsure how to describe the work, the guide to briefing a development project helps turn rough ideas into usable tasks.
Working across time zones
Developers in another region can still share a few hours of overlap with your team. Agree on that window early and use it for questions and reviews, leaving focused work for the rest of the day. More detail is on the time zones page.
Who owns the code
Work produced inside your repositories stays with you. The principles are described in code ownership.
Next step
Tell us which skills you need and how your team works today, and we can suggest a sensible starting size. You can reach us through the contact page or look at the full list of services.