Confirmed on the employer's own hiring board on Nov 17, 2026. First seen by Alion on Nov 17, 2026. Sage scores A on the Alion truth index.
Domain Services builds the shared capabilities that Sage products run on. Payments and Financial Services is the domain that moves money and manages financial data for the businesses that use Sage.
We build these capabilities once, so that several Sage products in several regions can offer them to their customers. The platform runs across multiple clouds and regions and handles billions of records. Correctness isn't negotiable here: a retry that isn't idempotent, or a ledger entry that doesn't reconcile, becomes a customer's problem.
About the role
As a Senior Engineer, you'll lead the ambiguous, cross-system and compliance-critical engineering in our domain, and you'll be trusted to release that work on your own judgement. You'll work across your pod and the neighbouring pods your changes touch. You'll decide how deeply AI-produced changes need human review, and you'll make the rest of the team better at building this way.
How we build
We're an AI-native engineering team. AI coding agents do most of our implementation. Engineers decide what gets built, give the agents the right context, and are accountable for what ships.
Context is engineered. Specifications, decision records, conventions, agent instructions and repository memory live alongside the code. We build and maintain them as carefully as the code, because they decide what the agents get right.
Verification is automated. Every change passes through a verification pipeline of tests, contract checks, static analysis and policy checks before release. We treat that pipeline as production code.
Review depth follows risk. Evidence from the pipeline and human review together decide what can be released.
This is a software engineering role. You won't be training models. You'll be building a regulated, high-scale platform with AI as your main tool.
You may be a good fit if you
Typically have 6+ years building and running production backend or distributed systems, or equivalent depth, including leading complex cross-system work from design to production.
Reason carefully about data modelling, state transitions, idempotency, consistency and failure recovery.
Have made AI coding tools central to how you deliver, and can show the context and verification you built around them, where you trusted them, where you didn't, and why.
Have led incidents, migrations or schema changes on systems where mistakes are expensive.
Explain technical risk in terms that product and business partners can act on, and challenge decisions with evidence before committing to them.
Have coached other engineers and can point to how their judgement grew.
What will make you stand out
Financial services. Experience with payments, banking or lending systems, such as ledgers, payment flows, reconciliation and integrations with external providers.
Our stack. Our services run on a range of technologies, including C#/.NET, Java and Node.js. Depth in one or more of these is particularly valuable, and we equally welcome strong engineers from other backend languages who are comfortable working across stacks.
Scale and reach. High-volume data systems running across multiple regions or clouds.
Resilience and security. Threat modelling, fault injection and performance testing for systems that can't fail quietly.
Leverage. Tools, automations or agents you built that other teams went on to use.
Location and working pattern
Location: Bengaluru, India.
Hybrid: three days a week in the office.
We encourage you to apply even if your experience doesn't match every line.
Responsibilities
What you'll do
Lead the hard changes. Own regulated logic, integration contracts, schema changes and data migrations across billions of records.
Shape the approach when it isn't clear. Turn an ambiguous problem into a technical design, prove the critical path early, name the dependencies and risks, and agree with Product what's essential and what's optional. Raise it early when the facts change in a way that could move the date.
Work across pods. Coordinate with the pods whose systems or contracts your work touches, and bring in the Architect early when a design crosses an architecture boundary. Explain technical risk in terms Product and Solution Design can act on, challenge with evidence, and commit once a decision is made.
Build for correctness at scale. Design for idempotency, consistency, concurrency, reconciliation and audit across services, clouds and regions.
Set review depth by risk. Decide how deeply each kind of AI-produced change needs human review, back that decision with automated evidence, and explain it.
Engineer the context. Design and maintain the specifications, decision records, agent instructions and repository memory that let AI agents make correct changes across services, and make them reusable by other pods.
Own the verification pipeline. Build the automated checks, such as contract, property-based, reconciliation and fault-injection tests, that prove AI-produced changes are safe to release, and close the gap whenever something escapes.
Run what you build. Lead complex incidents and migrations, always with a tested rollback path, and fix the systemic cause.
Grow other engineers. Review their work and coach the judgement behind it, not just the code.

