Akshit Agrawal
Obsessing over details.. Design Engineer.. Taste, refined daily.. I own an S1000RR.. Nerd at heart.
A little about me
I get stuck on the stuff nobody puts in the ticket: the hover that lands, the redirect that doesn't flinch, the empty state that tells the truth. Taste isn't a mood board. It's what you refuse to ship.
On Harness SEI I own how customers connect their tools — and whether those connections actually stay healthy. I started in the integrations UI, then followed the same product into backend validation, monitoring APIs, the Platform 2.0/3.0 rewrite, AI coding-tool integrations, and the AI Insights agent experience. If the plumbing is lying, the interface is just a costume.
Promoted to Software Engineer II in May 2026. Still chasing the version that feels inevitable.
Good coffee, too many tabs, and a slightly unreasonable love of micro-interactions.
Blog( 1 )
Experience.
02 / THE JOURNEY- Took frontend ownership of SEI Integrations through Platform 2.0/3.0 — catalog, schema-driven wizards, OAuth/PAT, review, detail pages, re-auth. I treat every step as a micro-interaction: what loads, what waits, what reassures you that you didn't break the connection.
- Led Harness AI / Git AI (AIDI) end to end: agent setup wizard, settings, diagnostics, token regeneration, Windows-inclusive binary download, monitoring APIs, Artifact Registry delivery. The unglamorous path still gets a considered hover, an honest empty state, a recovery that doesn't panic.
- Built AI Insights past setup — spend and developer explainability, PR drilldowns, session timeline, diagnostics before the first heartbeat, parallel metric fetching — so the dashboard feels immediate, not like a report you sit through.
- Kept 1.0 shipping beside 2.0 (GitHub App for GitHub Actions, Jira Connect deprecation onto API tokens, PagerDuty, Copilot preflight). Same auth, same feeling — taste is consistency, not a redesign.
- Owned SEI onboarding across SCM, CI/CD, ITSM, then AI tools — GitHub, GitLab, Bitbucket, Azure DevOps, Jenkins, Jira, ServiceNow, PagerDuty, SonarQube, and more — OAuth, PAT, GitHub App, Connect-app. I care about the awkward providers as much as the pretty ones; that's where taste shows.
- Hardened connection and re-auth UX: redirects, state, cloud vs on-prem, scoped Bitbucket tokens, Azure DevOps OAuth. Enterprise recovery shouldn't feel like a punishment. The redirect should land. The error should tell you what to do next.
- Built ingestion monitoring and health surfaces, then extended them for push-based and AI integrations (Cursor, Windsurf, Copilot, Claude Code). 'Connected' is a micro-interaction too — it has to mean data is actually landing.
- Shipped the backend in api-levelops / Panorama for the same work: token validation, preflight, ArmorCode / Snyk / custom ingestion, data-status APIs. Better UX is cheap if the plumbing is lying. I don't ship a skin.
My toolbox.
03 / THE EVERYDAYLanguages
- TypeScript
- JavaScript
Frontend
- React
- Next.js
- HTML & CSS
- Tailwind CSS
Backend & Data
- Node.js
- PostgreSQL
Workflow
- Git
Product craft
- Accessibility
- Design systems
Design
- Figma
Let's make something.
Have a role in mind, an interesting idea, or just want to say hello?
My inbox is always open.