Asks for

The ad says“API design and gateway concepts — OpenAPI contracts, versioning, and service boundary decisions sufficient to govern API delivery across squads.”
The ad says“Proven people leadership across multiple squads or teams — hiring, coaching, performance management, and building high-performance engineering culture at scale.”
The ad says“System design and distributed systems — working knowledge sufficient to review, challenge, and validate architecture decisions made by the Architect and Tech Leads. Not required to design; required to govern.”
The ad says“Kubernetes, Docker, and Helm — deploy, release, and manage containerised applications in production, including CI/CD pipeline ownership in a cloud-native context.”
The ad says“Engineering quality governance — managing technical debt, balancing quality against velocity, enforcing definition of done, and ensuring production-readiness gates across squads.”
The ad says“Event emission and observability standards — what agents emit, how services are traced, and what healthy looks like from a delivery governance lens.”
The ad says“Kubernetes, Docker, and Helm — deploy, release, and manage containerised applications in production, including CI/CD pipeline ownership in a cloud-native context.”
The ad says“Proven people leadership across multiple squads or teams — hiring, coaching, performance management, and building high-performance engineering culture at scale.”
The ad says“Kubernetes, Docker, and Helm — deploy, release, and manage containerised applications in production, including CI/CD pipeline ownership in a cloud-native context.”
The ad says“Multi-tenant SaaS architecture — delivery and governance implications. Security and IAM concepts beyond OAuth sufficient to validate decisions; Platform Architect owns depth.”
The ad says“OAuth 2.0 and one IDP — production experience sufficient to govern security delivery and validate implementation decisions made by the team.”
The ad says“Event emission and observability standards — what agents emit, how services are traced, and what healthy looks like from a delivery governance lens.”
The ad says“API design and gateway concepts — OpenAPI contracts, versioning, and service boundary decisions sufficient to govern API delivery across squads.”
The ad says“Proven people leadership across multiple squads or teams — hiring, coaching, performance management, and building high-performance engineering culture at scale.”
The ad says“Proven people leadership across multiple squads or teams — hiring, coaching, performance management, and building high-performance engineering culture at scale.”
The ad says“System design and distributed systems — working knowledge sufficient to review, challenge, and validate architecture decisions made by the Architect and Tech Leads. Not required to design; required to govern.”

Description

Trintech is the leader in AI Financial Close Management, helping finance and accounting teams transform the way they work by eliminating manual burdens, strengthening controls, and empowering strategic decision-making.

We are looking for an Engineering Manager to lead the Agent Stream at Trintech’s AI Platform. You will own delivery across multiple Agent Development Squads, each building AI agents that power the Autonomous Financial Close. This is a leadership role that requires equal technical depth and people leadership.

You are the Direct Responsible Individual (DRI) for the Agent Stream — when delivery is off track, you own identifying it, communicating it, and resolving it. You work closely with the Software Architect on technical direction, with Product Owners on backlog sequencing, and with the Director of Engineering on stream strategy and hiring. The right person has strong engineering instincts, is comfortable working within a Human-led Agentic SDLC, and has the credibility to lead a team of senior engineers building production-grade AI agent systems.

What You’ll Do

Engineering Leadership & Delivery

Own end-to-end delivery across all Agent Stream squads — sprint cadence, dependency management, release readiness, and cross-squad coordination.
Be the DRI for Agent Stream outcomes — identify risks early, communicate clearly to the Director of Engineering, and resolve blockers before they affect delivery.
Partner with the Software Architect on technical direction — ratify architecture decisions and ensure squads build on solid foundations.
Work with Agent Stream Product Owners to sequence backlog priorities — bring engineering judgement to product trade-off conversations and own the Agent Stream engineering roadmap in alignment with the platform product roadmap.

People Leadership

Hire, onboard, and develop engineers across the Agent Stream — FTEs and contractors, across all seniority levels.
Build and sustain a high-performance engineering culture. Conduct regular 1:1s, performance conversations, and career development discussions.
Manage performance proactively — recognise high performers, course-correct early, and make hard calls when needed.
Foster collaboration across squads and streams — Agent, Platform, Data, and Intelligence streams share dependencies and require active coordination.

Technical Oversight

Maintain sufficient technical depth to engage credibly in architecture reviews, design discussions, and trade-off decisions. Able to step into code when needed — primary mode is technical oversight, not production delivery.
Review and challenge technical proposals from squad Tech Leads — raise the right questions, identify risks, and validate proposals rather than simply approve them.
Ensure engineering standards are maintained across squads — code review practices, test coverage, observability standards, and production-readiness gates.
Stay current on the AI and agent engineering landscape — bring informed perspectives on tooling, practices, and the Human-led Agentic SDLC.

Who You Are

People Leadership & Delivery Ownership — Primary Gate

Proven people leadership across multiple squads or teams — hiring, coaching, performance management, and building high-performance engineering culture at scale.
Delivery ownership with DRI accountability — experience owning stream or programme-level outcomes end-to-end, including risk identification, stakeholder communication, and resolution.

Technical Depth

System design and distributed systems — working knowledge sufficient to review, challenge, and validate architecture decisions made by the Architect and Tech Leads. Not required to design; required to govern.
Engineering quality governance — managing technical debt, balancing quality against velocity, enforcing definition of done, and ensuring production-readiness gates across squads.
OAuth 2.0 and one IDP — production experience sufficient to govern security delivery and validate implementation decisions made by the team.
Programming experience in at least one language, Python preferred — sufficient to step in, review code, and contribute when needed. Not required to be a primary coder.
Kubernetes, Docker, and Helm — deploy, release, and manage containerised applications in production, including CI/CD pipeline ownership in a cloud-native context.

Awareness

API design and gateway concepts — OpenAPI contracts, versioning, and service boundary decisions sufficient to govern API delivery across squads.
Event emission and observability standards — what agents emit, how services are traced, and what healthy looks like from a delivery governance lens.
Multi-tenant SaaS architecture — delivery and governance implications. Security and IAM concepts beyond OAuth sufficient to validate decisions; Platform Architect owns depth.

Nice to Have

Agent and workflow orchestration patterns — cross-agent handover, Temporal, event bus patterns. Learnable on the job; directional awareness is sufficient for this role.
AI-native SDLC — familiarity with Human-led Agentic SDLC practices and how they differ from traditional software delivery in planning, testing, and release cadence.
Azure certification demonstrating cloud platform depth. Financial close or R2R domain experience to accelerate ramp-up on the business context the platform serves.

At our core, Trintechers stand committed to fostering a culture rooted in our core values – Humble, Empowered, Reliable, and Open. Together, these values guide our actions, define our identity, and inspire us to continuously strive for excellence in everything we do.

All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin or disability.

Asks for

Values

Description