Design Java and Spring Boot services with clear domain boundaries, APIs, data ownership, and failure behaviour.
Backend and platform engineering · Open role
Principal Backend & Platform Engineer
Design and build the services, data flows, and operating foundations behind products where reliability, security, and change are genuinely difficult.
This role sits at the hard centre of Qubit’s platform work: transactional systems, integrations, event flows, data infrastructure, and the operational controls that keep them trustworthy. You will still work from product outcomes, not an isolated infrastructure backlog.
Build resilient integrations, asynchronous workflows, and event-driven systems using tools such as Kafka.
Make pragmatic decisions about PostgreSQL, search, caching, lakehouse components, and cloud infrastructure.
Establish observability, security controls, deployment patterns, capacity assumptions, and operational runbooks.
Lead migrations and production changes with explicit compatibility, rollout, and rollback plans.
Deep JVM and Java experience in systems that carried meaningful production load or business risk.
A strong model of transactions, concurrency, distributed failure, data consistency, and operational recovery.
Experience making cloud systems observable, diagnosable, and safe for another team to own.
Good architectural judgement without turning architecture into abstraction for its own sake.
The ability to explain system behaviour and trade-offs clearly to product teams and clients.
Probably not for you if
A senior title is the goal, but hands-on ownership is not.
- You prefer platform work disconnected from users and business workflows.
- You reach for distributed complexity before proving it is necessary.
- You consider production operation someone else’s responsibility.
Show us how you think.
Send a short note, relevant work, and one difficult problem you personally owned. Skip the polished cover letter. Specific evidence is more useful.
Apply for this role ← Back to all roles