Salesforce developer
- Apex
- LWC
- CPQ
- Integrations
Available now
Team / Roles and seniority
The roles you can get, at the seniority you need, in weeks rather than quarters.
A single dedicated team, not a shared pool rotated between accounts, working in four seniority bands. You interview every person before they join your team, and you keep the same people for the life of the engagement.
Five
Engineering practices staffed, from Salesforce to applied AI
Four
Seniority bands, from junior through to technical lead
GMT +5:30
Working day that overlaps Australia, Asia, the Gulf and Europe
One week
Start for a bench-ready role. Recruited roles take three to six weeks
Roles and seniority
Every role we staff, and how quickly each one starts.
Lead time runs from the point the shortlist is agreed to a named person working on your backlog. Bench-ready roles start within a week. Recruited roles take three to six weeks.
| Role | Junior | Mid | Senior | Lead |
|---|---|---|---|---|
| Salesforce developer | Within a week | Within a week | Within a week | Three to six weeks |
| Salesforce administrator | Within a week | Within a week | Within a week | Three to six weeks |
| Salesforce QA engineer | Within a week | Within a week | Within a week | Three to six weeks |
| Full-stack developer | Within a week | Within a week | Within a week | Three to six weeks |
| Mobile developer | Within a week | Within a week | Three to six weeks | Three to six weeks |
| AI and machine learning engineer | Within a week | Within a week | Three to six weeks | Three to six weeks |
| QA engineer | Within a week | Within a week | Within a week | Three to six weeks |
| DevOps engineer | Within a week | Within a week | Three to six weeks | Three to six weeks |
| Business analyst | Within a week | Within a week | Within a week | Three to six weeks |
| Project manager | Three to six weeks | Within a week | Within a week | Three to six weeks |
| UI and UX designer | Within a week | Within a week | Within a week | Three to six weeks |
Lead times assume a standard commercial process. Where a role needs a specific domain, such as CPQ pricing or offline sync on a live field application, we say so at shortlist rather than at onboarding.
Seniority
What each band actually means.
Seniority is matched to the risk in the work. A production quoting path or a data migration is not junior territory, and we will say so before you ask.
| Band | Experience | What they own | How the work is checked |
|---|---|---|---|
| Junior | One to two years | Defined tickets inside an established pattern | Work reviewed by a senior engineer before it merges |
| Mid | Three to five years | Features end to end, including tests and release notes | Peer review, with design decisions checked by a senior |
| Senior | Six to nine years | Technical design, production diagnosis and review of others | Accountable for the design, reviewed by the practice lead |
| Lead | Ten years or more | Architecture, delivery planning and the standard a team works to | Reports against outcomes agreed with you |
The bench
A representative view of the bench.
Profiles are shown by role, seniority and stack, and are indicative of the shape of the team rather than a live availability feed. Current availability against your roles is confirmed on the first call. People are proposed by name once a requirement is agreed, and never published here.
Salesforce developer
- Apex
- Flow
- Experience Cloud
Available now
Salesforce administrator
- Permissions
- Sharing model
- Data quality
- Release
Part allocated
Salesforce QA engineer
- Regression
- Apex test classes
- Release verification
Available now
Full-stack developer
- Architecture
- Node
- React
- AWS
On request
Full-stack developer
- React
- Node
- PostgreSQL
- APIs
Available now
Full-stack developer
- TypeScript
- React
- REST
Available now
Mobile developer
- React Native
- Offline sync
- iOS and Android release
Within a week
AI and machine learning engineer
- Extraction pipelines
- Model evaluation
- Python
- Vector search
Within a week
AI and machine learning engineer
- Python
- Prompt and retrieval design
- Data pipelines
Available now
QA engineer
- Test strategy
- Playwright
- API testing
Part allocated
QA engineer
- Manual test execution
- Defect triage
Available now
DevOps engineer
- CI and CD
- Terraform
- AWS
- Observability
Within a week
Business analyst
- Requirements
- Process mapping
- Acceptance criteria
Available now
Project manager
- Delivery planning
- Reporting
- Risk and dependency management
Part allocated
UI and UX designer
- Product UI
- Design systems
- Prototyping
Available now
Roles not shown here are staffed on request from the same selection process. Tell us the requirement and we will confirm availability before you commit to anything.
Selection
How people are selected and vetted.
The same process applies whether someone joins a client engagement in their first week or their fifth year. Nobody reaches a client system on a recruiter's recommendation alone.
01
Technical screen
A working problem in the language and platform the role calls for. Reviewed by an engineer who does that work, not by a recruiter.
02
System interview
Design and diagnosis on a realistic estate. We look for how someone reasons about a fault they have not seen before.
03
Communication check
A written and spoken exercise against a client scenario. Clear written English is a requirement of every role, not a bonus.
04
Reference and paperwork
Employment references, identity verification, and confidentiality and intellectual property assignment signed before any client system is touched.
Speed to start
From requirement to working engineer, in a week for a bench-ready role.
The route from a role description to a named person on your backlog. The interview stage is yours, run on your criteria, not a formality we run on your behalf.
01
Requirement
Send the role, the seniority, the stack and the working hours you need covered. A short call is usually enough.
02
Shortlist
Anonymised profiles against your requirement, with experience, stack and availability. No generic bench list.
03
Your interview
You interview the shortlist yourself, on your own criteria. Nobody joins your team without your agreement.
04
Onboarding
Access, tooling and first tickets in week two. The first fortnight is a defined block of work you can judge.
Timezone
Galle sits at GMT +5:30, which is the useful part of the map.
Far enough east to cover the Australian and Asian working day, far enough west to hold a real overlap with Europe. Overlap hours are agreed in writing before an engagement starts.
| Region | Difference from Galle | Overlap in a normal working day |
|---|---|---|
| Eastern Australia | Four hours and thirty minutes ahead | Up to six hours with an agreed early start in Galle, covering their full afternoon. |
| Western Australia | Two hours and thirty minutes ahead | Close to the entire working day, with no shift arrangement needed. |
| Singapore, Hong Kong and Malaysia | Two hours and thirty minutes ahead | Close to the entire working day, with no shift arrangement needed. |
| Gulf states | One hour and thirty minutes behind | The entire working day, including their morning stand up. |
| Western and Central Europe | Three and a half to four and a half hours behind | Four to five hours, covering their morning and our afternoon. |
| United Kingdom and Ireland | Four and a half to five and a half hours behind | Three to four hours as standard, five with an agreed later finish. |
| United States, east coast | Nine and a half to ten and a half hours behind | Written handover overnight, plus an agreed call window in our evening. |
English as a working language
Every engineer we place works in English, written and spoken. Sri Lanka teaches English throughout school and uses it as the language of business and higher education.
- Written English assessed before anyone is placed
- Tickets, pull requests and documentation written to your standard
- Client-facing calls handled directly, without a translator in the middle
Your hours and your ceremonies
Overlap hours are agreed in writing at the start of the engagement and held to. Start times in Galle shift to suit the account.
- Daily stand up in your timezone
- Your sprint cadence, your planning and your review meetings
- Sri Lankan public holidays notified in advance
Escalation outside the overlap
Production incidents do not wait for the overlap window. Each engagement has a named escalation path and an agreed response expectation.
- Named escalation contact on our side
- Response expectation written into the engagement
- On-call arrangement where the system warrants it
Continuity
Cover, rotation and the knowledge that comes with them.
The risk in an offshore team is not capability. It is what happens when a person is away, or leaves. We plan for both from the first week.
Cover for leave and illness
Every engagement has a named second who already has access and context. Cover is arranged before leave is approved, not after it is taken.
- Named backup on every engagement
- Planned leave notified at least two weeks ahead
- Unplanned absence covered the same working day
Rotation and replacement
If someone rotates off, the replacement works alongside them before the handover completes. You approve the incoming person the same way you approved the first.
- Overlap period before anyone leaves the account
- You interview the replacement
- No silent substitution, ever
Knowledge that stays with you
Work is documented as it is done, inside your repositories and your knowledge base. What an engineer learns about your system belongs to you.
- Decisions recorded in your tooling, not ours
- Runbooks and diagnosis notes kept current
- Handover pack written before an engineer rotates off
Next step
Tell us the roles and we will send the shortlist.
Send the role, the seniority, the stack and the hours you need covered. You will get anonymised profiles and a start date, then you interview.