Skip to content
Rudvanth

, Careers

No open roles today. That will change, here is what to expect.

We are early and small. Rather than post aspirational listings, this page tells you honestly what we will hire for, how the process works, and how to be first to know.

01What we look for

Four things, consistently.

Note what is absent: a required degree, a years-of-experience floor, or a specific stack. None of those have predicted much for us.

01

You have shipped something that stayed up

Not a demo. A system that other people depended on, that broke at some point, and that you were responsible for fixing. That experience changes how someone designs software and it is difficult to acquire any other way.

02

You are suspicious of your own results

The instinct we hire for is the one that says “that number looks too good” and goes to find the bug. Most AI work fails on unexamined assumptions rather than insufficient cleverness.

03

You write clearly

A design document, an honest post-mortem, a comment that explains why rather than what. Writing is not a soft skill here; it is how a small distributed team stays coherent.

04

You want depth over breadth

We work on a small number of things for a long time. If you would rather touch twenty technologies this year than understand two of them properly, you will find this frustrating.

02Process

Four steps. Roughly two weeks.

  1. 01

    Written exchange

    You send us something you have built or written. We reply with specific questions about it. No cover letters, no keyword screening.

  2. 02

    Technical conversation

    Ninety minutes on a real problem from our actual backlog, with the engineers you would work with. No whiteboard algorithms, no trick questions.

  3. 03

    Paid work sample

    A scoped piece of real work over a few days, paid at market rate. We think it is unreasonable to ask for unpaid labour, and it tells both sides far more than an interview does.

  4. 04

    Decision, either way, with reasons

    You get a clear answer and an explanation. Being ghosted after a work sample is the kind of thing we are trying not to become.

Register interest

Send a short note to careers@rudvanth.com with one link, a repository, a paper, a write-up, a system you are proud of, and one paragraph on what you would want to work on here. We keep these, we read them, and we come back to them first when a role opens.

We are particularly interested in hearing from people working on evaluation methodology, retrieval systems, and Indian-language speech and text.