Hi, I'm Oğuzhan Özcan

Senior Product Designer with 7+ years designing enterprise SaaS — currently at Jotform, previously at Enocta.

I work across the full product lifecycle: research, strategy, design systems, usability testing, and increasingly — writing the code myself with React, TypeScript, Next.js, and Storybook. This portfolio is built with Next.js 15.

I've shipped features used by millions of people: two-factor authentication, OAuth integrations, internal operations platforms, growth experiments across 430,000 users.

On the side: Kroma, a free color blindness checker for designers. The Brifl Design System, 30+ components with Storybook docs. And a published article on designing components for JavaScript frameworks.

Based in Ankara, Turkey. Open to remote work worldwide.

I studied Physics at Middle East Technical University — optics concentration, 203 credits deep. I never finished the degree, but I came away with something more useful than a diploma: a stubborn habit of asking why things work the way they do.

I taught myself design in 2019, mostly out of curiosity. I had no portfolio, no formal training, and no obvious reason to believe it would go anywhere. But design turned out to be the exact intersection of logic, creativity, and human behavior I had been looking for without knowing it. So I kept going.

My first real product role was at Enocta, designing a learning platform used by over 2 million people across 374 enterprise clients — as the only designer on the team. That forced a kind of ownership I'm grateful for. In 2023 I joined Jotform Enterprise, and in January 2026 I was promoted to Senior Product Designer.

The physics background never really left. It just showed up differently — in how I model information architecture, structure experiments, and refuse to stop at the first answer that seems to work.

At Jotform, I currently split my time between two things I care about equally.

The first is Zeus — an internal revenue operations platform I designed and product-managed from scratch. It processes millions of user records, powers the CRM and sales workflow for a 65-person team, and has contributed to significant enterprise revenue growth. Building something that your colleagues depend on every single day is a different kind of responsibility than designing for end users. I like that.

The second is growth experimentation — running A/B tests across Jotform's core user flows to improve conversion, onboarding, and enterprise lead generation. This is where I get to be the most data-driven: forming hypotheses, designing variants, reading results, and iterating fast.

Across both, my workflow looks like this: research and SQL analysis, Figma for design, Storybook for documentation, Chromatic for visual regression testing, and increasingly — React and TypeScript to ship the thing myself. I am not trying to replace engineers. I am trying to close the gap.

I build things when something bothers me enough. Kroma started because accessibility tools were either paywalled or frustrating to use — so I built a free, no-limit color blindness simulator with React and Vite and put it online. It supports 8 vision deficiency types and has no upload limits. That's it. Simple problems deserve simple solutions.

Accessibility is not a checklist item for me. During university, I taught Braille to visually impaired students. That experience made inclusive design feel personal in a way that a WCAG spec sheet never could. I integrate accessibility from the start — not as a pass at the end.

I also wrote a science newsletter during my physics years called ObservareScientia. It never reached many readers, but it taught me something I still use: complex ideas deserve clear explanations, not impressive-sounding ones.