Atomicwork is building agentic service management for modern IT teams. Atom, our AI assistant, answers and resolves employee requests where people already work, and our service desk gives IT teams one place to run everything behind it. The hard design problems here are new ones: how an agent shows its work, when it should ask a human, and how an IT team trusts software that acts on its own.

You will own product surfaces end to end: frame the problem, explore in whichever medium gets you to the truth fastest, prototype in code, and ship to production with engineers. Your influence comes from the work you ship and the bar you set for everyone around you.

It moves quickly into a working prototype, often built with Claude Code or Cursor on top of our real React components. We put it in front of customers, then refine it for system consistency and polish. Figma is where we think about systems and detail, not the only place design happens. You will help shape this process as the tools keep changing.

Agent experiences that earn trust: showing what Atom is doing and why, how sure it is, when it hands over to a person, and how to undo what it did.

Dense, operational screens for IT teams (queues, request details, approvals, workflows) that stay calm and legible at scale.

Our design system, in Figma and in code, with the frontend team.

Prototypes wired to real models and real data,



valuable enough to test with customers and to critique honestly.

Pull requests to our frontend for polish, interactions and UI fixes, reviewed like any other engineering change.

Quality after launch. You will use what you shipped, notice the paper cuts, and fix them.

Around 4–7 years designing software products, much of it in B2B SaaS. What you have shipped matters more.

You write solid HTML and CSS and can find your way around an existing frontend codebase. We build in React, so knowing it helps. You don't need to be a frontend engineer, but you should be able to ship UI polish yourself.

AI is part of how you actually work. You use tools like Claude Code, Cursor or Claude Design to explore, prototype and build, and you can explain, test and take responsibility for what they produce. You can tell a generated screen from a solved problem, say what a prototype did not prove, and argue for killing a feature when it is the right call.

A working understanding of how LLM products behave (latency, uncertainty, mistakes, non-deterministic output) and what that means for the interface.

You have built or contributed to a design system in code: tokens, components, documentation.

Something you made on your own: a side project, an open-source component, a tool your team still uses.

Experience with IT, HR or operations software.

React experience.

📌 Design Engineer- Product Management (Bengaluru)
🏢 Atomic Works
📍 Bengaluru