Atlas Design System
A themeable Angular component library used by six product teams.
- Components
- 48
- Teams onboarded
- 6
- a11y test coverage
- 100%
Available for select freelance work
I am a software engineer with a bias for shipping. Most of my work sits where product meets platform: designing the API, building the interface that consumes it, and owning the pipeline that puts both in front of users.
About
I have spent six years moving between the browser, the server and the pipeline that ships both — usually because the interesting problems live in the seams.
I am a software engineer with a bias for shipping. Most of my work sits where product meets platform: designing the API, building the interface that consumes it, and owning the pipeline that puts both in front of users.
I care about the parts users feel but never name — a page that paints in under a second, a form that recovers gracefully, a keyboard path through every flow. Lately I have been deep in Angular signals, edge rendering and the surprisingly hard problem of making CI honest.
A change that reaches users this week beats a perfect one that lands next quarter. I break work into slices that can each stand on their own.
Keyboard paths, focus order and contrast get decided while the component is being written, not in an audit six months later.
If I built it, I want the pager. Writing code you have to operate changes what you build in ways nothing else does.
Toolkit
Depth where it counts, working knowledge everywhere else. The bars are a self-assessment, not a certification.
APIs and services built to be operated.
Interfaces that stay fast as they grow.
The unglamorous work that makes releases boring.
How the code actually gets built.
Selected work
A few projects where the interesting part was not the feature list.
A themeable Angular component library used by six product teams.
An edge backend-for-frontend that cut p75 LCP from 4.1s to 1.3s.
Self-hosted observability for teams that cannot ship logs off-prem.
Experience
Six years across product companies and an agency, mostly on things people use every day.
HUB Platform TechnologiesFull-time
FoundIt (Formerly Monster.com)Full-time
Avizva SolutionsFull-time
Software Engineer specializing in scalable enterprise integrations, high-throughput automated rule engines, and technical team enablement.
References
Ashish is the engineer I hand the ambiguous problems to. He comes back with a design, the trade-offs written down, and usually a prototype that already answers half the questions.
Our checkout rewrite could easily have taken a year. He scoped it into shippable slices and we were live in eleven weeks with no rollback.
The accessibility work he did on our platform passed audit first time — I have never seen that happen before or since.
Writing
Post-mortems, migrations and the occasional strong opinion about testing.
Removing zone.js from a 240-component Angular app was less about performance and more about finally understanding when our UI updates.
Eleven round trips became one when we stopped exposing our schema and started exposing our pages.
Two themes is a config problem. Three is an architecture problem. Here is the line between them.
Let's talk
I take on a small number of freelance engagements each year — usually performance work, platform migrations or design systems. Tell me what you are building and I will tell you honestly whether I am the right fit.