Design and ship high-craft product surfaces at the intersection of design and front-end code, AI-first

Ramp is hiring a Design Engineer (NYC) who prototypes directly in code, validates with real customers, and ships production React/TypeScript interfaces — working AI-first with Cursor and Claude Code before systemizing in Figma. This interview probes design craft shown through shipped or prototyped work, front-end engineering fluency, and genuine facility with AI-assisted workflows, not just design theory.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Design-to-code craft in React/TypeScript/CSS
AI-first workflow using Cursor and Claude Code
Design systems and reusable component thinking
Performance and accessibility as part of craft
Designing legibility/trust around AI agent actions

Common question themes

Walk me through a product surface you designed and built end-to-end, in your portfolio

Describe your actual workflow using an LLM, Cursor, and Claude Code to go from intent to shipped code

How have you extended or contributed to a design system with reusable patterns

How do you balance visual/interaction craft with performance and accessibility

How would you design UI that reveals what an AI agent is doing without overwhelming the user

How candidates describe it

Real Design Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Ramp interviews