Product Engineering; Backend - B2B cooperation- Regular & Senior

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.

At 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.

• Backend services - designed, built, tested, and shipped by you
• Technical discovery: validate feasibility, identify constraints, and shape the approach before scope is locked
• End-to-end quality: merged code is the beginning, not the end- you stay on standby through hypercare
• AI-augmented development: Claude Code is our daily driver- MCP servers, custom agents, and internal tooling are part of the real workflow
• Close collaboration with Product Managers -you own the how, they own the what and why
• Continuous improvement: you leave systems better than you found them

• You've shipped things that survived contact with real users - and when bugs appeared, they were yours to fix
• You get restless when you don't understand why something is being built before you start building it
• Owning a problem end-to-end feels more natural than executing a fully-specified ticket
• AI tools feel like a natural extension of how you think and work - not something you use because someone told you to
• You 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 engineer
• You ask "is this worth building at all?" before diving into how to build it
• You have a side project - something you built for yourself, for real users, or just because you had to
• You use AI tools on your own account, not just when your employer provides them
• You've built or worked with Event Sourcing / CQRS in a production system
• You've built an MCP server or Claude Code agent for a real workflow

• You're most comfortable when everything is fully specified before you start
• You consider testing someone else's job, or something you do after the feature is done
• Your hands-on AI experience is mostly autocomplete and the occasional PR summary

• PHP & Laravel / Symfony -strong commercial experience; you know the frameworks, not just the syntax
• Backend architecture -microservices, REST APIs, event-driven systems; you've designed things, not just implemented them
• AI tooling -hands-on Claude Code, Cursor, or equivalent in real development; bonus if you've built MCP servers or agents
• Communicative Polish and English -you work closely with PMs, QA, and other engineers
• 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

Contract terms:
B2B
, Monthly compensation range:
15,000- 25,000 PLN net depending on experience and scope of responsibilities.

• Intro 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.