Role Description
We are looking fa Frontend Tech Lead to support the
replatforming of an existing production website from AEM Headless to Storyblok.
The project is based on a custom React + TypeScript
architecture with server-side rendering, client-side hydration, a shared
Node.js/TypeScript BFF/page-model layer used by both SSR CSR navigation.
This is not a standard Next.js implementation.
The ideal candidate has strong experience with React,
TypeScript, Headless CMS integrations, SSR/CSR data flow, frontend
architecture. They will help define the technical standards fintegrating
Storyblok content the existing frontend, working closely with the solution
architect, the client’s frontend team, other developers.
The role requires technical ownership, not only execution.
The candidate should be able to propose implementation patterns, identify
trade-offs, challenge assumptions, help other developers follow consistent
standards.
---
Key Responsibilities
Lead the frontend implementation approach fthe Storyblok
integration.
Define standards reusable patterns fCMS-driven
component rendering.
Work on the first batches of components to establish
implementation guidelines fthe rest of the team.
Help define the Storyblok-to-BFF/page-model data flow.
Decide, together with the team, what data should be
transformed in the BFF what should remain a frontend concern.
Integrate Storyblok-managed content an existing React
application with minimal unnecessary changes to stable components.
Design wrapper/adaptcomponents where useful to connect
Storyblok content to existing frontend components.
Support SSR, hydration, client-side navigation
consistency.
Ensure the frontend can support Storyblok preview behaviour
where required.
Work with the client’s frontend team to align implementation
decisions propose improvements.
Mentother developers review implementation
approaches.
Document technical patterns, decisions, guidelines.
--
Required Skills
Strong React experience.
Strong TypeScript experience.
Experience with custom SSR/CSR architectures.
Good understanding of React hydration client/server
rendering boundaries.
Experience with Node.js/TypeScript BFF, API, page-model
layers.
Experience integrating frontend applications with a Headless
CMS.
Strong understanding of frontend data flow API
contracts.
Ability to design CMS-to-component mapping strategies.
Experience working with reusable component libraries.
Ability to integrate CMS content without creating one-off
logic fevery component.
Experience with React Context, composition patterns,
wrappers, adapter components.
Ability to reason about what should run on the server, what
should run on the client, what should remain isomorphic.
Ability to work directly with client technical teams.
Ability to provide technical guidance define standards
fother developers.
---
Preferred Skills (optional)
Storyblok experience.
Experience with the Storyblok SDK.
Familiarity with Storyblok Bridge Visual Editor
concepts.
Experience with `StoryblokComponent` similar CMS-driven
component rendering patterns.
Experience with AEM Headless AEM-to-Headless CMS
migrations.
Experience designing consuming page-model contracts.
Experience with rich text rendering from CMS content.
Experience with CMS-managed media image assets.
Experience with redirects, shared content, headers, footers,
global content models.
Experience testing CMS-driven rendering transformation
logic.
Experience reviewing frontend architecture mentoring
developers.
---
Nice to Have
Microfrontend experience.
CloudFront, CDN, cache invalidation awareness.
Experience with migration tooling.
Storyblok Management API awareness.
Experience working with vendtechnical support.
SSR performance hydration optimization experience.
SEO accessibility awareness fCMS-rendered websites.
---
Ideal Candidate
The ideal candidate is a senifrontend engineer tech
lead who understands React beyond framework-level usage.
Experience with frameworks such as Next.js is useful, but
the candidate should also understthe underlying concepts of React
rendering, SSR, hydration, client-side navigation. This project requires
someone who can work inside an existing custom architecture rather than relying
on a framework to solve the architectural problems automatically.
They should be pragmatic, collaborative, able to balance
delivery speed with maintainable architecture.
更多
