Engineering for Software and Tech Companies
A product company seldom has the number of engineers its roadmap assumes. Recruitment takes a quarter, the backlog grows meanwhile, and the people already on the team spend their evenings on the integration nobody wanted.
We provide additional engineers who join your team as it is. They use your repository, your branching rules, your ticket tracker and your stand-up. Your technical lead directs the work. We look after employment, equipment and continuity on our side.
When a product team runs short of hands
A customer commitment with a date
Sales agreed an integration for a large account, and building it would stall the roadmap for everyone else.
Test coverage that never gets written
Everybody agrees the suite is thin. Nobody has a free sprint to thicken it.
A framework upgrade long postponed
The major version is two behind, security patches are about to stop, and the migration is dull work.
A mobile app the web team cannot staff
Customers want it, and your engineers know React but not the app stores.
Support tickets eating development time
Senior developers spend mornings on bug triage when they should be designing the next release.
A hire that fell through
The candidate accepted elsewhere, and the project they were meant for has already begun.
Jobs that transfer well to an outside engineer
Tasks with clear edges go best. Here are the usual ones.
Third-party integrations
Connectors to payment, CRM, accounting or messaging APIs, including the retry and error handling that documentation glosses over.
Automated tests
Unit, API and browser tests added to existing code, wired into the pipeline so a failing build blocks the merge.
Version and dependency upgrades
Moving to a supported release of the language or framework, one deprecation warning at a time.
Internal admin tools
The back-office screens your support staff need and your product engineers never get round to.
Companion mobile apps
A Flutter or React Native client for an API you already operate.
Pipeline and infrastructure chores
Build caching, container images, staging environments and infrastructure written as code.
Adding an engineer to your team
Describe the work
Send the stack, the kind of tasks and the hours of the day you need overlap.
Meet a named person
We put forward a specific engineer. Your lead interviews them as they would any candidate.
Set a small first task
A real ticket of a few days. It shows code quality and communication better than an interview does.
Settle into a rhythm
Tasks live in your tracker. You receive a written summary each week and a single invoice each month.
Change the size when needed
Hours can go up or down from one month to the next. If someone leaves, a replacement is proposed and you approve them.
Hourly rate by role
Our rates are published. Pick the role and move the sliders for an indicative budget.
Rate card
| Role | Hourly | Monthly* |
|---|---|---|
| Frontend / WordPress | $30 | $4,800 |
| Backend / API | $32 | $5,120 |
| Full-stack | $35 | $5,600 |
| Mobile (React Native / Flutter) | $35 | $5,600 |
| DevOps / Cloud | $40 | $6,400 |
| AI / Automation engineer | $45 | $7,200 |
| QA / Test engineer | $25 | $4,000 |
| UI / UX design | $28 | $4,480 |
*160 hrs/month full-time. Rates are indicative for planning, in USD (other currencies are converted at an indicative rate), and depend on seniority, contract length and timezone overlap. Longer engagements and multi-role teams are discounted — ask.
How we fit into your process
- Commits go to your repository under the engineer's own name
- Your code style, linters and review rules are followed
- Pull requests kept small enough to read properly
- Questions asked in your chat channel, in the open
- Blocked tasks reported the same day
- Access limited to the systems the task requires
- Overlap hours with your time zone fixed in advance
- Intellectual property assigned to you in the agreement
Decisions your company must take
Bringing in outside engineers touches your own obligations. These are for you and your advisers to settle. We hold no attestation you could inherit, and any audit is performed by your auditor.
Your security attestations
If you hold or are working towards SOC 2 or ISO 27001, contractors fall inside the scope. Tell us which controls apply: device rules, access reviews, training.
Customer contracts
Some enterprise agreements require notice or consent before a subcontractor handles their data.
Personal data crossing borders
GDPR and similar laws restrict transfers. The simplest route is that our engineers never see production personal data.
Open-source licences
Your policy on copyleft licences and on adding new dependencies needs to be written down so we can follow it.
Use of AI coding assistants
Whether they are allowed on your code base, and which ones, is your call.
Will extra capacity actually help?
It tends to help when
- Tickets are written clearly enough for a newcomer to pick up.
- A lead has time to review code from one more person.
- The code base has a working local set-up and some tests.
- The shortage is of hands, not of direction.
It rarely helps when
- The product direction changes weekly.
- No one can review, so work would merge unread.
- The real need is a chief technology officer.
- Everything must happen in your own time zone, all day.
Send the stack and a sample ticket
A redacted ticket tells us more than a job description. Include your time zone. Our reply, with a person in mind where possible, follows within one business day.