Nine salaried engineers · Pune, India
The engineers
Everyone who would work on your project, with what they have shipped and the date they come free. Nobody here is sourced after you sign, and you interview whoever is proposed before anything is agreed.
Most agencies show you a sales engineer and staff the work later. You find out who actually writes your code in week three, and you have no say in it.
Publishing the bench costs us something, competitors recruit from this page, and a client can ask for a specific person we had planned elsewhere. We think you should be able to see who you are buying.
Photographs are the one thing we leave off. That is the team's choice, not a policy, and the GitHub link does the verifying a photo never could.
Availability updated every Monday
The bench
All nine, and what they have shipped
Names are withheld on this public page and shared on the first call: the GitHub history comes with them.
Subscription billing, multi-tenant schemas and the money paths. Reviews every pull request on his team himself.
Laravel 12 
Vue 3 
PostgreSQL AWS Strangler migrations off CodeIgniter: one router, both frameworks live, no big-bang rewrite.
CodeIgniter 
PHP 8.4 Rector 
MySQL 8 Runs our headless builds, and keeps the editor experience simple while the front end changes underneath it.
Astro 
Redis Multisite Large catalogues and the checkout path. HPOS, index strategy and the plugin cull that usually matters more than either.
WooCommerce 10 HPOS 
Stripe Subscriptions Queue topology and throughput. Horizon, backoff, dead-letter handling, and the profiling that finds the real bottleneck.
Redis Octane SQS Integrations specialist, Stripe, NetSuite and three shipping carriers, every call idempotent and replayable.
Stripe OpenAPI Webhooks Plugin work that survives core updates, and the audits that prove which inherited ones will not.
Builds the internal tools clients stop asking their own team for. Ships a Filament panel in a fortnight.
Livewire 3 Filament 4 
Tailwind 4 
Alpine Writes the tests nobody else wants to write, starting with the paths where a wrong number costs real money.
GitHub Actions How we hire
Why the bench is small
Nine engineers is a deliberate number, and we hold it close to that. We hire when someone leaves or when a stack needs real depth, not when demand spikes, because the bottleneck is finding people who will still be here in three years and who review other people's work properly.
If we do not have the right person free, we will say so and tell you when, rather than putting a weaker engineer on it and hoping.
Engineering standards
The bar every commit passes
These are not aspirations. They are configured in CI, so a pull request that misses them cannot merge.
PHPStan level 8
on every new codebase, and level 5 minimum on anything inherited.
70% coverage floor
on business logic. Not a vanity number: the paths that touch money are covered first.
Two-approver rule
on anything touching auth, payments or migrations. Never a self-merge.
Conventional commits
and a written PR template: what changed, why, how it was tested, what could break.
Staging before production
always. Deploys are automated from your main branch, never from a laptop.
Runbook per project
so the person on call at 3am is not reading source to find the queue worker.
Your working day, and ours
Four hours of overlap, every day
Standup is at 9:00am your time, not ours. A written handover lands in your inbox before your morning, so the questions you have at 9am were answered at 6pm the day before.
What you get in writing
Before anyone starts
A twenty-minute interview with the engineer, not a salesperson
Their GitHub history, and two references from past clients
Ten working days risk-free before you owe anything
A replacement inside five days if the fit is wrong, at no cost
The same person for the whole engagement, named in the contract