Three teams. One product. Your architecture.
Some roles let you influence the technical direction. This one hands it to you.
As our Technical Delivery Lead & Product Architect , you are the technical authority for a software product built by three engineering teams. You set the architecture, define the engineering standards and make sure three teams ship as one. You lead two of them directly; you are the customer's go-to technical partner, and you stay close enough to the code to know when something smells.
If you have ever thought, "give me the whole thing and I'll make it work", keep reading.
The role at a glance
Your scope: end-to-end technical direction of one product, built by three engineering teams
Your teams: two teams report to you directly; you are the technical lead for all three
Your counterparts: the customer, our engineers and a third-party vendor team
Your stack: the Microsoft .NET ecosystem
Your mandate: architecture, engineering standards, cross-team coordination and technical delivery
What you'll own
The architecture and the big calls
Own the product's end-to-end technical direction and solution architecture.
Lead architecture reviews, design discussions and the major technical decisions.
Guide teams on .NET architecture, application design, APIs, integration, testing, performance, security and maintainability.
Balance new features, technical debt, scalability and reliability – so the product is still a joy to work on in five years.
Stay hands-on enough to give practical guidance and to challenge implementation decisions when it matters.
The people and how they grow
Lead two engineering teams directly and provide technical leadership to all three.
Mentor Tech Leads and Senior Engineers into the next stage of their careers.
Create clear ownership of teams and system components, so people can work autonomously within one consistent framework.
Step in when complex technical issues or dependencies get stuck.
The delivery, three teams, one engine
Make three teams across company boundaries work as one engineering organization.
Coordinate dependencies, integrations, shared components and releases.
Shape planning, estimation, prioritization and sequencing with your technical input.
Spot risks and blockers early and clear them.
Set the bar for coding, code review, testing, CI/CD, documentation, observability and quality.
The customer and the vendor - a seat at the table
Be the customer's primary technical counterpart in architecture, design and planning discussions.
Explain decisions, risks and trade-offs in a way everyone understands.
Give the vendor team technical direction and governance, and make sure their work fits the architecture and standards.
What you bring
You have built and shipped production systems that people rely on and you have led the teams who built them.
Significant experience designing and delivering production software systems.
A track record as Technical Lead, Principal/Staff Engineer, Engineering Manager, Solution Architect or in a similar role.
Deep, hands-on expertise in the Microsoft .NET ecosystem.
Proven ownership of the architecture and technical direction of a product or platform.
Experience leading several engineering teams, or teams sharing one codebase.
Strong command of software architecture, distributed systems, APIs, integrations, scalability, security, reliability and maintainability.
Modern engineering practice as second nature: source control, code review, automated testing, CI/CD, observability and production support.
The range to switch between the architecture whiteboard and a concrete pull request in the same afternoon.
Clear communication, confident decision-making and strong stakeholder management – with internal teams, customers and third-party vendors alike.
Why Agile Actors
European Software Teams. Built To Deliver. Since 2012 we have augmented and empowered engineering teams for international and Greek clients – and we have built a place where professionals don't just…