Senior/ Lead Product Designer

Itilite; Bengaluru; On-site; INR 900,000 - 1,800,000; Full time

Job summary

ITILITE is building AI-first travel & expense platforms in Bengaluru. We seek a senior designer to shape everyday experiences and AI agents that work alongside people.

You will define when agents act, explain intent, and ensure the design system supports complex workflows while maintaining a consumer-grade UX. Join a team that blends business needs with delightful product design.

Qualifications

• Senior (5 to 7+ years): own a complex product area end to end.
• Lead (6 to 9+ years): led designers or a product area.
• You work well with engineers and PMs and can explain your reasoning.
• You have experience with AI-assisted workflows or prompts.
• You bring craft and systems thinking to design problems.

Responsibilities

• Own everyday products: Travel, Expense, and Cards workflows end to end.
• Define when an agent acts, asks or hands back control and show intent.
• Improve the design system and patterns for AI states and workflows.
• Work with product and engineering from problem to launch.
• Lead critiques and uplift design craft across the team if in Lead role.

Skills

Tast e you can defend

Craft and systems thinking

Complex products

AI in workflow

Nice partner

Figma

AI prototyping tools

React

CSS

HTML

Tools

Figma

AI prototyping tools

React

CSS

HTML

Job description

Design the product people use, and the AI agents that work alongside them

ITILITE runs business travel, expense management, and payments for 500+ customers, with $50M+ in booking volume. We're building on two fronts at once.

• The first is the digital experience people use every day to book, approve, expense and manage spend. 500+ customers and 100k+ users rely on it, and there's plenty of craft left to put into it.
• The second is an AI-first layer, where a growing team of AI agents does the work for people: booking, rebooking, approvals, expense coding and reconciliation. These agents act in the real world, where mistakes cost money and people need to know when to trust the machine.

You'll design for both, and where they meet. When should an agent act, and when should it ask? How does it explain itself? Whether someone is clicking a screen or talking to an agent, it should feel like one product.

B2B2C: business buyers, consumer-grade expectations

We sell to businesses, but the people who feel the product are their employees, and they compare us with the best consumer apps they use. So the bar is the delight of a B2C product with the control a business needs. That's a rarer and more interesting design problem than either one alone, and it's why this work is more fun than "business software" sounds.

Persona

• Buyer (finance, procurement, leadership) cares about Cost, visibility, return on investment. Your design question: How do we prove value without burying them in dashboards?
• Admin (travel and finance ops) cares about Control, audit-readiness, fewer escalations. Your design question: How do we give them control without making them the bottleneck?
• Employee (the traveller, the user) cares about Speed, convenience, no friction. Your design question: How do we make the right choice the easy choice?

Cost, convenience and control pull against each other, and we don't want you to pick a winner. We want the design where all three feel the value, whether the work is done by a person or an agent.

We're in the 1-10 journey. The foundations are solid, the guardrails are sensible, and a good idea reaches production in weeks, not quarters. You won't start from a blank page, and you won't wait on a chain of approvals either. The design system works the same way. Think of it as a house that's mostly built: the foundations are poured, the walls are up, and most rooms already work well. A few rooms are still unfinished, and a few we'd happily knock through if you showed us a better way to live in them. Pick a component that's been bothering you, rethink it, and tell us where the walls should move. You won't redraw the blueprint, but you will shape it.

What you'll own

• The everyday products. Travel, Expense, and Cards—all three. Booking, approvals, expenses, card management, and the admin tools behind them. You'll make complex workflows feel clear and effortless, and sweat the details that make a product feel finished: empty states, errors, latency, edge cases, accessibility.
• How people and AI agents work together. You'll define when an agent acts, asks or hands back control, how it shows intent and confidence, how people review, override or undo its work, and how an admin supervises many agents at scale.
• The machine that makes concepts. A PM writes a PRD, and a workflow turns it into four or five solid concepts grounded in our design system. A designer steps in to steer the styling and make the two or three decisions that matter. We don't want our best designers hand-building prototypes or running twenty prompts. We want them to design this workflow once, so anyone on the team, PMs included, gets strong starting points in minutes. You'll own it and keep improving it.
• The design system. Improve the components and patterns that matter most, build patterns for AI states and complex workflows, and keep it coherent so AI-generated concepts meet the same bar as what we ship.
• Decisions that move the business. You'll work with Product and Engineering from problem to launch, build research into a team habit, and use funnels, session data and support conversations to find where people struggle. When a problem is hard, you'll lay out the real options, say which one will work and why, and tie it to outcomes like booking completion, policy compliance and support volume.
• If you're coming in as Lead, you'll also set the bar for craft, research and AI-assisted workflows across the team, run critiques, and grow the designers around you.

Who we're looking for

• Taste you can defend. You explore several directions fast and explain why one beats the others, with logic and evidence, and you understand the business well enough to connect a design choice to cost, risk or retention.
• Craft and systems thinking. Your work shows sharp interaction and visual design, and you care about design systems the way some people care about a garden: you know what to prune, what to let grow, and when to leave well alone.
• Complex products, new interfaces. You've shipped products with more than one kind of user, and you're curious about AI, agent or copilot experiences, whether you've shipped them or built side projects that show how you think.
• AI in your own workflow, and in your team's. You've turned a way of working into something other people use: a workflow, an agent, a prompt library, a template.
• A good partner. You work well with engineers and PMs, explain your reasoning, and make progress while things are still changing.
• Comfort with Figma, AI prototyping tools and a little code (React, CSS, HTML, Cursor, Claude Code) helps. None of it replaces design judgment.
• Senior (5 to 7+ years): you can own a complex product area end to end and ship it without hand-holding.
• Lead (6 to 9+ years): you've led designers or a product area, and built the workflows and standards a team runs on.

What you get

• Real ownership of an important part of multiple products, with a direct line to product & design leadership.
• A rare design challenge: consumer-grade experience at business scale, with AI agents in the mix.
• Room for your craft: a strong design system to improve and real customer problems to solve.
• An AI-first way of working, with the tools and space to build workflows that make the whole team better.

This role may not be for you if

You want a blank canvas, or a place where every change needs a long chain of approvals. You'd rather build a design system from scratch than shape a good one. You'd rather hand-build every prototype than build something the whole team can use. Or you want to work only on AI, or only on traditional screens, when this role needs both.

If you read all that and felt a little excited, we'd like to meet you.