Software Engineer -1727

Software Engineer at Judiciary

About the role

We are hiring a Software Engineer to develop and support our portfolio of software products. The role suits an engineer who thinks rigorously about quality, takes ownership end-to-end, and can get onboard with how we build software here: AI supports our work — we own every decision.

How we build

We deliberately favour simple, boring technologies: Go, PostgreSQL, containers, and minimal JavaScript dependencies. We're optimising for systems that are easy to reason about, easy to operate, and still maintainable years from now. We prefer to "make impossible states impossible" rather than rely on continued diligence.

AI supports our work — we own every decision. The thinking, the design, the judgement, the call on whether something is right: that comes from the engineer. The execution can lean on AI as far as it's useful. We don't outsource decisions to a model, and we don't avoid AI out of purism either. You own what ships.

We're direct with each other. Feedback is candid, recognition is earned.

What you'll do

• Design, build, and support software products that underpin Judiciary's work

• Take problems from ambiguous brief through to production — including testing, deployment, monitoring, and incident response

• Participate in design discussions and code reviews; advocate clearly for technical positions and update your view when the evidence warrants it

• Identify improvements to systems, tooling, and ways of working — and drive them through

What we're looking for

• Sharp engineering taste and sound judgement — we care about this more than years of experience with any particular popular stack

• Strong fundamentals: automated testing, version control, CI/CD, observability, and secure-by-design thinking

• Comfort with (or genuine appetite for) Go, PostgreSQL, and container-based deployment; a preference for boring, durable technology choices

• Ability to discuss and defend technical solutions robustly while remaining genuinely open to being persuaded

• A problem-solving orientation — you go after root causes, not symptoms

• High initiative: you spot what needs doing and get on with it without waiting to be told

• Effective collaboration with engineers and non-technical stakeholders