Ramesh
Mandal.

Seven years is long — I'll be direct about that. But IndiGo isn't one product; it's 15+ different products across booking, operations, loyalty, and enterprise tools, each with its own user base, constraints, and politics. I've worked with product managers from IITs, engineers with zero design appreciation, and C-suite stakeholders who measure everything in rupees. The industry is aviation. The work is scaling digital systems under pressure — and that transfers. I've also been consulting at Intelegencia across US, UK, and Middle East markets since 2025, specifically to stress-test my adaptability. So far, the patterns translate.

Both — and I think that's a feature, not a confusion. I lead teams, but I still get into Figma. I run design reviews, but I also run user sessions myself. At IndiGo I led 15+ designers while remaining the design decision-maker on the most critical flows. I've seen leaders who 'went management' and lost their craft instinct — they make bad calls because they've forgotten what it feels like to struggle with a layout. I haven't. What I offer is strategic leadership with practitioner credibility. If you need someone who only manages up and never gets their hands dirty — I'm probably not the right fit.

Two things I'll own publicly. First: I shipped a booking confirmation redesign that tanked NPS by 12 points because I optimised for visual quality without accounting for familiarity loss. 50 million people had automated a specific screen — we moved things, they noticed. We fixed it in 3 weeks, but I should have caught it in research. Second: in my early management years, I protected my team from difficult stakeholder feedback instead of preparing them to handle it. It felt like leadership. It was actually avoidance. The designers who grew fastest were the ones I put in the room, not the ones I shielded. I corrected both — but they're real failures.

Honest answer: if you need someone with deep consumer app experience at a company known for design culture, a Swiggy or Razorpay hire probably wins. I haven't worked in that environment. What I have done is shipped UX at genuine scale — 50M+ users — in a company where design wasn't the default language, which means I've had to earn every stakeholder's trust with evidence, not reputation. I've built systems from scratch, convinced engineers to delay a sprint for a UX fix, and turned NPS data into a budget conversation. That's harder to do when everyone already believes in design. If you want someone who can operate in ambiguous, high-stakes environments without a design-first safety net — that's my background.

Open to both, with clarity on what I bring to each. As an IC, you get senior-level craft with strategic context — I won't just execute briefs, I'll question the brief when it needs questioning. As a leader, you get someone who still designs, which means my feedback in reviews is specific rather than directional. What I'm not well-suited for: pure execution roles where the design decisions are already made and I'm just producing. That's not a seniority issue — it's a boredom and attrition risk for both of us.

I'll give you the actual feedback patterns rather than a self-assessment. What I hear consistently: direct, sometimes uncomfortably so. Good at cutting through ambiguity quickly. Gets frustrated when process substitutes for thinking. Brings rigour to research that most designers skip. Makes good calls under pressure. Where I get harder to work with: I have low tolerance for decisions made by seniority rather than evidence, and I'll say so. I work best with teams that want to be challenged, not just supported. If the culture rewards deference over debate, there'll be friction.

No — and the distinction matters. I use Claude for research synthesis: clustering 40 interview transcripts into themes in 40 minutes instead of 4 hours. I use Figma AI for generating layout variants to explore, not to ship. I use AI for first-draft UX copy that I then rewrite. The judgment — which insight matters, which layout works, which copy is honest — is still mine. AI removes the friction from the parts of design that don't require creativity, so creativity gets more time. If you're evaluating whether I'm intellectually lazy: look at the case studies. The thinking in them is mine.

Yes — and I have the certificate to prove it, though that's not really the point. I'm a certified Full Stack Developer, which means I understand the full stack of constraints engineers are working within: component architecture, state management, API dependencies, performance budgets. In practice this means I don't design things that are expensive to build for no good reason, I can read a pull request and understand what changed, and when an engineer says 'that's technically complex', I know whether they mean genuinely complex or just unfamiliar. Design-engineering friction is one of the biggest delivery bottlenecks I've seen — understanding both sides of the conversation is how I eliminate it.