The Mandate
Veronix is expanding its remote engineering roster for targeted operational infrastructure.
The engineer takes a forensic reconnaissance blueprint, or a development scope provided by the client, and translates it into a production-ready system.
The Role
The engineer is the primary technical operator on the deployment, accountable for 70 to 80 percent of the project's technical execution. Ownership covers the build from initial logic through to final deployment.
The architecture spans four layers.
- 01InterfacePortals and operator dashboards. Accounts, request routing, document generation, and the operational views.
- 02LogicWorkflows and APIs. Deterministic steps, where a specific input guarantees an exact result and record.
- 03DataThe relational model on a managed Postgres store. Strict constraints, access rules, and immutable audit logs.
- 04EdgeLegacy systems and third-party APIs. Modern architecture bound to existing infrastructure, without data loss.
The Tooling
Engagements begin inside a proven architecture. The environment is already standing.
TypeScript and Python are the languages on the build. Next.js carries the interface and the request paths. Tailwind CSS is the UI system. Strict payload validation sits in front of every write.
AI tools are part of how the work is done. Cursor and Claude Code are encouraged; some licences are supplied to the team. An engineer who does not put AI into their workflow is leaving speed on the table.
- TypeScript
- Python
- Next.js
- Tailwind CSS
- Cursor
- Drafting, refactoring, and review. Supplied where the engagement needs it.
- Claude Code
- Encouraged alongside Cursor for the same class of work: faster drafts, clearer traces, tighter review.
The Sequence
Engagements range from rapid internal tooling, measured in days, to a unified operational system, usually two to four months. The pipeline adapts to the engagement. The stages do not.
- 01
Scope and Reconnaissance
For a full overhaul, the principal architect handles reconnaissance. The engineer inherits a forensic blueprint of the bottlenecks. For a direct build, the client provides a development scope.
- 02
Architecture
Tables, keys, and integration contracts are set here, including the distinction between a request and a job.
- 03
Increments
Interface and logic ship together, in modules. Each block is verified against ground truth before the next begins.
- 04
Handoff
Deployment, access transfer, and client sovereignty. The repository, the data, and the operating manuals transfer to the organisation.
- 05
Stabilisation
The engineer remains attached after launch. Real operational load surfaces edge cases, and the audit log is how the system is fortified.
What You Bring
Screening is for production competence, relational logic, and architectural autonomy. A specific degree, or a count of years in a role, is not the measure.
- Production Record
- Complete web applications, not tutorials or samples. Real user data, complex state, and recovery when a write fails.
- Systems Thinking
- Relational schemas, strict audit logs, and a clear sense of when an automated action still needs a person.
- Integration Fluency
- A legacy API or a flat export, mapped into a new model, with writes made idempotent so a retry does not double-book the work.
- Autonomous Execution
- When a client's operation contradicts the model, the logic error is named and the structure is adjusted.
The Ground
This role is remote. On-site reconnaissance stays with Recon.
- Location
- Fully remote. No mandatory days in the London office.
- Site Visits
- None. On-site reconnaissance is handled entirely by Recon.
- Hours
- Full-time work is limited to the United Kingdom and European timezones, so review can happen in working hours. Contractor roles are open in selected countries only. Apply, and we will review the submission.
- Compensation
- Pay and engagement terms are confirmed on the initial call and in the final documents if you are selected. The roster moves quickly; we do not publish fixed figures against roles that are still taking shape.