Product Designer

What if you could define how a country interacts with its land?

Land is the most fought over, inherited, feared and misunderstood thing in India. The documents are worse than the land. We've solved the hard back-end, document mapping and real-time access across 20+ state databases. What we're hiring for is how it should feel. Fast. Clear. Like this is how land should always have worked.

Complexity is not the enemy. Confusion is. One of those we inherited. The other is ours to fix.

What you'll own

• End-to-end design across mobile and web. Government-heavy data turned into something that lands in seconds.

• The full spread of India. Non-English speakers, first-time smartphone users, and power users, who live in the product all day. The same screen has to work for all of them.

• Our design system. Tokens, components, states, motion. Work inside it, extend it where it's thin, keep it honest.

• The brand. Landing pages, ads, social, brand assets. India's first land-tech brand is still being written.

• Real surface area. Small team, no layers. You present your own work to the people who decide.

What we're screening for

We don't expect all four. Two genuinely strong, real curiosity in the other two. A designer who's mildly good at everything has no edge, we'd rather have the edge.

1. Design thinking - can you get from fog to a screen you can defend?

You start from the user's situation, not from a Dribbble reference. You explore more than one direction before committing, and you can show the ones you killed. You can say why this layout and not that one, in words a non-designer follows. Your final screen looks inevitable, getting there wasn't.

2. Product thinking - You can name the job.

You can finish this sentence about anything you design: "I am on this screen to ___." You understand the business without letting it drive, "it converts better" is not an argument here, it's the thing we check against. You think past the happy path: back, abandon, interrupt, resume, repeat use, the support ticket it creates. And you know what every choice costs you somewhere else.

3. Systems thinking - can you absorb variance instead of passing it on?

This is the capability we weigh most heavily, and the one most portfolios fake. Can you hold altitude and detail simultaneously? The thing we're hiring for is not losing one while you're inside the other. Zoom out far enough to see the whole flow, the business, the org, the market, the ecosystem. Then zoom all the way into a 4px alignment, a tap target on a cracked screen, the exact word on a button. You notice when a new pattern is an old pattern in a new coat, and you consolidate instead of adding. Can you think in second order?

4. Brand and craft - do you have a voice, and can you hold it?

Brand is not a phase that happens after the wireframes. It is a constraint you carry into the wireframe. You know removing something is usually the stronger move. You know the difference between brand and decoration. Brand is the accumulated feeling of a thousand small decisions being consistent. It is not a gradient. You can carry one identity across an ad, an app screen and an email without it fraying.

How we work

• We ship weekly. Your work hits real hands fast, and fails there fast.
• Our standard is written down. No claim ships without its proof on the same surface. No fear, no pressure, no countdown timers. People are making the largest purchase of their lives, we don't get to be clever about it.
• We don't average. Every surface declares the one thing it's exceptional at. Balanced work is failed work.
• Feedback is direct and it's about the work. We'll teach you land records. We can't teach you judgment.
• In-office, Hyderabad.

Must-haves

You've shipped something real and can say what it taught you. Fluency in Figma. Clear written English, you'll write product copy from week one. Obsessed with how people feel using a product, not just how it looks. And AI-native, not AI-dependent, AI should raise your ceiling, not set your floor.

How to apply

Show us what you've built, portfolio plus the questions below.

1. Tell us about one project where the design was wrong the first time and you fixed it. What was wrong, and how you knew. (A short paragraph.)

2. One thing you'd change about Landeed today, flow, brand or visual, your choice and why. (Use the product first. The "why" matters more than the "what".)

1. Apply. Your portfolio and a few short questions.

2. Design assignment. Everyone who applies with a working portfolio gets it. A real Landeed problem, take-home, scoped to a weekend rather than a fortnight. There's no trick in it, it's the same kind of problem you'd pick up in your first month here. You keep the work regardless of what happens next.

3. Screening. We read your portfolio and your assignment together. The assignment matters more. We're looking for reasoning, what you decided, what you rejected, and why not polish. Lo-fi with clear thinking beats hi-fi with none.

4. Interviews. You present your assignment to the design and product teams, and we go deep on it together. Expect to be asked why more often than you're used to. That's the job, not a trap. It's also the clearest look you'll get at how we actually work.