Senior

Own consumer-facing web features end to end for Pinterest's Product Engineering org — from prototype to scale

Pinterest is hiring a Senior Web Engineer for its Product Engineering teams in Toronto, building desktop and mobile web features for millions of Pinners. The role spans full-stack-adjacent ownership (prototyping, A/B testing, architecture, cross-functional delivery with design/product/backend) with a strong emphasis on React/Redux depth and thoughtful, verifiable use of AI in the engineering workflow.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Deep React/Redux architecture and best practices at consumer scale
End-to-end feature ownership: prototyping, A/B testing, build, launch, scale
Cross-functional collaboration with product, design, and backend engineers
Automated testing and maintainable-code practices for shared codebases
Thoughtful AI-assisted development with explicit verification/critical evaluation
Mentoring, code review, and technical decision-making as a senior engineer

Common question themes

Walk through a consumer web feature you took from prototype through A/B test to full launch

How do you use AI tools in your day-to-day engineering workflow, and how do you verify what they produce

Describe an architecture decision on the frontend that had to scale to millions of users

Tell me about a time you influenced product direction using your own product sense

How do you approach code review and mentoring junior engineers on a web team

Describe a case where you caught an error in AI-generated code or data before it shipped

How candidates describe it

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

All Pinterest interviews