freehire launches on Product Hunt on 26 August.

Follow →

Product Engineer/ Full-stack

At Profitroom we build hospitality software used by thousands of hotels and millions of guests. In this cooperation, you take responsibility for technical initiatives end-to-end: from technical discovery and solution design, through implementation and testing, to release and production readiness. The Product Manager steers direction and owns the what and why. You own the how and the technical solution.

This is a full-stack product engineering cooperation with a strong frontend focus. Your technical home is the frontend: user journeys, component architecture, interaction design, and UX quality. You also work across the backend when AI, established patterns, and your experience make it practical — for example, when connecting APIs, implementing business logic, or building integrations.

Frontend development and product engineering are not the same thing. Frontend without product judgment is implementation. Product judgment without frontend craft is wireframes. We're looking for both — plus the full-stack reach to deliver a feature end-to-end without handing half of it off.

“The builder drives; the PM steers.” This is what we mean by product engineering. Not just a label — a way of working.

→ Tech stack

Full-stack, TypeScript, JavaScript,VueJS , Node.js, Claude Code, MCP servers, AI agents, REST API, Docker, GitLab CI/CD, PHP, Laravel, MySQL / MariaDB, MongoDB, Redis, Microservices, Kubernetes.

You'll enjoy collaborating with us if:

  • You've shipped user-facing features that real people used — and you know what broke and why
  • You notice UI details that most engineers scroll past, and it bothers you when they're wrong
  • You get curious about the business reason behind a feature before you start building it
  • Taking responsibility for a feature end-to-end — from the PM conversation through to production — feels like the natural way to work
  • AI tools feel like a natural extension of how you work; you use them to move beyond the frontend boundary into full-stack work when needed
  • You care about what happens on a slow connection, with a keyboard, and on a screen size nobody designed for
  • You can weigh in on whether a feature is worth building without needing to be the person who makes the final product decision

Probably not for you if:

  • Your definition of “done” is a Figma-accurate implementation, regardless of how it actually works for users
  • Backend is someone else's problem and that's a firm boundary for you
  • Your hands-on AI experience is mostly autocomplete and the occasional PR summary


Contract terms: B2B cooperation. Monthly compensation range: 15,000–25,000 PLN net, depending on experience and the agreed scope of services.

  • 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

Technical expectations:

  • TypeScript & JavaScript, VueJS, Tailwind and Pinia — strong commercial experience; component architecture, state management, performance; you've built real things with these technologies.
  • UX sensibility — you notice what's wrong before users complain; interaction quality matters to you.
  • PHP & Laravel — you have documented experience with backend engineering, you understand concepts like design patterns, APIs, caching, database query optimization, microservices, message queues. It’s a full-stack job, writing backend will not be an occasional favour but your daily task.
  • AI tooling — hands-on Claude Code, Cursor, or equivalent; experience generating backend integrations with AI and understanding advanced topics like skills, spec-driven developmen, feedback loops; is a strong plus.
  • Communicative Polish and English — you work closely with PMs, QA, and software engineers.

Bonus points:

  • You have a side project — something you built, shipped, and perhaps use yourself
  • You use AI tools on your own account, not only when they are provided as part of a project
  • You've worked with or contributed to a design system or component library
  • You've built Node.js services or backend integrations beyond the occasional CRUD endpoint