Ramp Frontend Engineer Interview Questions

Ramp·Frontend Engineer·Online Assessment (OA)

Aug 2026

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.

Build a functional Wordle clone within 90 minutes.

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

View Post

Ramp·Frontend Engineer·Technical Phone Screen

Jun 2026

Ramp frontend interview with a pretty unusual DOM traversal problem. Not your typical leetcode grind, felt more like a browser internals quiz wrapped in a coding challenge.

A URL is split into individual characters and embedded inside specially nested DOM elements. Write a custom query selector that walks the DOM tree, finds the matching elements using a selector syntax that supports '*' as a wildcard for zero or more characters in element names, and reassembles the characters in order to reconstruct the original URL.

“I did not see this coming.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Frontend coding round at Ramp, one question about building a typewriter animation in React. Pretty focused and self-contained, no system design or behavioral stuff from what I could tell.

Build a React component that animates a string fetched from an API, revealing it one character at a time at a consistent interval until the full string is displayed.

“The core logic isn't that complicated once you see it.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Ramp frontend round focused on async data fetching inside React. Pretty technical for what I expected, they really wanted you to think through edge cases beyond just 'put it in useEffect'.

Inside a React component, fetch a flag value asynchronously on mount and manage loading, error, and success states. How do you structure this, and how do you expose the result to other parts of the component tree?
How do you handle cleanup of an in-flight fetch when the component unmounts, and what problems does skipping this cause?
React strict mode runs effects twice in development. How does that interact with your fetch-on-mount pattern, and what breaks if you haven't accounted for it?

“I went straight to useEffect with fetch and useState for the three states, which was fine.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Ramp frontend interview had me build a Wordle clone in React from scratch, no styling needed but the logic had to be solid. The component breakdown and state management discussion took up a good chunk of time alongside the actual coding.

Build a Wordle-style mini-game in React with up to 6 guess attempts, letter coloring logic (green/yellow/gray), correct duplicate letter handling, and win/loss detection.
Walk through how you'd break this into components and manage state across the app.

“The duplicate letter handling is where I stumbled.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Ramp frontend interview that was basically a testing-focused coding challenge. You get a React component with some specific behaviors and have to write Mocha + TypeScript tests covering the happy path, async timing, error states, and a single-run animation guarantee. More nuanced than I expected for a frontend screen.

You're given a React component that fetches a hidden flag from a URL, renders it with a typewriter animation, and must never retrigger that animation on re-render or remount. Write Mocha + TypeScript tests covering the happy path, async timing, the single-run guarantee, and error handling. Use sinon for mocking fetch and fake timers.

“The single-run guarantee part is what tripped me up.”

View Post

Ramp·Frontend Engineer·Take-home Assignment

May 2026

Ramp frontend interview had me building a mini Wordle clone in React, fetching the target word from an API and wiring up per-letter color feedback with a 6-guess limit. The unit tests were provided and mocking the endpoint was part of the deal, so you couldn't really fake your way through it.

Build a simplified Wordle game in React where the target word is fetched from a given HTTP endpoint. The game should handle user input, show per-letter feedback (correct position, present but misplaced, or absent), and stop on a win or after 6 attempts. Your implementation must pass provided unit tests that mock the API.

“The fetch part was fine, useEffect on mount, nothing wild.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Frontend engineering round at Ramp, one coding problem focused on React animation behavior. Pretty niche stuff, not your typical leetcode grind, which I appreciated but also wasn't fully ready for.

Build a React component that reveals a string character by character using a typewriter animation with setTimeout or setInterval inside useEffect. The animation must run exactly once for the component's lifetime, even under React strict mode's double-invocation behavior.

“This is where I tripped up first.”

View Post

Ramp·Frontend Engineer·Online Assessment (OA)

Apr 2026

Ramp frontend OA where the whole challenge was less about coding and more about figuring out why the test suite wouldn't even load. Niche problem, but kind of interesting once you realize what's actually going on.

A source file uses CommonJS exports but the test runner expects ESM imports, causing the entire suite to fail before any assertion runs. Diagnose the root cause and decide whether to fix the export syntax or strictly follow the comment in the file that says to only replace one specific string.

“The comment in the file was pretty explicit: replace this one string, touch nothing else.”

View Post

Ramp·Frontend Engineer·Online Assessment (OA)

Apr 2026

Ramp frontend engineering challenge where the task was to locate and retrieve a hidden flag value from either the DOM or a URL response. Pretty practical exercise, less algorithmic than I expected.

Given either a DOM fixture with a hidden flag embedded in the markup or a URL whose response contains the flag, write code to retrieve the flag value regardless of which source it comes from.

“The DOM side was fine, querySelector and dataset access are muscle memory at this point.”

View Post