Tech Lead

We are the digital backbone of OutSystems' growth — building the enterprise applications, integrations, and digital products that run the company's operations and accelerate it into the AI-powered era. We work in small, high-autonomy teams of two to five people, each with a clear mission and the authority to ship. We take both craft and speed seriously, and we expect the people who join us to do the same.

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.

The Behaviours We Are Looking For

• You evaluate at the system level. Your first question about any piece of work is not 'does it run?' but 'is it right?' — architecturally, strategically, and in the context of everything else the team maintains.
• You act as a role model for best practices. You define good software architecture principles and methodologies, seek out the knowledge to make informed decisions aligned with the company's vision, and never propose quick fixes that ignore the future.
• You strive for the optimal solution but understand the trade-offs. You know when to stretch the boundaries to hit a business objective, and you never let tech debt go unacknowledged. You are neither rigid nor careless.
• You have a global understanding of the technology, and you use AI to move faster. You research, you network with peers, and you keep an open mindset for new technologies — then you put that knowledge into practice rather than restricting yourself to what you already know. AI tools are part of how you build and how you expect the team to build, not an occasional shortcut, and you stay curious across the whole landscape — AI, integrations, other platforms — reaching for whatever fits the business problem rather than forcing every problem through the tools you already know.
• You align with the business rather than defer to it. You work with product owners and stakeholders to understand the real problem, foster active communication, and challenge requests that do not support the business goal — instead of blindly accepting what you are told.
• You care about the team, not just the deliverables. You help the team overcome difficulties rather than absorbing every problem yourself or ignoring the pains they are carrying.
• You adapt your communication to your audience. You make sure the message lands — with technical and non-technical people alike — rather than using one style for everyone.
• You respect what is already running. You understand that live systems have users who depend on them, and you extend them with the same care you would apply to anything new — which means you understand them before you change them.

Experience

• 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

• Bonus

• 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

• 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