Skip to content
DXP Team Structure

Frontend Developer

Layer: Operational

Scope: Account/Project

Track: frontend

Mission

Section titled “Mission”

Build and maintain the user-facing experience — functional, performant and accessible interfaces — across the team’s CMS platforms.

Responsibilities

Section titled “Responsibilities”
  • Implement UI components and templates per design specs and the project’s CMS/frontend architecture.
  • Ensure performance, accessibility (WCAG) and cross-browser/device compatibility.
  • Integrate with backend/content APIs (REST/GraphQL) to render content.
  • Write component/unit and end-to-end tests for the UI layer.
  • Collaborate with design (Figma handoff) and Backend on API contracts.

Objectives by level

Section titled “Objectives by level”
LevelWhat success looks like
OperationalUI deliverables (functionality, performance, accessibility) meet the quality bar and ship on time.

Reporting & management

Section titled “Reporting & management”
  • Reports to: Tech Leader
  • Manages: No direct reports.

Decides vs. escalates

Section titled “Decides vs. escalates”
  • Decides: Implementation details within assigned frontend tasks and the agreed design.
  • Escalates: Design ambiguities, blockers, and scope or estimate risks.

Requirements

Section titled “Requirements”

Must have

Section titled “Must have”
  • HTML/CSS/JS fundamentals
  • A component framework (React or equivalent)
  • Responsive, accessible UI development
  • REST/GraphQL API integration
  • Frontend testing (Playwright or equivalent)

Nice to have

Section titled “Nice to have”
  • Not specified in the source material yet.

By CMS

Section titled “By CMS”
  • aem-traditional: HTL (Sightly) templating, AEM Core Components, clientlibs; React/Angular where the project uses the SPA Editor.
  • aem-eds: Vanilla JS (ES Modules) block architecture, Preact for complex interactive components, Dropin development (e.g. Adobe Commerce Dropins) for reusable framework-agnostic components, blocks instrumented for the Universal Editor.
  • optimizely-cloud: React/Next.js (or equivalent) consuming Optimizely Graph, headless-only delivery.
  • contentful: React/Next.js or Vue/Nuxt, fully decoupled; Contentful App Framework for custom UI extensions where needed.
Section titled “Related documents”