Skip to content

Careers

Work on the rails India's payments run on.

Payvendors is a small team in Jaipur building consumer payments and merchant infrastructure. This page describes how we work and hire. The roles listed are sample listings until real openings are published.

How we work

Three habits, kept on purpose

  • Write it down

    Decisions, incidents and customer promises live in documents people can find later. If it was only said, it did not happen.

  • Receipts over reassurance

    We prove a payment moved by showing the ledger, not by saying trust us. The same goes for our own work: tests, logs and reviews.

  • Humans answer the phone

    Support is a team, not a queue. Engineers and product people take their turn reading what merchants and customers write in.

Open roles

Timetable of sample roles

Each row opens a short description and a demonstration application form.

Sample listings

Roles shown are illustrative placeholders until the team publishes openings; applications on this website are a demonstration and are not submitted.
  • Engineering

    Payments engineer

    Sample listing
    Location
    Jaipur
    Type
    Full-time
  • Engineering

    Front-end engineer

    Sample listing
    Location
    Jaipur or remote (India)
    Type
    Full-time
  • Operations

    Merchant support specialist

    Sample listing
    Location
    Jaipur
    Type
    Full-time
  • Product

    Product designer

    Sample listing
    Location
    Remote (India)
    Type
    Contract

Nothing that fits?

Send a general note. The same demonstration form applies — nothing is submitted.

How we hire

Four steps, no surprises

Timelines depend on the role and on you; we say at each step what happens next and when.

  1. 01

    Apply

    A short note and a link to your work. No cover-letter theatre; tell us what you did and what you learned.

  2. 02

    Conversation

    A call with the person you would work with. We talk about the role as it actually is, including the dull parts.

  3. 03

    Practical exercise

    A small task close to the real work, reviewed together rather than graded in silence. Nothing you build is used without your agreement.

  4. 04

    Offer in writing

    Pay, leave, equipment and start date are confirmed in writing before anyone is asked to decide.

What we commit to

Plainly, and in writing

No perks wall. The specifics are confirmed in every offer letter.

  • 01Pay and leave stated in writing with the offer — no verbal extras.
  • 02The equipment and software you need to do the job, from day one.
  • 03Working hours that match the support hours on the contact page, not a 24×7 rota.
  • 04Direct access to the people whose decisions affect your work.

Prefer to build first? Try the sandbox.

Every product flow on this website runs as a demonstration you can click through before you write to us.

Open the onboarding demoContact the team