[Hiring] OutSystems Tech Lead @OutSystems

Role Description

You will join an existing team and take technical ownership of a portfolio of live OutSystems products and SaaS, while leading the delivery of new capabilities that solve the organisation's most important problems. This is a hands-on role. You write code, not just review it — you stay close enough to the work that your standard for correctness is earned, not assumed.

This is a role for someone who commits to the outcomes and success of their work. You take responsibility for the quality of what is already running and correctness of everything new that gets built. Those two things reinforce each other — the same standard of judgment that protects live systems is what makes new systems worth building.

Most of your focus — roughly seventy percent — will go into innovation: new applications, new integrations, new capabilities that did not exist before. The remaining thirty percent keeps the existing portfolio healthy, coherent, and evolving. That balance is a principle, not a ceiling: when a live system needs attention, it gets it.

What You Will Own

• The technical architecture — you design and build system architecture across the OutSystems estate based on real business needs and drivers, and you own the development principles the team works against.
• The quality bar for everything the team ships — new features and live systems alike. You are the final call on production readiness, and you guarantee overall delivery quality and OutSystems engineering behaviours.
• Technical direction of a small, high-autonomy team — not through process and approvals, but through a clear standard of correctness that everyone can verify their work against.
• Portfolio integrity across built-for-purpose OutSystems applications — understanding the existing applications well enough to extend them without accumulating hidden debt, and well enough to know when something needs to be rebuilt rather than patched.
• The ecosystem view — understanding the key systems and integrations that surround your applications and the role each plays, rather than restricting your attention to your own modules.
• People growth — mentoring the team, working on individual strengths and weaknesses, and inspiring commitment while keeping expectations aligned.
• Fast validation of new approaches — when there is uncertainty about a technology, a pattern, or an architecture, you explore quickly and return with a clear recommendation rather than committing the team to an untested path.

Qualifications

• Proficiency with OutSystems ODC and O11 — hands-on, production-grade experience across both platforms (required)
• Minimum 3 years of OutSystems development experience, with at least 1 year leading technical delivery as a Tech Lead (required)
• Strong experience in enterprise and backend application development, process design, and project delivery practices, with a clear grasp of the trade-off between technical debt and speed (required)
• Technical skills in architecture patterns, solution design, and application performance (required)
• Active use of AI-augmented development in real work — Claude Code, Cursor, Copilot, Mentor, or similar — as a core part of how you build
• Fluency in English, written and spoken (required)
• Degree in computer science or another technical related field

Requirements

• Experience integrating LLMs via API into enterprise applications
• Experience with MCP (Model Context Protocol) server creation and integration
• Experience with Agile Scrum methodology
• Experience working in larger, multi-team engineering environments, where coordination and clear ownership matter across group boundaries
• Prior experience in small, high-autonomy teams where every person's judgment is tested daily

This Is Not For You If...

• You want to be "only" an extra coder on the team, and treat anything outside your own modules as somebody else's problem
• You restrict your area of knowledge to your own applications and technologies
• You are rigid and inflexible, or you let tech debt accumulate unacknowledged
• You accept what product owners tell you without seeking context
• You treat maintaining existing systems as beneath the role you want
• You need a large team or formal approval layers to feel like you are doing real leadership
• You're loyal to your favourite tools and slow to try new ones
• You've stopped being curious about anything outside your own stack

Growth Path

This is a senior role, so growth here is less about climbing and more about widening your reach. Tech Leads who thrive tend to move in one of a few directions: broadening from one team's architecture to setting technical direction across the Digital estate; deepening into principal-level ownership of a critical domain; or, for those drawn to the people side, growing toward engineering management.

And because we are customer zero for the OutSystems platform — building mission-critical products on it every day — there is a path few OutSystems roles anywhere can offer: your hands-on experience becomes direct feedback to the product teams, shaping where the platform goes next. You’ll have a chance to engage with people who have taken each of these routes.

Why Join

You will take technical ownership of live OutSystems products that people across the company depend on every day — on both ODC and O11 — in a company that builds the platform you work on. You're expected to bring the newest tools and technologies into how the team works — not to wait for permission to try them.

The small-team model is not a future ambition; it is how this team already operates.

You will have more autonomy, more architectural leverage, and more direct impact than in any traditional engineering leadership role — and a front-row seat to how enterprise software on OutSystems is evolving into the AI-powered era.