Software Engineer (Frontend)

About the role

Velt’s platform is trusted by industry leaders including Altana and Freshworks. We build the review and approval infrastructure for AI agents.

Here is the problem. Companies are now shipping agents that do real work. The agents write code, move money, email customers, change records. Almost nobody trusts them to do any of it unattended. So every one of these companies ends up building the same thing: a queue where a human looks at what the agent wants to do and says yes or no, plus the audit trail to prove who said yes. It takes them a quarter. It is not their product. We give them an SDK and it takes them an afternoon.

The catch is that our UI shows up inside their product, so it has to look like they built it. A dense enterprise console and a stripped down consumer app should both feel like the review queue was theirs all along. Today that means we expose a lot of knobs and hope we guessed right about which ones people want. That does not scale. There are infinite ways an app can look and we cannot enumerate them in advance.

So we want to attack it from the other side. Instead of a developer reading our docs and hand writing theme configs, an agent should read their design system, look at their code, generate the tokens and component overrides, show them what it will look like, and open a PR. Building that is the job. You would own both halves: the customization surface itself, and the agents that drive it.

This is an unusual frontend job, in a good way. Most frontend work is making one app look right. This is making our components look right inside apps you have never seen, written by people you have never met, and doing it automatically.

What you need to succeed:

- You have written a lot of CSS and are not afraid of it. Theming, design tokens, shadow DOM, style isolation, layout.

- You have built something real with LLMs. Prompting, tool calling, structured output, evals.

- Taste. You can look at a component and tell whether it is merely correct or actually right. This part is hard to teach.

- Strong communication skills, both written and verbal.

- You have shipped at least one library or SDK used by other developers.

- Deep understanding of modern web languages, API and frameworks.

- Relevant experience of atleast 1 year building two of these:

- SDKs, widgets or component libraries that other developers use

- scalable component libraries and design systems in JavaScript or TypeScript

- headless or composable UI primitives with slots, render props or wrappers

- AI tools that generate code or UI

What you will do

- Make every part of the Velt SDK UI customizable. Themes, design tokens, dark mode, layout overrides, slots, and fully headless pieces for teams that want to build their own UI on top of our logic.

- Build the agents that do the customization for people. They read a customer's design system and app, generate the theme and the overrides, preview the result and ship it. You design the tools, schemas, evals and guardrails that keep the output sane.