Senior-only teams
You work alongside engineers who can challenge an architecture, explain a trade-off, and own production consequences. We do not build teams around layers of supervision.
Careers
We hire engineers who have opinions.
6+ years of experience, deep care for craft, and the ability to talk to clients directly.
What working here is like
The operating terms are explicit.
You are hired for judgement, not ticket velocity. The team stays small enough that decisions, delivery, and accountability remain connected.
Direct client contact
The engineer closest to the problem joins the conversation. You explain decisions in plain language, ask for missing context, and do not route every technical question through account management.
Architecture before code
One-way-door decisions are written down before implementation. You are expected to make assumptions visible, identify operational risk, and leave a system another senior engineer can understand.
Products you can point at
Client systems are not the only output. Our themes, plugins, and PHP products keep us responsible for documentation, upgrades, compatibility, support, and the maintenance cost of our own decisions.
Open roles
Current engineering openings.
Role availability changes. Every application is read by someone involved in delivery, not screened by an automated keyword score.
03 open rolesHiring process
Four steps. No interview theatre.
The process is designed to reveal how you think, communicate, and finish work. Trial tasks are paid because useful engineering should not be extracted for free.
CV and work
We review the systems you have shipped, the decisions you owned, and whether your experience matches the role.
Technical conversation
A working session with senior engineers. Expect architecture trade-offs, debugging judgement, and direct questions about production.
Paid trial task
A bounded task with written acceptance criteria, realistic constraints, and enough context to show how you work.
Paid at an agreed rateOffer
Role, compensation, working hours, probation terms, equipment, and start date are stated in writing before you accept.
Start with evidence
Send us your CV.
Include two or three systems you can discuss in detail, what you personally decided, and what changed after the software reached production.
Send us your CVPDF preferred · links welcome