Question 1

How quickly can someone start?

Accepted Answer

It depends entirely on who is free, and we will not pretend otherwise — we are a small senior team, not a staffing agency with a bench. When there is a match, introductions typically happen within days and a start follows once contracts and access are in place. If nobody suitable is available for the timeframe you need, we tell you at the first call so you can keep looking elsewhere.

Question 2

What is the minimum engagement length?

Accepted Answer

We normally start with a short paid trial of around two weeks so both sides can judge the fit on real work, then continue in monthly periods with a notice period agreed in the contract. Very short engagements of a few days rarely pay off for either side, because onboarding into an unfamiliar codebase consumes most of that time. Part-time arrangements are possible where the work genuinely suits them.

Question 3

Who owns the code that gets written?

Accepted Answer

You do. The contract assigns all intellectual property in the delivered work to your company, and it is signed before any code is written rather than negotiated at the end. Work happens in your repository under your accounts, so there is no stage at which output sits somewhere you cannot reach.

Question 4

What happens if the developer is not a good fit?

Accepted Answer

That is exactly what the trial period exists for, and ending it is a normal outcome rather than a dispute. During the trial you can stop with immediate effect and pay only for the days worked; after it, the agreed notice period applies. Where it makes sense we will propose a different engineer, but we will not push a replacement just to keep the engagement alive.

Question 5

How do you handle time zones?

Accepted Answer

We work from Turkey, which sits one to two hours ahead of Central European Time depending on the season, so the working day overlaps almost completely with teams in Germany, Austria, Switzerland and the Netherlands. In practice that means the engineer is in your standup and available for a call in your afternoon, not answering yesterday's questions. For clients in the Gulf the overlap is equally comfortable; for North America we agree fixed overlap hours in advance.

Question 6

Can we hire the engineer directly later?

Accepted Answer

Yes, and we prefer to agree the terms at the start rather than treat it as a breach. A conversion arrangement — typically a notice period plus a transparent one-off fee that decreases the longer the engagement has run — is written into the contract from day one. We would rather someone joins a client permanently on good terms than be locked into an arrangement nobody wants.

Question 7

How many engineers can you provide at once?

Accepted Answer

A small number, and we would rather say that plainly than imply a talent pool we do not have. We are a senior team that takes on a limited set of engagements, which is why we are selective about which ones we accept and why we will decline work we cannot staff well. If you need to scale a department quickly, a large vendor is a more honest fit than we are.

Question 8

How does NDA, confidentiality and data access work?

Accepted Answer

A mutual NDA is signed before any access is granted, and access itself is scoped to what the work requires — your accounts, your permissions, revocable by you at any moment. Where production data contains personal information we work against anonymised or reduced datasets wherever the task allows. Credentials are never shared outside the named engineer, and access is removed on the last day of the engagement.

Question 9

When is staff augmentation the wrong model?

Accepted Answer

When there is nobody on your side to own the direction. Augmentation assumes you have a technical lead who prioritises, reviews and decides; without that, an embedded engineer ends up guessing and you get the drawbacks of both models. If the goal is a defined outcome with a deadline and a scope, a delivery-owned project or a dedicated team with its own lead — see our Dedicated Teams page — is the better structure, and we will tell you which one we think fits.

Question 10

What happens at the end of the engagement?

Accepted Answer

Nothing dramatic, because handover is written as the work happens rather than assembled in the final week. You get architecture and decision notes, runbooks for anything operational, open questions and known rough edges, and a walkthrough session with whoever takes over. Access credentials are revoked on the last day and we confirm in writing what was removed.

How can we help?

Staff Augmentation
FAQ

Helpful
information

Getting Started

Timeline

Pricing

Support

Still have questions?

Staff AugmentationFAQ

Helpfulinformation