Product Engineer / Product Builder - Backend or Full-stack

AI is making software execution faster and more accessible. What remains rare is judgment - knowing what to build, why it matters, which trade-offs to make, and what it takes to turn an idea into real customer and business impact.

At Profitroom, we build hospitality software used by thousands of hotels and millions of guests. Our Product Engineers own technical solutions end-to-end: from understanding the problem and contributing to technical discovery, through implementation and testing, to release, production and continuous improvement.

We are hiring Product Engineers with one of two technical backgrounds:

• Backend-led: your strongest area is PHP, application architecture, business logic, APIs, data and distributed systems. You are comfortable taking responsibility for backend solutions and stepping into other parts of the product when established patterns, collaboration and AI make it practical.
  
• Full-stack: you work across frontend and backend, usually with your strongest edge in TypeScript, Vue.js, user journeys and UX. PHP and Laravel are part of your regular work - not an occasional favour handed over to another team.
  

You do not need identical depth across every part of our stack. We expect strong engineering foundations in your primary area, enough range to deliver meaningful outcomes, and the judgment to recognise when to work independently, when to collaborate and when specialist depth is genuinely needed.

The Product Manager owns product direction and the what and why. You own the technical how - and remain responsible for the quality of what reaches production.

The builder drives; the PM steers. This is what we mean when we say Product Engineer. It is not just a title - it is a way of working.

Depending on the product and your area of focus, you will work with:

PHP · Laravel · Symfony · TypeScript · JavaScript · Vue.js · Tailwind · Pinia · REST APIs · MySQL / MariaDB · MongoDB · Redis · RabbitMQ · Microservices · CQRS · Event Sourcing · Docker · Kubernetes · GitLab CI/CD · Claude Code · MCP servers · AI agents

We do not expect every candidate to be equally experienced with every technology listed above.

• 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

• 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

• Remote-first collaboration model
  
• International technology and product projects
  
• Flexible project collaboration setup
  
• Planned service breaks aligned with contract terms
  
• Opportunity to collaborate with experienced product and technology teams
  
• Opportunity to access selected knowledge-sharing initiatives

Zakres obowiązków

• End-to-end delivery: depending on your background, this may mean leading backend services or shipping complete user-facing features across frontend and backend
• Technical discovery: validating feasibility, identifying constraints and shaping the technical approach before the scope is locked
• Technical decisions: selecting solutions that balance customer value, delivery speed, maintainability and operational risk
• Production quality: testing, releasing, monitoring and staying close to the solution during rollout and hypercare
• AI-augmented development: Claude Code is our daily driver; MCP servers, custom agents, skills and internal tooling are part of the real workflow
• Close collaboration with Product Managers, QA and other engineers: you contribute context and trade-offs instead of waiting for a fully specified ticket
• Continuous improvement: you notice recurring problems and leave products, systems and engineering practices better than you found them

Wymagania

Your technical home is the backend. We expect:

• Strong commercial experience with PHP and Laravel or Symfony
  
• 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 TypeScript, JavaScript and Vue.js
  
• Experience with component architecture, state management, performance and maintainable frontend systems
  
• Practical knowledge of Tailwind and Pinia, or the ability to transfer relevant experience from comparable tools
  
• Commercial experience with PHP and Laravel
  
• 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.

We do not expect every candidate to be equally experienced with every technology listed above.

Hands-on experience with Claude Code, Cursor or an equivalent AI coding environment 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.

• 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

Tech stack

• PHP
• Laravel
• REST API
• Microservices
• Docker
• JavaScript
• TypeScript
• API
• Tailwind
• Symfony
• Vue.js
• MySQL
• MongoDB
• Redis
• RabbitMQ
• Kubernetes
• GitLab CI
• AI
• Design System
• Event Sourcing
• CQRS