Sarah Abdul Khader
Frontend-focused. Detail-obsessed. Quietly making things better.
About
How I think
I treat UI as a conversation. Every interaction is a question — does this feel right? Does it cost the user anything? If it does, it shouldn't.
How I work
Iterative and thorough. I'll write the messy version first, then clean it until it feels inevitable. The code should read like it couldn't have been written any other way.
What I care about
Performance is a feature. Accessibility is respect. Good state management is good thinking. I hold these as baseline, not bonus.
A quieter thing
I'm building dear.di — a personal AI scrapbooking app. It started as something I wanted to exist, so I made it.
Bengaluru
Home base
Frontend
Where I spend my time
dear.di
Side project
Capillary
Building
Work
Click any card to see the thinking behind it.
2026
The AI scrapbook I always wanted to exist.
Click to explore
Skills
System design
Performance debugging
Component architecture
Accessibility audits
API contract design
Experience
Capillary Technologies
2024 — Present
Bengaluru, India
Performance
Improved perceived speed with lazy loading, code splitting, and careful render work — fewer wasted frames, snappier flows.
Systems
Contributed to a shared UI foundation so product teams ship with clearer patterns and less one-off UI drift.
Innovation
Helped introduce AI-assisted workflows that reduced repetitive engineering toil and made reviews more about intent than boilerplate.
Ownership
Shipped features used by enterprise retail clients across Southeast Asia — from edge cases to polish.
Writing
Longer pieces live on Medium — here’s a highlight you can open in one click.
Thinking
01
Design
Good UI is invisible until it's broken.
02
Architecture
State management is a design problem, not just a code problem.
03
Performance
The best performance optimization is not rendering what doesn't need to render.
04
Code quality
If I have to explain why the code is structured this way, it probably needs to be restructured.
05
Craft
Accessibility is empathy at scale.
06
Architecture
A component that does one thing really well is worth ten that do many things okay.
07
Product
The user never sees your clever abstraction. They see the result.
08
Engineering
Technical debt is future you paying interest on past you's shortcuts.