Software Engineer in London

Naverion is seeking a software engineer at experienced-junior to mid-level to deliver defined components across its quantitative decision platform. Working directly with the CTO, the engineer will implement, test, document and support the controlled release of production software.

The role suits someone who can progress bounded work independently and, at the upper end of the range, own defined components through the full SDLC. Architecture, methodology, clinical interpretation, security design and production approval remain with the CTO and relevant specialists.

Naverion is developing an auditable decision platform combining financial engineering, actuarial analysis, simulation, healthcare-treatment evaluation and long-term decision optimisation.

Qualifications

• Candidates should normally hold a bachelor’s degree at UK 2:1 level or above, or an equivalent international qualification, in Computer Science, Software Engineering, Mathematics, Statistics, Operational Research, Physics, Engineering, Data Science, Actuarial Science, Financial Mathematics or a closely related discipline.
• Candidates without a degree may be considered where substantial commercial experience, professional qualifications or a strong production-software portfolio demonstrates equivalent capability.
• A relevant master’s degree is desirable but not required.
• No actuarial or clinical qualification is required.

Experience

• Typically three to six years of commercial software-engineering experience, including delivery of meaningful features or components to production.
• Stronger evidence of capability may offset a shorter period in role.

Essential Technical Skills

• Python for data processing, quantitative analysis and production workflows.
• SQL and PostgreSQL.
• REST APIs and versioned data contracts.
• Git and pull-request workflows.
• Automated unit and integration testing.
• Modular design, debugging and service integration.
• Commercial cloud experience with Azure or AWS, including deployment, identity and access, secrets, monitoring and CI/CD.
• Working within a controlled software development life cycle.

Quantitative Capability

The candidate must be numerically confident and able to implement clearly specified calculations involving probability, statistics, financial mathematics, portfolio modelling, simulation, time-series data, actuarial calculations or healthcare costs and outcomes. The engineer is not expected to originate or approve methodology. They must implement approved specifications, test numerical behaviour and elevate ambiguity before proceeding.

Current Workstreams

• Quantitative financial and actuarial calculation engines.
• Portal, API, PostgreSQL and audit-service integration.
• Healthcare evidence extraction and hosted-LLM workflows.
• Azure deployment, monitoring and operational controls.

Key Responsibilities

• Implement well-defined product and platform components within an agreed design.
• Build and maintain APIs, integration services, data models and ingestion routines.
• Implement approved quantitative requirements and create deterministic regression tests.
• Maintain data contracts, schema migrations, validation rules and audit evidence.
• Contribute to hosted-LLM extraction and evaluation workflows.
• Prepare concise technical notes, runbook updates and release evidence.
• Diagnose routine defects and support controlled deployments and verification.
• Identify unclear requirements, assumptions and technical risks early.

Software Development Life Cycle

Assigned work must progress through requirement clarification, design review, implementation, automated testing, peer review, integration, release preparation and post-deployment verification. Every material change must remain traceable from requirement and acceptance criteria through code, tests, review, deployment and verification. Testing and documentation are part of delivery.

Assurance and Governance

• Implement only approved, versioned model specifications.
• Test boundary conditions, failure cases and agreed golden results.
• Preserve model, assumption and input-data versions in outputs.
• Follow agreed privacy, access-control and environment boundaries.
• Preserve source references and human review for healthcare or LLM-derived information.
• Escalate any change affecting methodology, clinical interpretation, security or previously issued results.

Role Boundary

The engineer owns defined component delivery within an agreed architecture. The CTO retains authority for overall architecture, quantitative methodology, clinical boundaries, material security decisions and production-release approval.

Success in the First Six Months

• Deliver defined production components with complete tests and documentation.
• Use Naverion’s review, release and verification process reliably.
• Add useful regression coverage to a quantitative or data workflow.
• Contribute safely to an API, database schema or integration service.
• Demonstrate sound judgment about when to proceed and when to escape.

Ideal Candidate

The strongest candidate combines disciplined engineering habits with numerical confidence, clear written communication and the maturity to work safely in a high-assurance environment. They can deliver defined work without constant supervision, take ownership proportionate to experience and do not make silent assumptions in quantitative, healthcare, security or data-governance work. The role offers structured exposure to technically demanding products and a clear path toward mid-level ownership while working directly with the Naverion CTO and specialist contributors.