Principal Software Engineer

About the role

You will write production code, design the systems it belongs to, and stay accountable for how it behaves after release. Most engineering roles stop at "feature complete." This one does not. You will define what a service looks like, build it, prove it works through automated testing, ship it through our delivery pipeline, and own its behaviour in production. You will set the technical standard for application engineering across the organization, architecture, code quality, and test discipline — and you will do it by building, not by reviewing from a distance. This is an AI-augmented role. We expect coding agents to be part of how you work daily, and we expect you to define what responsible, verifiable use of them looks like here.

Responsibilities

• Ideation through design: turn ambiguous business problems into technical direction; produce architecture and interface designs that other engineers can build against; make and defend technology selection and build‑vs‑buy decisions.
• Full‑stack implementation: design and build front‑end applications and the services, APIs, and data layers behind them; write production code at a standard that raises the bar for the engineers around you.
• Test strategy and coverage: own the automated testing approach for your systems; enforce unit test coverage as a merge gate; build integration test suites against real service contracts; author and maintain functional and end‑to‑end browser tests in Playwright, keeping them fast and non‑flaky.
• Delivery to production: package your services as containers; author deployment configuration for your workloads and promote changes through the GitOps pipeline; be fluent in the platform — reading and modifying Terraform and Kubernetes manifests that describe your service.
• AI‑augmented delivery: use coding agents as a core part of how you work — decompose problems into agent‑executable units, direct multi‑step implementation, and review generated output with the same rigor you would apply to a strong junior engineer's pull request; deliver scope that would conventionally require a larger team and establish guardrails, review standards, and verification practices that let other engineers do the same safely.
• Security and compliance as code: write code that clears automated SAST, DAST, dependency, secret, and container scanning on every commit; remediate findings at the source; design services so that authentication, authorization, encryption, and data handling meet control requirements by construction.
• Auditability and evidence generation: instrument services to emit structured, tamper‑ev