Electrical Engineering @ uOttawa · Building toward Product Management
I design and ship products from the first user problem through launch and what comes after. EE gives me systems depth; product work is where I decide what to build, for whom, and why.
- Start with the person who is stuck, not with a stack demo
- Scope tightly, ship something real, learn from usage
- Write tradeoffs down: what I chose, what I cut, what I would change next
- Stay close to execution (React Native, Expo, APIs, design systems)
| Product | Problem | What shipped | Links |
|---|---|---|---|
| StudentOS | Academic life is fragmented across calendars, tasks, and notes | Closed-beta academic OS: home, classes, calendar, focus, Ask AI, school-email OTP | Repo · Demo · Case study |
| SIgns | Spoken-language apps dominate; sign learners lack a clear path | Mobile learning product (team of 2): dictionary + structured lessons on React Native | Repo · Case study |
| Portfolio | Case studies need a product narrative, not a project dump | Personal site framed as problem → users → decisions → shipped → learned | Live · Repo |
- Running StudentOS through closed beta and the App Store path
- Strengthening product writing: problem framing, decisions, outcomes
- Building toward PM roles where technical judgment and user empathy both matter
Product: discovery, prioritization, tradeoff docs, Figma, user feedback loops
Build: TypeScript, React Native, Expo, Next.js, Node.js, PostgreSQL
Systems: Electrical Engineering fundamentals, embedded / systems thinking
Open to conversations about product roles, student tools, accessibility products, and technical PM paths.
- Portfolio: rayannsagnon.com
- LinkedIn: linkedin.com/in/rayannsagnon
- Email: rsagn083@uottawa.ca
EE student who ships. Proof lives in the repos and case studies above.