Rachel Chen Portfolio
Computer science and business student who designs and codes: internships at Notion (design engineering), Bloomberg and RBC (software engineering), 1Password (product design) and Onova. The homepage is a dated internship list above eight project tiles, each labelled with its status: SHIPPED, CONCEPT, CONTRACT or HANDED OFF.
Location
Coordinates unknown. Vibes: international.
Companies
Skills
Notable
- Internships at Notion (design engineering), Bloomberg and RBC (software engineering), 1Password (product design) and Onova
- RBC Amplify intern project (heyHR): her case study reports a patent application, 19.5% shorter HR advice calls and $2.1M projected annual savings
- Devpost: 13 projects across 15 hackathons, several marked winners
What makes it work
A breakdown of the choices that make this portfolio stand out.
Every project labelled with what happened to it
Every tile says what happened to the work: two 2025 concepts, a 2025 contract, work handed off at RBC in 2024, and shipped products. A confidential Amazon Alexa+ contract gets an honest "reach out to learn more" page instead of a password wall. Readers know exactly what kind of evidence each project is.
Design and engineering in the same case study
Earth and PokerGPT list her as Product Designer and Frontend Engineer, and the Earth write-up credits front-end development with sharper design decisions. The GitHub and Devpost links back it up: 13 Devpost projects across 15 hackathons, several marked winners.
NDA work handled in the open
The RBC case study states up front that NDA limits what she can show, then gives the outcomes her team reported: 19.5% shorter HR advice calls, $2.1M projected annual savings and a patent application. Being clear about what is confidential makes the numbers that are shown more credible.
What Product Designers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Label each project with its status (shipped, concept, contract, handed off) so reviewers weigh the evidence correctly.
If you also write code, show the front-end you shipped alongside the designs. It proves the handoff gap you closed.
If work is under NDA, say so on a public page and show the outcomes you're allowed to share. Don't password-protect the whole portfolio.
Case studies
A student who ships: an onboarding flow for 1Password's macOS autofill, a hackathon platform launched at a 1,000-person event, and an intern project that ended in a patent application. Each tile says whether the work shipped, stayed a concept, or was handed off.
Bringing macOS autofill to 1Password users
Designed how 1Password users discover and set up macOS autofill. She mapped possible entry points (onboarding modals, the mandatory guided setup, the core app) and proposed "Do More with 1Password": optional suggested-setup cards that reach new users in guided setup and existing users on the home screen.
It is a discovery and adoption problem, not a screen redesign: she weighed where a new capability should surface for two different user groups and designed a reusable pattern, working within technical limits she describes.
Mapped three entry points before choosing one
One pattern serves new and existing users
Reflection names the API constraints the flow had to work around
heyHR: patent-pending AI for RBC HR advice (RBC Amplify)
In RBC's Amplify internship program, her team of four interns took a real problem from the HR Technology and HR Advice teams, then designed, built and deployed an AI solution in four months. Details and designs are under NDA, which the case study states up front.
Intern work that reached production-level stakes: a real business problem, a deployed solution, measured beta results, and a pitch that won executive support.
Built and deployed in four months by four interns
Reported outcomes tied to call time and volume
Patent application filed with RBC legal
Projects
Earth: hackathon platform for Onova
Onova, an innovation consultancy, ran corporate hackathons on disconnected third-party tools. On a team of one PM, two engineers and herself, she designed and built the front end of Earth, Onova's own event platform, including a design system and a live dashboard. Beta testing showed participants struggled to find the live dashboard, so she restructured the navigation and page naming.
She owned both the design and the front end, and used beta-event feedback to fix information architecture before the big launch.
Design system and live dashboard built from scratch
Navigation restructured after beta-event testing
Launched at a 1,000+ person corporate hackathon
Tomo: an AI device concept for OpenAI (self-initiated)
A self-initiated concept by three designers answering "What should OpenAI build as its first AI device?" It is not OpenAI work. They argue memory should be OpenAI's moat and propose Tomo, a pin-and-pendant wearable camera and microphone, feeding "Moments", a new log of captured events inside ChatGPT.
It starts from a platform-strategy argument, not a gadget sketch, and makes an explicit privacy trade-off with its reasoning written down.
Strategy first: why an app-layer company needs hardware
Manual capture chosen deliberately for privacy
Designs for the people around the wearer, not only the user
More Product Designer portfolios
Ready to build your portfolio?
Follow the Product Designer roadmap — skills, projects, and timeline to get hired.