Senior OutSystems Developer

outsystems; Portugal; Presencial; EUR 60 000 - 90 000; Tempo integral

Resumo da oferta

OutSystems in Portugal is seeking a senior engineer to own architecture and delivery of features and integrations across a portfolio of live products and SaaS. You will build new capabilities while maintaining what already runs, with a roughly seventy percent focus on innovation and thirty percent on upkeep, and you will ship end-to-end with minimal supervision.

As a senior engineer, you are trusted to take a problem from a rough brief to a correct, production-ready solution and to raise the bar

Qualificações

• At least 4 years of software development experience, with a minimum of 2 years building on OutSystems (required).
• Hands-on OutSystems experience, ODC and/or O11. Deep platform expertise is welcome.
• Strong backend and integration fundamentals: REST APIs, JSON, authentication patterns, and error handling under real conditions (required).
• Solid grasp of solution architecture and application performance, with the ability to estimate and prioritise your own delivery (required).
• Experience with unit and integration testing and the bug fixing that follows (required).
• Active use of AI-augmented development - Claude Code, Cursor, Copilot, Mentor, or similar - as a core part of how you build, not an occasional shortcut (required).

Responsabilidades

• Own architecture and delivery of features and integrations across live products and SaaS.
• Build new capabilities while maintaining and evolving existing systems.
• Ship to production from build through testing to bug fixing end-to-end.

Conhecimentos

OutSystems

Backend development

REST APIs

System integration

AI-assisted coding

Ferramentas

OutSystems ODC

OutSystems O11

REST APIs

Descrição da oferta de emprego

There are NO limits to your career: come shape the future and be part of a truly unique global culture at OutSystems!

About the OutSystems Digital Team

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.

The Role

You will join an existing team and take ownership of features and integrations across a portfolio of live, mission-critical OutSystems products and SaaS, while dedicating most of your focus to building new capabilities that did not exist before.

The balance we aim for is roughly seventy percent innovation - new applications, new integrations, new capabilities - and thirty percent maintaining and evolving what is already running. That split is a principle, not a rigid rule: when a live system needs attention, you give it. What stays constant is that you own your output end to end, whether it is new or existing.

As a senior engineer, you are trusted to take a problem from a rough brief to a correct, production-ready solution with little supervision - and to raise the bar for the developers working alongside you.

What You Will Own

• Solution design and delivery - you take responsibility for the architecture of your own work, execute it, and support it in production, within the guidelines the Tech Lead sets for the team.
• Features and integrations that ship to production - real users, real consequences, and your name on them; from build through unit and integration testing to the bug fixing that makes them solid.
• Integrations with external systems - connecting OutSystems applications to the wider ecosystem according to the defined architecture guidelines, with attention to correctness and error handling under real conditions.
• Your share of the existing portfolio - understanding the applications the team maintains well enough to extend them without accumulating hidden debt, and knowing when something needs escalating.
• Quality before it merges - you develop and apply the instinct to distinguish code that is correct from code that merely looks plausible, before anything reaches production.
• Shared context that makes the team faster - documenting decisions and patterns, and helping the more junior developers grow through review and example.

The Behaviours We Are Looking For

• You own what you ship. You do not hand something off and move on. You care whether it works in production, whether it holds under load, and whether it solves the actual problem - including in systems you inherited rather than built.
• You distinguish correct from plausible. You have enough experience to know that output which looks right is not always right, and you apply that judgment before anything ships.
• You deliver with quality and to the timeline. You organise, estimate, and prioritise your own work, and you finish what you take on to a standard you would be happy to defend.
• You find a way around walls. When you hit a blocker, you try before you ask. When you do ask, you arrive with what you have already tried and ruled out.
• You share context generously. In a small team, what you know is a shared asset. You document, you flag assumptions, you explain your reasoning, and you help the people around you get better.
• You are honest about what you do not know. You surface uncertainty rather than hiding it behind confident-sounding output.
• You use AI to work faster and better. You reach for it by default and you try the new tool rather than waiting to see if it sticks.
• You solve the business problem with whatever fits. You stay curious beyond OutSystems and explore other technologies when they're the better answer.

Experience

• At least 4 years of software development experience , with a minimum of 2 years building on OutSystems (required)
• Hands-on OutSystems experience , ODC and/or O11 . Deep platform expertise is welcome - but so is a strong engineer from an adjacent stack who ramps fast . We'd rather teach the platform than teach curiosity. (required)
• Strong backend and integration fundamentals: REST APIs, JSON, authentication patterns, and error handling under real conditions (required)
• Solid grasp of solution architecture and application performance, with the ability to estimate and prioritise your own delivery (required)
• Experience with unit and integration testing and the bug fixing that follows (required)
• Active use of AI-augmented development - Claude Code, Cursor, Copilot, Mentor, or similar - as a core part of how you build, not an occasional shortcut (requi