Technical Web Specialist

About Us
Perk (formerly Travel Perk) is the intelligent platform for travel and spend management. Built to tackle the time-consuming, manual work that gets in the way of real work, our tools automate everything from travel bookings to expenses, invoice processing, and more. By eliminating this shadow work that wastes hours, erodes morale, and saps innovation, we're on a mission to power real work, with real impact.
We're trusted by more than 12,000 companies worldwide, including On Running, Breitling, and Fabletics, and we're tackling the 7 hours of lost productivity per employee each week, a $1.7 trillion problem.
Founded in 2015, Perk has grown into a global company of more than 1,800 people across 12 offices globally, with headquarters in London and Boston. We combine innovation, control, and simplicity to transform how businesses work and how people feel at work.
At Perk, we're driven by our values, like being an owner, delivering a 7-star experience, and working as one team. We value curiosity, purpose, and mindset, not just knowledge, to unlock the power in your potential. Our talent team brings together leading minds from the travel, fintech, and SaaS industries, representing over 70 countries. If you're excited about having a real impact and shaping how millions of people experience work, we'd love you on the team.
Visit  to learn more.

As a Technical Web Specialist, you’ll be the connective tissue between our web team and the rest of the business. This role exists because great websites aren’t just built — they’re coordinated, prioritised, and protected from chaos. Sitting at the intersection of Marketing and Web Development, you’ll own the intake and lifecycle of web requests, ensure every project is properly scoped before it touches the dev queue, and support the team in delivering an ambitious web roadmap.

But this role doesn’t stop ’ll also be hands‑on in the quality of what we ship — reviewing copy and UX before pages go live, supporting CRO initiatives, and acting as a critical second pair of eyes on every significant release. You care as much about whether a page converts as whether it launches on time.

If you’re someone who thrives on bringing order to complexity, understands how a website is actually built, and can hold your own in a room with developers, designers, and marketers alike, this is your role.

Technical Ownership & QA

• Build and ship pages/components directly in Storyblok CMS: component configuration, staging, QA, and production deployment across market versions

• QA every release technically — rendering, functionality, and cross-browser/device behaviour, not just copy and visual polish

• Use AI tools as a core part of daily production work (drafting, layout variants, QA support), and know where AI output still needs a human check, particularly around localisation nuance and experiment validity

Request Triage & Scoping

• Own intake for web requests: qualify, triage, and estimate technical complexity and dependencies before anything is scoped or scheduled

• Enforce briefing standards and know enough technically to explain why a brief is incomplete

• Decide what can be handled directly vs. what needs to go to the development team, and write specs the team can act on without excessive clarification

Project Coordination

• Act as day-to-day PM between the development team and business stakeholders: track scope, delivery, and risk

• Maintain the web backlog and sprint board with clear status, ownership, and blockers

• Support CRO initiatives: help build A/B test setups, document hypotheses, and track experiment results

Process & Reporting

• Maintain intake templates, briefing standards, and triage criteria

• Produce regular status updates and pipeline reports for the Head of Web and wider leadership

Must-haves

• 2 to 4 years in a web operations, technical/digital project management, or web production role, ideally with hands‑on CMS or front-end exposure — not purely marketing coordination

• Working technical literacy: solid HTML/CSS fundamentals, understanding of how a CMS is structured (Storyblok, Contentful, Webflow or similar), staging vs. production workflows,…