Mid

Build the web platform, DevEx, and AI-accelerated tooling powering Pinterest.com

Pinterest is hiring a Software Engineer II to work on the web platform and developer-experience tooling (builds, CI/CD, testing) that hundreds of engineers rely on to ship Pinterest.com. This interview probes 3+ years of front-end depth (JavaScript, CSS, DOM, HTTP, React/Redux/TypeScript, Jest), build-tooling familiarity (Webpack/Rspack/Vite, Node.js, SSR/Next.js/Remix), and hands-on use of AI coding agents for large-scale migrations and workflow automation.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Front-end fundamentals (JS, CSS, DOM, HTTP) and React/TypeScript/Redux
Build tooling and testing (Webpack/Rspack/Vite, Jest, SSR/Next.js)
Web platform/DevEx work: CI/CD, cross-team tooling adoption
Hands-on use of AI coding agents for migrations and workflow automation
Driving a site-wide technical improvement across team boundaries

Common question themes

Describe a DevEx, build, or CI/CD improvement you shipped that other engineers relied on

Deep dive: how does the browser rendering/DOM/HTTP pipeline work, and where have you optimized it

Your experience with React/Redux/TypeScript state management tradeoffs on a real project

How have you used an AI coding agent (Claude Code, Cursor, Codex) for a large-scale migration or repetitive task

Tell me about identifying a site-wide technical challenge and driving adoption of your solution across teams

Testing strategy: how you use Jest/RTL to keep a large front-end codebase reliable

How candidates describe it

Real Software Engineer II 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 Pinterest Software Engineer interviews

All Pinterest interviews