Design Engineer
Design and build the workspace where teams fix AI agents
TL;DR
We're hiring a Founding Design Engineer to shape how Neatlogs looks, feels, and works at the interface level.
This is not a standard frontend role.
We want someone with serious frontend chops and real product taste. Someone who notices when spacing is slightly off, when an interaction feels clumsy, when a layout creates cognitive drag, when a screen technically works but still feels bad.
You'll work directly with the founder and engineers to craft the core product experience from the ground up. A lot of the time, there won't be a Figma file waiting for you. You'll be expected to think through the UX, make strong calls, and ship polished interfaces yourself.
What is Neatlogs
A specialised workspace for teams that build AI agents.
The problem: Most debugging tools today are built for infra and AI/ML engineers. They're hard for business teams to use, even though those teams often hold the context needed to actually improve the agent.
So teams pass agent runs around in Slack, screenshots, docs, and calls. Feedback gets scattered. Context gets lost. Fixes take too long. And a lot of agents never make it to production.
The fix: Neatlogs is a shared workspace built on top of traces. Devs and business teams look at the same run, understand what went wrong, and move from feedback to fix in minutes.
Every wave of tech got its multiplayer workspace. Code got GitHub. Design got Figma. Agents don't have one yet. That's what Neatlogs is.
We're a small, focused team with early users, a real product in the wild, and backing from top investors across the US, India, and Japan.
Here's a walkthrough of Neatlogs:
Why this is a good hill to die on
- Agent tooling is still ugly, fragmented, and too technical. The core interface patterns for this category are not set yet. You'll help invent them.
- You won't just implement mocks. You'll make product decisions in code.
- You'll be one of the people defining what 'great taste' means inside the company.
- We are building for both technical and non-technical users. Making that feel simple without dumbing it down is a very hard product problem.
- Small details matter here. A better hierarchy, smoother state transition, cleaner empty state, tighter table, more legible trace view — these things change whether the product feels powerful or exhausting.
Here's a short deck on our vision:
View the Neatlogs vision deck →What you'll spend your days doing
- Building and refining the core UI of the product: traces, evals, comments, dashboards, filters, onboarding, settings, and collaboration flows.
- Designing in code. A lot of the time the best version of the interface will emerge directly in the product, not in a static design file.
- Making judgment calls on layout, hierarchy, interaction patterns, motion, states, and microcopy without waiting for perfect specs.
- Sweating the details: alignment, spacing, visual rhythm, typography, hover states, loading states, transitions, responsiveness, and edge cases.
- Working closely with the founder, designer, and engineers to improve workflows fast.
- Creating reusable UI patterns and components so the product feels coherent as it grows.
- Cleaning up the product constantly. Reducing clutter is part of the job.
- Helping shape the visual bar for Neatlogs across product surfaces, docs, and high-impact web experiences when needed.
You might be a good fit if…
- You've built polished product interfaces before, not just functional ones.
- You have strong frontend skills and strong taste.
- You can look at an interface and immediately spot what feels off.
- You can work from a rough idea, a conversation, or a user problem and turn it into a clean shipped experience.
- You care deeply about hierarchy, typography, spacing, and interaction quality.
- You think in user flows and states, not isolated screens.
- You can move fast without making the product feel sloppy.
- You've worked on complex products like devtools, SaaS software, dashboards, workflow tools, or internal tools.
- You don't need handholding to produce beautiful work.
You'll probably hate this if…
- You only want to implement exact mocks from Figma.
- You think 'good enough' is good enough for product quality.
- You only care about architecture and not about how the UI actually feels.
- You want highly defined specs before starting.
- You don't enjoy revisiting details until they feel right.
What we care about
| What we care about | What we don't care about |
|---|---|
| Interfaces that feel crisp, clear, and deeply considered | Pixel-perfect implementation of mediocre designs |
| Strong product judgment | Whether your previous title said 'frontend engineer' or 'design engineer' |
| Taste and attention to detail | Big company logos on your resume |
| Ability to design through code | Whether you have a formal design degree |
| Shipping real product improvements users can feel | Fancy animations with no product value |
| Clear thinking and clear writing | Performing sophistication |
What strong candidates usually have
- Strong command of modern frontend fundamentals
- Experience with React / TypeScript and building production UI
- A portfolio or shipped work that shows real product taste
- Evidence that you can handle ambiguity and still produce clean outcomes
- Good instincts on component systems, interaction design, and visual consistency
- Comfort working closely with product, design, and engineering without rigid role boundaries
Compensation and how we work
- Salary in line with top product startups, plus stock options large enough to matter if this works.
- We work remote first and do regular off sites for a few days so we can plan, hack, and hang out in person.
- Many of our users are AI startups in San Francisco. You'll hear directly from them and may meet some of them too.
- We set aside budget each year for books, courses, or conferences that make you better.
Apply
Email your best work to people@neatlogs.com or send a DM to Ajay.