Skip to content

Frontend Engineering

Product Engineering

Braudit

Braudit is a B2B SaaS platform for employee productivity and performance management. As the sole frontend engineer on a five-person team, I owned the frontend architecture and implementation from the company's early product development through multiple pivots. I helped launch its initial product within three months and built workflows for task management, productivity tracking, goals, KPIs, and performance reviews as the platform evolved to serve 33 organizations.

Live preview(opens in a new tab)

Project details

Project type
B2B SaaS Platform
Role
Software Engineer, Frontend
Engagement
Full-time · Remote
Period
February 2023 – April 2026
Status
Live · Engagement completed
Technologies
  • React
  • TypeScript
  • GraphQL
  • Apollo Client
  • GraphQL Code Generator

Context

Project context.

Braudit evolved from an early-stage career-focused product into a SaaS platform for employee productivity and performance management. The platform helps organizations organize work, track employee activities, manage performance goals, and provide managers and administrators with visibility into team productivity. I joined before the initial product launched as the sole frontend engineer in a five-person team. Over three years, I was responsible for building and evolving the frontend as the business refined its direction, introduced new features, and adapted to changing product requirements. The resulting application supported 33 organizations, each with at least 30 employees, with distinct workflows for employees, managers, and administrators.

Project setting

Braudit's product direction changed significantly during my engagement. The application evolved from its initial career-focused offering into an employee productivity and performance platform. This required continuously adapting the frontend architecture, introducing new workflows, and maintaining reusable components while supporting ongoing product development.

Problem space

  • Organizations needed a structured way to manage daily employee activities, goals, and performance within a shared platform.
  • Employees needed straightforward workflows for tracking tasks, monitoring progress, and managing their responsibilities.
  • Managers and administrators needed visibility into productivity, workload, and performance across their teams.
  • The product's evolving requirements demanded a frontend architecture that could support frequent changes without repeatedly rebuilding shared functionality.
  • Multiple organizations and user roles needed appropriately scoped data and distinct application experiences.

Target users

  • Organizations managing employee productivity and performance.
  • Employees tracking daily work, tasks, and goals.
  • Team managers monitoring productivity and workload.
  • Administrators overseeing organizational performance and workflows.

Contribution

My contribution.

I served as Braudit's sole frontend engineer from February 2023 to April 2026, owning frontend architecture, implementation, and ongoing product development. Working alongside product, design, and backend engineering, I helped deliver the initial product within three months and continued building the application through multiple pivots.

My responsibilities covered the frontend from architectural decisions and API integration to complex product workflows and reusable interface components. Rather than focusing on isolated screens, I worked across the application to ensure new features could be introduced consistently while accommodating multiple organizations, different user roles, and changing business requirements.

  1. Frontend Architecture and Ownership

    Designed and maintained the application's React and TypeScript architecture, establishing reusable components, shared configuration, and consistent patterns for accessing backend data. Owned the frontend implementation as the product evolved through changing requirements and multiple iterations.

  2. Multi-Tenant Application Experiences

    Built organization-aware frontend workflows using Apollo Client, GraphQL, and generated types. Developed distinct experiences for employees, managers, and administrators, with data requests scoped to the relevant organization.

  3. Workday and Productivity Management

    Developed Workday, a central productivity workflow supporting daily task tracking, automatic rollover of unfinished work, and productivity grades visible to managers and administrators. Workday became the platform's most-used workflow.

  4. Goals, KPIs, and Performance Reviews

    Built product interfaces for goals, key performance indicators, workload visibility, approvals, and AI-assisted performance reviews. These features supported the platform's transition toward employee performance and productivity management.

  5. Continuous Product Development

    Collaborated with the wider team to implement new product requirements, adapt existing features, and maintain consistent frontend behavior as the business changed direction. Used reusable and composable UI primitives to support ongoing development across the application.

Scope of ownership

I worked as part of a five-person startup team, collaborating directly with other engineers and product stakeholders. My ownership extended beyond implementing individual designs to making frontend architectural decisions, coordinating data requirements with backend engineering, and maintaining the application's frontend as the product matured.

Implementation

Technical breakdown.

