Ship BI-tool-quality React interfaces sitting on top of production LLM agent systems

Ramp's Financial Intelligence team needs a frontend-leaning engineer who owns customer-facing surfaces for agentic financial analysis, FP&A, and book-close end to end — from React UI through the API and data contracts feeding it. This interview digs into complex client-side state for data-dense, agent-driven, real-time surfaces, plus fluency with AI coding tools as a daily workflow.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

React and TypeScript at production scale
Complex client-side state for data-dense/real-time surfaces
Agentic/LLM-driven UI patterns (streaming, partial updates)
API and data contract design collaboration
Daily fluency with AI coding models and agentic dev workflows
Ownership through ambiguity

Common question themes

Describe the most complex client-side state problem you've solved and why

Tell me about a UI you built for a data-dense or BI-style workflow

How have you designed a frontend experience around an LLM agent's output

Walk me through how you use AI coding tools in your day-to-day workflow

Tell me about a time you shaped an API contract, not just consumed one

Describe shipping a production-grade feature end to end under ambiguity

How candidates describe it

Real Applied AI 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