Engineering Manager, Frontend (Maternity Cover)
- Work arrangement
- On-site
- Occupation
- Software & IT
- Location
- Poznań, Greater Poland Voivodeship, PL
- Compensation
- Not disclosed
- Apply by
- April 15, 2027
About this role
<h2>Requirements</h2><ul>
<li>Agentic development as your primary workflow: daily, fluent use of Claude Code, OpenCode or an equivalent harness on production code, including multi-step tasks and parallel sessions.</li>
<li>Evidence you have configured the harness, not only used it: agent instructions, subagents, MCP servers, tool permissions, CI checks for agent output.</li>
<li>6+ years building production frontend applications, with deep React and advanced TypeScript.</li>
<li>Critical review of generated code — knowing when to accept, correct or reject, and why.</li>
<li>Node.js and BFF patterns, REST API design, automated testing with Playwright and Jest.</li>
<li>Technical leadership without needing a manager title behind you: mentoring, setting standards, owning a codebase area, leading a squad through decisions.</li>
<li>Ownership of features from ticket to production, with a quality and reliability mindset.</li>
<li>Clear written communication and autonomy in a remote-first, agile team; English at C1.</li>
</ul><h2>Nice to have</h2><ul>
<li>Experience with Next.js and server-side rendering</li>
<li>Familiarity with AWS or other cloud environments</li>
<li>Experience in subscription, billing or payments domains</li>
</ul><h3>Responsibilities:</h3><ul>
<li>Ship code yourself — stay hands-on in React and TypeScript, take real tickets, and drive them with agents rather than supervising from a distance.</li>
<li>Own the agent harness for frontend — Claude Code and OpenCode configuration, agent instruction files, subagents, MCP servers, hooks and permissions. Treat "the agent could not figure this out" as a signal about our codebase and context, not only about the agent.</li>
<li>Raise the team’s agentic ceiling — pair, demo, and improve the docs, conventions, tests and tooling agents work from, so the whole squad ships faster and not only you.</li>
<li>Stay the engineer in the loop — you own correctness, design quality and security of what the group merges, whoever or whatever wrote the first draft. Set the review bar for agent-written code and back it with CI gates.</li>
<li>Hold delivery for the frontend scope of your squad: sprint commitments, estimates, and the trade-off calls between speed and quality.</li>
<li>Run the group day to day — 1:1s, standups, unblocking. Light-touch and temporary by design; you are not being hired to write process.</li>
<li>Own what you ship: launch with dashboards and alerts, monitor, and take part in the operational health of your squad’s domain.</li>
<li>Take a structured handover from our Lead Frontend Engineer before the leave starts, and hand it back cleanly on her return.</li>
</ul><h2>Benefits</h2><ul>
<li>Flexible working hours and form of employment;</li>
<li>100 % paid sick leave within the agreed limits;</li>
<li>Events, celebrations</li>
<li>Work with an international team of well - rounded experts in Amsterdam (HQ), Poznan, Manila, NYC. 16 nationalities and counting!</li>
<li>Work on unique, market-leading, SaaS products, with clients all over the world: Europe, Asia, Americas;</li>
<li>Work closely with people who value diversity, hard work, friendly relationships and love their jobs, and get all together to the next level!</li>
<li>Join a company where engineering and business teams work as true partners, shaping the future of subscriber management technology.</li>
<li>Be part of a culture that values ownership, impact, and learning, with AI at the heart of our innovation strategy.</li>
</ul>