Ramp·Frontend Engineer·Online Assessment (OA)·Junior

JuniorPending

Aug 2026Remote

Summary

Took the frontend OA for Ramp and had to rebuild Wordle from scratch in 90 minutes. Thought I bombed it since I ran out of time on some of the frontend code, but it came back 100/100 somehow. Still not sure if there were other sections I'm blanking on.

Questions Asked (1)

Build a functional Wordle clone within 90 minutes.

System DesignTechnical Trade-offs

Author's notes

Ran out of time before I could finish all the frontend code and fully expected to fail.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints (e.g., word list size, UI polish, animations) to scope the 90-minute build. Then outline a minimal viable architecture (React + state management) and prioritize core game logic (guess validation, color feedback) before UI enhancements. Finally, discuss trade-offs made and potential improvements if given more time.

Pro tip: Demonstrate time management by explicitly allocating minutes to each phase (e.g., 10 min planning, 50 min coding, 20 min testing, 10 min polish) and stick to it. This shows you can deliver under pressure without over-engineering.

1. Clarify Requirements and Constraints

Ask questions to understand expected features (e.g., daily word, hard mode, animations) and constraints (e.g., no external libraries, mobile responsiveness). This ensures you build what matters most.

2. Design Minimal Architecture

Sketch component structure (e.g., Board, Keyboard, Game) and state management (e.g., guesses, current guess, game status). Decide on data structures for word list and guess evaluation.

3. Implement Core Game Logic

Code the guess validation (length, word list), color feedback algorithm (correct, present, absent), and win/loss conditions. Use a simple UI to test logic quickly.

4. Build UI and Interactions

Create the grid, keyboard, and input handling. Add basic styling and ensure the game is playable. Prioritize functionality over polish.

5. Test, Refine, and Discuss Trade-offs

Manually test edge cases (e.g., duplicate letters, invalid words). If time permits, add small enhancements (e.g., animations). Be ready to explain what you'd do with more time.

Key Points to Mention

State management approach (e.g., React useState/useReducer, or external store) and why it fits the time constraint.
Algorithm for evaluating guesses, especially handling duplicate letters correctly (e.g., two-pass approach).
Trade-offs made: e.g., using a static word list vs. API, skipping animations for core functionality, or choosing simplicity over extensibility.
Testing strategy: how you ensured correctness quickly (e.g., unit tests for logic, manual testing for UI).
Performance considerations: efficient rendering of the grid and keyboard, avoiding unnecessary re-renders.
Potential improvements if given more time: accessibility, animations, daily word rotation, hard mode, etc.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.