Use the Product Design posting’s own terms
The Product Design internship is Early Career ID 41263. Roblox lists a 12-week Summer 2027 role in San Mateo, a Friday, October 30 cutoff written as 5 PM PST, and a $58–$58 hourly pay range.
| Field | Current posting |
|---|---|
| Early Career ID | 41263 |
| Program length | 12 weeks |
| Location | San Mateo, California |
| Application cutoff | Friday, October 30; employer wording: 5 PM PST |
| Listed base pay | $58 per hour |
| Academic fit | Undergraduate or graduate design study, or a related field |
| Office pattern | Tuesday–Thursday in office; Monday/Friday optional in-office unless otherwise noted |
The posting asks for undergraduate or graduate study in design, including UX/UI, interaction, motion, graphics, typography, web or product design, or a related field. The work includes accessible workflows, prototyping, competitive analysis, user research and design refinement with engineering and product partners.
Office-based roles are onsite Tuesday through Thursday with optional Monday/Friday office presence unless otherwise noted. The posting includes the same role-specific warning that some U.S. visa-related work authorization or future H-1B sponsorship may not be supported. Do not copy the PM role’s rolling-review language into this design application; the design posting does not state it.
Sources[1]
Build a case study around a difficult interaction
Choose one workflow where a user has a real decision to make. Explain the starting problem before the polished screens: what was the user trying to do, what did the first design make difficult, and which evidence caused you to change it?
A useful practice scenario is a fictional collaborative creator tool where a creator wants to invite a teammate without accidentally granting broader editing access. Show the entry point, permission choice, confirmation and recovery path after an error. This is practice, not a claimed Roblox product problem or interview assignment.
A short prototype that handles states, feedback and mistakes can be more informative than a large gallery that shows only the successful path.
Sources[1]
Show evidence without overstating research
Document who tested the prototype and what task you gave them. Keep observation separate from interpretation. “Two testers hesitated at the permission label” describes a small test; it does not establish a universal user belief.
Show the before-and-after change and the alternative you rejected. If you changed a label, added a consequence statement or moved a choice earlier, explain why. Include limits such as a convenience sample, no assistive-technology test or a prototype without a real backend.
Make the portfolio usable before you submit
A reviewer should be able to reach the strongest case without requesting file access. Label your contribution in group work and identify borrowed assets or components. Pair an interactive prototype with a short static explanation so the reasoning still works if the prototype link fails.
The requisition controls eligibility. A portfolio case study is preparation, not an invented additional requirement. Use the official Product Design application and evaluate any later assessment invitation separately.