Skip to content

Frontend Team Structure for NepWalk

  • Frontend Team Lead
  • Feature Developer (with API Integration)

Frontend Team Lead

The Frontend Team Lead owns the technical direction of the frontend, leads collaboration across teams, and is also responsible for building and maintaining the shared component system.

Architecture & Leadership

  • Define the frontend architecture for scalability using Next.js and modern best practices.
  • Review PRs to TEST and main, enforcing coding standards, code quality, and consistency.
  • Align with Scrum/PM teams to plan and track sprint deliverables in line with BRD/SRS goals.
  • Collaborate with backend and design teams to validate API feasibility and ensure Figma alignment.
  • Mentor frontend team members in best practices (e.g., functional components, hooks, accessibility).
  • Enforce WCAG 2.1 accessibility, performance benchmarks, and mobile-first principles.
  • Maintain and evolve shared logic in lib/, including utilities, hooks, and services.

Component System Ownership

  • Build and maintain reusable UI components (e.g., components/Button/Button.tsx) aligned with design tokens.
  • Write unit tests (Button.test.tsx) using Jest and maintain strong test coverage.
  • Style components using modular, responsive CSS (Button.module.css).
  • Ensure components meet accessibility standards (e.g., ARIA labels, keyboard navigation).
  • Document usage and variations (components/<Component>/README.md).
  • Collaborate with Feature Developers to ensure integration compatibility and encourage reuse.
  • Lead code reviews focused on component reusability, abstraction, and maintainability.
  • Tag and version components as they mature (e.g., components/button/v1.0.0).

Feature Developer (with API Integration)

Feature Developers are responsible for building complete user-facing functionality, integrating APIs, and ensuring business logic, UI, and testing are in place for each feature.

Responsibilities

  • Develop scoped feature components (e.g., app/login/components/LoginForm.tsx) that follow design and accessibility guidelines.
  • Integrate backend APIs (e.g., POST /api/auth/login) with TypeScript and proper typing.
  • Write unit and integration tests (e.g., LoginForm.test.tsx) with mock APIs and edge case coverage.
  • Document technical dependencies (app/<feature>/dependencies.md) and component usage (app/<feature>/docs/components.md).
  • Ensure responsiveness and alignment with Figma designs across breakpoints.
  • Collaborate with backend developers to finalize API contracts and with QA to meet testing standards.
  • Open clear and documented PRs to TEST, including integration logic and usage examples.
  • Identify opportunities to refactor shared logic into components or libraries for reuse.