Skip to content
DevBatch

Careers · Engineers who can prove the work

Anyone can generate the code now. We hire for the harder half.

The scarce skill stopped being how fast you type and became whether you can say what correct means and then stand behind it. That is what we hire for, what we train through, and — for people early in their careers — how you get in the door. Send a brief; we read every one and reply inside five business days when there's a fit.

Send your application →How we operate

Life at DevBatch

Six things that are different working here.

The honest version: senior bench, US time-zone overlap, real payroll, direct client communication, returning-customer cadence, and the discipline to say no to deals that don't fit. That's the day-to-day.

SR
A senior bench, not a junior factory
Every engineer on the bench has 5+ years of professional experience. The vet bar is would I let this person commit unsupervised on day one. You work with peers, not a hierarchy of layers.
Our vet bar →
TZ
Time-zone overlap, not red-eye shifts
Engagements are matched to engineers by time-zone overlap with US business hours. Your standups happen during your daytime, not your sleep schedule. We mean it.
How we match →
LLC
Real payroll, real benefits
DevBatch contracts engineers as employees, not 1099s. Payroll runs through our US entity. Benefits, leave, and a clean tax surface come with the role.
How we contract →
REPO
On the client's tools, on our standards
You ship inside the client's repo, on the client's CI, against the client's standards — but the engineering bar is ours. We don't import a parallel process; we integrate.
Our delivery shape →
DC
Direct communication, no PM theater
Engineers talk to clients. Status comes from the people shipping, not from a layer of account managers translating updates. Slack the buyer, run the standup, own the deliverable.
How we run engagements →
REL
Returning customers, long arcs
Most of our work is with people we've shipped for before. Our longest client relationship is in its eighth year, and every engagement we publish is still running. The team that wins those renewals is the one you're joining.
The track record →

What we believe

Four principles you'll be measured against.

Performance reviews don't run on managerial check-boxes. They run on whether you held the line on these four.

01

Outcomes over hours

We bill by time but we are accountable to ship. If a sprint is going to slip, the engineer raises it the day they know — not at the next status meeting.

02

Senior over junior, always

We don't bill three engineers when two can do the work, and we never push junior talent under a senior price tag. That discipline is yours to carry inside engagements.

03

You enter through verification, not the keyboard

The old apprenticeship — cut your teeth on well-defined tickets — is the exact work that got automated. So people join us at the gates instead. You will learn more about correctness adversarially breaking a hundred generated artifacts than carefully producing three of your own, and it happens to be where the valuable work now is.

04

The deals we don't take

Turning work down is a feature. We turn down Magento engagements, pure project work without expansion, and first-time founders without technical leadership. You join a firm that says no.

Apply

Send a brief. We read every one.

No formal openings posted? Send the application anyway — we keep senior candidates in the pipeline and reach out when a match opens. Five business days for a real reply.

Protected by Turnstile

Not the right fit today? Stay on our radar.

Engineering capacity needs shift quarterly. If you're senior and overlap with US business hours, we want you in the pipeline.

Send your application →Read about the work