Product Engineer — Frontend Background (Full-stack) - Employment Contract (UoP)- Senior

Job Description This is a remote position. The ability to build software is no longer rare. AI has made execution accessible to almost everyone. What's rare now is judgment — understanding customer problems, making sound decisions, and knowing where to create real value. The role At Profitroom we build hospitality software used by thousands of hotels and millions of guests. Product Engineers own 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 Engineer role 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 when we say Product Engineer. Not just a title — a way of working. What you'll actually do Full-stack delivery of user-facing features — the frontend and the backend behind it, designed, built, tested, and shipped by you Technical discovery — together with the PM, you validate feasibility, identify constraints, and shape the technical approach before scope is locked End-to-end quality — you care whether the experience works in production, not only whether it passed review 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 and backend engineers — you own the how; the PM owns the what and why UX coherence — you notice recurring issues, raise them, and leave the product better than you found it → Tech stack Full-stack, TypeScript, JavaScript, React, Node.js, Claude Code, MCP servers, AI agents, REST API, Docker, GitLab CI/CD, PHP, Laravel, MySQL / MariaDB, MongoDB, Redis, Microservices, Kubernetes. Requirements What we're looking for Technical expectations: TypeScript & JavaScript — strong commercial experience; you know the language, not just the framework React (or equivalent) — component architecture, state management, and performance; you've built real products with it UX sensibility — you notice what's wrong before users complain; interaction quality matters to you Full-stack reach (Node.js / backend comfort) — you can connect APIs and write business logic when established patterns are available; full-stack delivery is a meaningful part of the job AI tooling — hands-on experience with Claude Code, Cursor, or equivalent; experience generating backend integrations with AI is a strong plus Communicative Polish and English — you work closely with PMs, QA specialists, and backend engineers You'll thrive here 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 Owning 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 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 your employer provides them 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 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 Benefits What comes with the job Form of employment: Employment contract. Salary range: 14,900–21,000 PLN gross per month. 100% remote — fully flexible, work from anywhere in Poland English classes — and a dedicated team development fund Medical and life insurance — co-financed, plus access to sports facilities 24 / 26 days off Company perks — retreats and events, wedding and baby packs, and an employee referral program Flat hierarchy — open communication, no bureaucracy → Recruitment process Intro call with the Recruiter (up to 45 minutes). We cover your background, what you're looking for, and mutual fit. Technical interview with the Team Leader, Tech Lead, and Product Manager (up to 90 minutes). Expect concrete technical questions and a discussion of how you approach frontend architecture, full-stack delivery, product ownership, and the practical use of AI. We care about judgment and initiative, not keyword recall. Technical task. A time-boxed, practical challenge reflecting what you'll actually do here, reviewed together in a follow-up call. We care about your process, UX decisions, and how you handle the parts that go beyond the frontend.