Skip to content

REQUIREMENTS.md

Latest commit

 

History

History
28 lines (20 loc) · 2.43 KB

REQUIREMENTS.md

File metadata and controls

28 lines (20 loc) · 2.43 KB
Raw

Requirements

Overview

Build a LaunchDarkly-inspired feature flag app that helps teams create, target, roll out, and measure feature flags. Think beyond a list of on/off toggles.

The app is full-stack React + Spring Boot (Java). It keeps the React frontend and Spring Boot backend of the sample calendar repo you clone, and it persists data in MongoDB. Every feature you ship must work end to end: a usable screen, a real API call, a backend handler, and stored data.

Pick five to ten features from the list below, or add your own of the same weight. Fewer than five is under scope. More than ten spreads the work too thin.

Feature set

  • Feature flag management. Create boolean and multi-variant flags with a key, description, and default value. Configure, toggle, and retire them from one screen.
  • Environment-based configuration. Keep a separate flag state for development, staging, and production. Switch between environments and see which one you are editing.
  • User and segment targeting. Define audience segments by user attributes (email, plan, country). Serve a variation to a named user or a whole segment.
  • Progressive rollouts. Set a percentage of users who receive a variation. Raise it step by step and see the current split.
  • Approval workflows. Submit a flag change for review. A second user approves, rejects, or schedules it before it goes live.
  • Experimentation and metrics. Assign users to variations and record a conversion event per variation. Compare the results side by side.
  • Change history and rollbacks. Record who changed a flag, when, and what changed. Restore any earlier configuration in one click.

Acceptance criteria

  • Five to ten features, each working end to end through the UI, the API, and MongoDB.
  • Human judgment is visible. AI can write the code. Feature selection, architecture, and production readiness must be your own decisions, and the transcripts should show it.
  • Modern, polished UI. Responsive, keyboard accessible, with loading, empty, validation, and error states where they apply.
  • Clean checkout works. The app installs, builds, and starts without errors using the commands in hackerrank.yml.
  • Current stack. Dependency versions are at least as recent as the sample calendar repo. Do not downgrade, and do not swap out the declared stack.
  • Matches the sample repo in scope, structure, and quality. Use the calendar app as the bar for what "done" looks like.