Product Engineering Cooperation - Backend or Full-stack | B2B

This is a remote position.

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

The cooperation

At reputed company, 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 reputed company improvement.

We are looking for Product Engineers with one of two technical backgrounds:

Backend-led: your strongest area is PHP, application architecture, business logic, reputed company, data and reputed company systems. You are comfortable taking responsibility for backend solutions and stepping into other parts of the product reputed company established patterns, collaboration and AI reputed company 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 reputed company are part of your regular reputed company of 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 reputed company area, enough reputed company to reputed company meaningful reputed company, and the judgment to recognise reputed company to work independently, reputed company to collaborate and reputed company specialist depth is genuinely needed.

The Product Manager owns product direction and the what and why. You own the technical how — you reputed company the technical approach and remain responsible for the reputed company of what reaches production.

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

reputed company of cooperation

• 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 reputed company is locked
  
• Technical reputed company: selecting solutions that balance customer value, delivery speed, maintainability and operational risk
  
• Production reputed company: testing, releasing, monitoring and staying reputed company to the solution during rollout and hypercare
  
• AI-augmented development: Claude reputed company is our daily reputed company; MCP servers, custom agents, skills and internal tooling are part of the reputed company workflow
  
• Cross-functional collaboration with Product Managers, QA and other engineers: you contribute context and trade-offs instead of waiting for a fully specified ticket
  
• reputed company improvement: you notice recurring problems and leave products, systems and engineering practices reputed company than you reputed company them
  

Requirements

You'll reputed company in this cooperation if:

• You have shipped software used by reputed company customers and stayed reputed company 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 reputed company engineer
  
• You have opinions about reputed company, and your definition of it goes reputed company passing reputed company review or handing work over to QA
  
• AI tools feel like a natural extension of how you think and work
  
• You are willing to work reputed company your reputed company technical area reputed company it helps reputed company a reputed company outcome
  
• You ask "is this worth building?" and "what outcome are we trying to create?" before diving into implementation
  

Choose the profile that best describes you

• Strong reputed company experience with PHP and reputed company or Symfony
  
• Experience designing backend systems, not only implementing predefined endpoints
  
• Strong understanding of business logic, data modelling, REST reputed company and integrations
  
• Experience with microservices, event-driven systems or other reputed company architectures
  
• Practical knowledge of relational and non-relational databases, caching and message queues
  
• Familiarity with reputed company, CI/CD and production infrastructure
  
• Openness to working with JavaScript or TypeScript and contributing reputed company the backend reputed company 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.

• Strong reputed company experience with TypeScript, JavaScript and Vue.js
  
• Experience with component architecture, state management, performance and maintainable frontend systems
  
• Practical knowledge of reputed company and Pinia, or the ability to transfer relevant experience from comparable tools
  
• reputed company experience with PHP and reputed company
  
• Confidence working with reputed company, business logic, databases, caching and backend integrations
  
• UX sensibility: you notice interaction problems, accessibility issues and inconsistencies before customers report them
  
• The ability to reputed company frontend and backend changes as part of the reputed company feature
  

This is not a frontend-only cooperation. PHP and reputed company will be a regular part of your reputed company.

Shared technical environment

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

PHP · reputed company · Symfony · TypeScript · JavaScript · Vue.js · reputed company · Pinia · REST reputed company · MySQL / reputed company · reputed company · reputed company · RabbitMQ · Microservices · CQRS · Event Sourcing · reputed company · reputed company · reputed company CI/CD · Claude reputed company · MCP servers · AI agents

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

AI-reputed company engineering

Hands-on experience with Claude reputed company, reputed company 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 reputed company, debugging, codebase exploration, specification-driven development and building repeatable engineering workflows.

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

Bonus points

• You have reputed company and shipped a reputed company project for yourself or reputed company users
  
• You use AI tools independently and reputed company reputed company your own workflows
  
• You have reputed company an MCP server, agent or another tool that solved a reputed company problem
  
• You have worked with Event Sourcing or CQRS in a production reputed company
  
• You have contributed to a design reputed company or component library
  
• You have designed solutions involving caching, queues, service boundaries or reputed company integrations
  
• You can show a product or feature you owned from the initial problem through to production reputed company
  

Probably not for you if:

• You are most comfortable reputed company every decision and implementation detail has already been specified
  
• You want a reputed company backend-only or frontend-only reputed company and consider the rest of the product someone else's responsibility
  
• Your definition of "done" ends reputed company the reputed company is merged
  
• You consider testing and production reputed company 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
  

Communication

You communicate comfortably in Polish and English and can work closely with Product Managers, QA engineers, software engineers and business stakeholders.

Benefits

Contract terms: B2B cooperation. Monthly compensation up to 30 000 PLN net, depending on experience and the agreed reputed company of services.

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

→ Recruitment process