Staff augmentation for US companies: dedicated developers in your sprints
We source engineers for your roles, you choose who joins, and they work in your repositories and tools and report to your leads. The overlap below is worked out from Alexandria, where our core team works; for people we recruit, location is part of the brief.
- Eastern
- 2 hours of overlap on a standard day
- Central
- 1 hour; our Houston office is on Central time
- Pacific
- No overlap on standard hours
- Models
- Staff augmentation or a dedicated team
East Coast teams get two shared hours a day.
Alexandria is 7 to 10 hours ahead of the US, depending on your zone. The bars show your working day, ours, and where they meet.
New York, Atlanta, Miami
Eastern · Alexandria 7 h ahead
00122 shared hours · 09:00 to 11:00 your time (16:00 to 18:00 in Alexandria)3 shared hours from 8 March to 23 April, and 30 October to 1 November, when Alexandria is 6 h ahead.
Houston, Chicago, Dallas
Central · Alexandria 8 h ahead
00121 shared hour · 09:00 to 10:00 your time (17:00 to 18:00 in Alexandria)2 shared hours from 8 March to 23 April, and 30 October to 1 November, when Alexandria is 7 h ahead.
Denver, Salt Lake City
Mountain · Alexandria 9 h ahead
0012No shared hours1 shared hour from 8 March to 23 April, and 30 October to 1 November, when Alexandria is 8 h ahead.
Los Angeles, Seattle, San Francisco
Pacific · Alexandria 10 h ahead
0012No shared hours
Computed from a 09:00 to 18:00 day in both places. Outside the overlap, work moves through written handovers in your tracker and chat, so your morning starts with the previous day’s pull requests and notes.
What US legal and security teams ask before access.
- State privacy lawsTexas DIR (opens in a new tab)
- There is no single federal privacy law. State laws such as California’s CCPA and the Texas TDPSA, in force since 1 July 2024, give consumers rights over their data. Engineers who can see that data act as your service provider, so it belongs in your contract.
- Vendor security reviews
- Most US companies send a security questionnaire before granting access. We answer it before the start date, and engineers work inside your identity provider, with your MFA and device rules.
- IP and confidentiality
- An NDA, a master agreement and a statement of work come before access. The agreement states that the code and intellectual property pass to your company at the end of the contract term or project, once it is completed and paid.
- Currency and invoicing
- One monthly fee per engineer. The currency and invoicing schedule are set in your proposal.
Four things we settle before the first sprint.
The full hiring process and engagement models- 01
Pick the overlap window
For Eastern time that is 09:00 to 11:00; for Central, 09:00 to 10:00. Stand-ups and reviews go there.
- 02
Security review and accounts
Your questionnaire first, then named accounts in your SSO, repositories and chat.
- 03
Data boundaries
Decide which environments engineers can reach. Production personal data stays in your environment.
- 04
First sprint
Engineers join your next sprint, pick up tickets with written acceptance criteria and demo at the sprint review.
Team extension in practice
“Flojics Technology has effectively filled the gaps in the client’s internal team with highly capable resources.”
Tools, West Coast hours, security reviews and billing.
Do the developers work in our tools and report to our leads?
Yes. They join your product team, work in your repositories, tracker and chat, and report to your leads. They join your next sprint and demo at the sprint review.
Can a West Coast team work with your engineers?
Yes, but on a standard day Pacific time has no overlap with Alexandria. Work moves through written handovers in your tracker and chat, so your morning starts with the previous day’s pull requests and notes.
Will you answer our vendor security questionnaire?
Yes, before the start date. Engineers then get named accounts in your SSO, repositories and chat, and work inside your identity provider with your MFA and device rules.
Can the engineers see our production customer data?
You decide which environments they can reach before the first sprint. Production personal data stays in your environment.
Do US state privacy laws affect the engagement?
They can. State laws such as California’s CCPA and the Texas TDPSA give consumers rights over their data. Engineers who can see that data act as your service provider, so that belongs in your contract.
What do we sign before engineers get access?
An NDA, a master agreement and a statement of work. The agreement states that the code and intellectual property pass to your company at the end of the contract term or project, once it is completed and paid.
How is the engagement billed?
One monthly fee per engineer. The currency and invoicing schedule are set in your proposal.