Build content-sharing and discovery features on Roblox's User Sharing team

This is Roblox's Software Engineer role on the User Sharing team, building the systems that let users capture, share, and discover content — feeding directly into homepage discovery and engagement. With a 2-year minimum bar, expect a practical mix of coding fundamentals, frontend-or-backend system design, and end-to-end project ownership questions rather than deep distributed-systems architecture.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Coding fundamentals (C++, TypeScript, React, C#, or Java)
Frontend or backend depth (UI systems / APIs, services)
Basic system design (APIs, data storage, scalability)
End-to-end project ownership with increasing autonomy
Code quality, testing, and code review practices
Cross-functional collaboration and communication

Common question themes

Walk through a project you owned end-to-end, from design to launch and iteration

Describe a system you identified as inefficient and how you improved its reliability or performance

How would you design an API or data model for a content-sharing feature

Tell me about a time you had to break down an ambiguous problem with limited guidance

Describe your approach to writing testable, maintainable code and participating in code review

Tell me about a time you gave or received feedback that changed how you worked

How have you collaborated with product or design partners to ship a feature

How candidates describe it

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

All Roblox interviews