Product Engineer / Product Builder - Backend or Full-stack - Employment Contract

You'll thrive here if

• You have shipped software used by real customers and stayed close enough to know what worked, what broke and what needed to change

• You want to understand the customer and business problem before deciding how to solve it

• Owning a problem end-to-end feels more natural than executing a fully specified ticket

• You can explain a technical trade-off to a Product Manager and a business rationale to an experienced engineer

• You have opinions about quality, and your definition of it goes beyond passing code review or handing work over to QA

• AI tools feel like a natural extension of how you think and work - not something you use only because your employer expects it

• You are willing to work outside your primary technical area when it helps the team deliver a better outcome

• You ask "is this worth building?" and "what outcome are we trying to create?" before diving into implementation

Your technical home is the backend. We expect:

• Strong commercial experience with

• Experience designing backend systems, not only implementing predefined endpoints

• Strong understanding of business logic, data modelling, REST APIs and integrations

• Experience with microservices, event-driven systems or other distributed architectures

• Practical knowledge of relational and non-relational databases, caching and message queues

• Familiarity with Docker, CI/CD and production infrastructure

• Openness to working with JavaScript or TypeScript and contributing outside the backend when the task requires it

We do not expect you to be a frontend specialist. We do expect you to care about the entire product outcome rather than treating the API boundary as the end of your responsibility.

You deliver across the stack, with particular strength in frontend engineering and user experience. We expect:

• Strong commercial experience with

• Experience with component architecture, state management, performance and maintainable frontend systems

• Practical knowledge of

, or the ability to transfer relevant experience from comparable tools

• Commercial experience with

• Confidence working with APIs, business logic, databases, caching and backend integrations

• UX sensibility: you notice interaction problems, accessibility issues and inconsistencies before customers report them

• The ability to deliver frontend and backend changes as part of the same feature

This is not a frontend-only position. PHP and Laravel will be a regular part of your work.

is important to us.

We are especially interested in people who use AI for more than autocomplete: technical discovery, implementation across unfamiliar parts of the stack, test generation, debugging, codebase exploration, specification-driven development and building repeatable engineering workflows.

Experience creating MCP servers, agents, skills or internal AI tooling is a strong advantage.

Bonus points

• You have built and shipped a side project for yourself or real users

• You use AI tools independently and actively develop your own workflows

• You have built an MCP server, agent or another tool that solved a real problem

• You have worked with Event Sourcing or CQRS in a production system

• You have contributed to a design system or component library

• You have designed solutions involving caching, queues, service boundaries or complex integrations

• You can show a product or feature you owned from the initial problem through to production outcomes

Probably not for you if

• You are most comfortable when every decision and implementation detail has already been specified

• You want a strictly backend-only or frontend-only role and consider the rest of the product someone else's responsibility

• Your definition of "done" ends when the code is merged

• You consider testing and production quality primarily the QA team's responsibility

• Your hands-on AI experience is limited to autocomplete and occasional summaries

• You prefer receiving tasks over understanding and owning the problem behind them