PAGE 07 · ABOUT

Hi, I'm Jenil.

I'm a UX designer interested in problems where the design challenge is emotional and structural at the same time — products that have to feel calm in a stressful moment, useful without being intrusive, honest without being cold.

Based Open to relocation Looking for UX research · Product design Status Open to roles

A bit about me.

I recently completed the Google UX Design Certificate. I work in the full UX stack — research, IA, interaction, and visual — and I write Python on the side for data analysis and small tooling.

I care a lot about accessibility. The Severance project is WCAG 2.1 AA on every screen, with keyboard navigation, screen-reader landmarks, and reduced-motion respected throughout.

What I find myself drawn to: service design — products that sit between people and institutions, translating bureaucracy into something a tired person can navigate at midnight. Severance is one such product. I think there are dozens more worth designing.

TOOLS & METHODS

What I work with.

DESIGN
Figma · FigJam
Components, auto-layout, variables, prototyping. The Severance design system is built with proper Figma styles and components.
RESEARCH
Maze · OptimalSort · Treejack · Otter.ai
Card sort and tree test for the Severance IA. Otter for transcription, manual review for synthesis.
CODE
Python · HTML/CSS · Markdown
Python for small data tooling (Severance affinity-cluster stats). HTML/CSS for case-study sites like this one.
METHODS
Generative interviews · diary studies
Semi-structured interviews with vulnerable populations. Trained on Google UX Cert curriculum and IDEO Field Guide.
A11Y
WCAG 2.1 AA · Stark · screen readers
Accessibility-first design. Stark plugin for contrast verification. Manual checks for landmark roles, focus order, reduced motion.
DELIVERY
Service blueprints · design tokens · handoff
Cross-functional service blueprints. Design system documentation. Engineering-ready handoff specs.
PHILOSOPHY

How I think about design.

The Severance project taught me four things I'll carry forward:

1. Restraint is a feature.

Most products try to do more. Some products win by doing less, on purpose. The calm-mode home screen — one card, intentional empty space below — was the most-discussed surface in usability testing.

2. Tone is a design system token.

It's the most consequential token, and the hardest to defend in critique. I needed three iterations to get the calm-mode copy right.

3. Cross-list, don't bury.

Information architecture rarely fails because navigation is too deep — it fails because users have multiple correct mental models.

4. Hire a critic with lived experience.

A friend who'd been through the experience reviewed the calm-mode copy before round-2 testing. Without her note, the design would have shipped condescending.

GET IN TOUCH

I'd love to hear from you.

Whether you have a role open, want to talk about a problem you're working on, or just want to chat about service design — please reach out.

Thanks for reading this far. Whatever brought you here — I appreciate the time. — Jenil