Product Engineer- Backend background

The ability to build software is no longer rare. AI has made execution accessible to almost everyone. What's rare now is judgment — knowing what to build, why it matters, and what it takes to see it through to real customer impact.The roleAt Profitroom we build hospitality software used by thousands of hotels and millions of guests. Engineers own initiatives end-to-end: from understanding the business problem, through technical discovery, implementation, release, and production. The PM steers direction. You own the technical solution — all of it.Your technical home is backend development: data models, business logic, APIs, distributed systems. You step outside it when AI and established patterns make it practical. When something genuinely exceeds your range, you recognise the call and make it — but 'genuinely' is the key word.'The builder drives; the PM steers.' This is what we mean when we say Product Engineer. Not a title — a way of working.What you'll own Backend services- designed, built, tested, and shipped by youTechnical discovery: validate feasibility, identify constraints, and shape the approach before scope is lockedEnd-to-end quality: merged code is the beginning, not the end- you stay on standby through hypercareAI-augmented development: Claude Code is our daily driver- MCP servers, custom agents, and internal tooling are part of the real workflowClose collaboration with Product Managers- you own the how, they own the what and whyContinuous improvement: you leave systems better than you found themYou'll enjoy collaborating with us ifYou've shipped things that survived contact with real users — and when bugs appeared, they were yours to fixYou get restless when you don't understand why something is being built before you start building itOwning a problem end-to-end feels more natural than executing a fully-specified ticketAI tools feel like a natural extension of how you think and work — not something you use because someone told you toYou have opinions about what quality actually means, and your answer doesn't start with 'the QA team'You can explain a technical trade-off to a product manager and a business rationale to a senior engineerYou ask 'is this worth building at all?' before diving into how to build itBonus points:You have a side project — something you built for yourself, for real users, or just because you had toYou use AI tools on your own account, not just when your employer provides themYou've built or worked with Event Sourcing / CQRS in a production systemYou've built an MCP server or Claude Code agent for a real workflowProbably not for you if:You're most comfortable when everything is fully specified before you startYou consider testing someone else's job, or something you do after the feature is doneYour hands-on AI experience is mostly autocomplete and the occasional PR summaryTechnical expectationsPHP & Laravel / Symfony — strong commercial experience; you know the frameworks, not just the syntaxBackend architecture — microservices, REST APIs, event-driven systems; you've designed things, not just implemented themInfrastructure & databases — MySQL (MariaDB), MongoDB, Redis, Docker, Kubernetes, GitLab CI/CDAI tooling — hands-on Claude Code, Cursor, or equivalent in real development; bonus if you've built MCP servers or agentsCommunicative Polish and English — you work closely with PMs, QA, and other engineersTech stackPHP, Laravel, Symfony, Claude Code, MCP servers, AI agents, MySQL / MariaDB, MongoDB, Redis, CQRS, Event Sourcing, Microservices, RabbitMQ, Docker, Kubernetes, GitLab CI/CD, REST API, JavaScript, TypeScript, Node.js.What comes with the collaborationRemote-first collaboration modelInternational technology and product projectsFlexible project collaboration setupPlanned service breaks aligned with contract termsOpportunity to collaborate with experienced product and technology teamsOpportunity to access selected knowledge-sharing initiativesContract terms: B2B, Monthly compensation range: 15,000- 25,000 PLN net depending on experience and scope of responsibilities.If you're interested in a different type of collaboration than the one listed above, let us know in your application. We'll be happy to discuss the available options during the recruitment process.→ Recruitment processIntro call with the Recruiter (up to 45 minutes). We cover your background, what you're looking for, and mutual fit,Technical Interview (up to 90 minutes). Expect concrete technical questions, a discussion of how you approach architecture and ownership, and how you actually use AI in your work. We care about judgment, not keyword recall.