Braudit's frontend was built with React and TypeScript, using GraphQL and Apollo Client for communication with backend services. A major architectural consideration was supporting multiple organizations and user roles while maintaining consistent UI behavior and accommodating ongoing product changes. The implementation combined organization-scoped data access, typed GraphQL operations, reusable interface components, and dedicated workflows for employee productivity and performance management.

  1. Multi-Tenant Data Architecture

    • React
    • TypeScript
    • GraphQL
    • Apollo Client
    • GraphQL Code Generator

    Built the frontend data layer around Apollo Client and GraphQL, using generated TypeScript types to keep application code aligned with backend operations.

    Requests were scoped to the relevant organization, supporting the different data contexts required by employees, managers, and administrators.

    • Apollo Client for GraphQL data operations.
    • Generated TypeScript types for GraphQL operations.
    • Organization-scoped data requests.
    • Distinct administrator, manager, and employee workflows.
  2. Workday Task and Productivity Workflows

    • React
    • TypeScript
    • GraphQL
    • Apollo Client

    Implemented Workday to give employees a structured way to manage daily activities while providing managers and administrators with visibility into productivity.

    The workflow supported task tracking, automatic rollover of unfinished work, and productivity grades, bringing day-to-day execution and performance visibility into a central part of the product.

    • Daily employee task tracking.
    • Automatic rollover of unfinished tasks.
    • Productivity grades.
    • Manager and administrator visibility.
  3. Goals and Employee Performance

    • React
    • TypeScript
    • GraphQL
    • Apollo Client

    Developed frontend experiences for tracking goals, KPIs, workload, and performance-related activities.

    As Braudit expanded its employee performance offering, I also built interfaces supporting approval processes and AI-assisted performance reviews.

    These features formed part of the broader employee productivity and performance management application.

    • Goal and KPI management interfaces.
    • Workload visibility.
    • Approval workflows.
    • AI-assisted performance review interfaces.
    • Role-specific product experiences.
  4. Reusable Frontend Components

    • React
    • TypeScript

    Built reusable and composable UI primitives to support feature development across the product.

    Shared components and configuration helped accommodate changing requirements and enabled new product workflows to be developed without treating every interface as an entirely separate implementation.

    • Reusable UI primitives.
    • Shared frontend configuration.
    • Composable interface patterns.
    • Consistent components across evolving product workflows.

Outcomes

What the work delivered.

My work contributed to Braudit's initial product launch and its subsequent evolution into an employee productivity and performance management platform. Over the engagement, I delivered the frontend architecture and core workflows supporting a multi-tenant SaaS application used by 33 organizations. Workday became the product's most-used workflow, while reusable frontend foundations supported continued development through multiple product pivots.

  1. Outcome

    Initial Product Launch

    Contributed to launching Braudit's initial product within approximately three months as the sole frontend engineer on a five-person startup team.

    Measured impact

    Initial launch
    ~3 months

    Team-level product launch timeline from initial development.

    The product subsequently evolved through multiple pivots, with continued frontend development throughout my engagement.

  2. Outcome

    Multi-Organization Platform

    Built and maintained frontend experiences for a SaaS platform serving 33 organizations, each with at least 30 employees.

    Measured impact

    Organizations served
    33

    Each organization had at least 30 employees.

    The application supported distinct employee, manager, and administrator workflows within its multi-tenant structure.

  3. Outcome

    Most-Used Productivity Workflow

    Developed Workday, which became Braudit's most-used workflow, bringing task tracking, automatic task rollover, and productivity visibility into the employee experience.

    Workday provided employee task-management functionality and productivity grades accessible to managers and administrators.

  4. Deliverable

    Reusable Frontend Architecture

    Established a React and TypeScript frontend architecture with typed GraphQL operations, organization-scoped data access, and reusable components to support ongoing product development.

    The architecture supported evolving requirements across administrator, manager, and employee experiences as the product changed direction.

  5. Deliverable

    Employee Performance Features

    Delivered interfaces for goals, KPIs, workload, approvals, and AI-assisted performance reviews as Braudit expanded into employee productivity and performance management.

    These features extended the product beyond daily task management into broader organizational performance workflows.