Careers at OmniBizora

Build software that real businesses run on.

Not a demo, not a prototype. The systems we build are opened every morning by distributors, dealers, accountants and executives on the road — and they notice the moment something is slow, confusing or wrong. That is a hard, useful standard to work to, and it is the reason to join a team like this one.

A small team, close to the work.

We are early. That means less process, more responsibility, and a short distance between deciding something and seeing it in front of a customer.

Your work ships

What you build this month is in use next month. Nothing sits in a backlog waiting for a release train that never leaves.

You meet the business

You will sit with the people who use what you build — in a godown, an accounts room, on a dealer visit. It changes how you design things.

Real problems, not toy ones

Accounting data, field operations, messaging at scale, AI that has to be right. The problems are unglamorous and genuinely difficult.

You are not a resource

You work directly with the founder. Your judgement is wanted, your objections are listened to, and you own what you build end to end.

Where we would like to hear from you

We keep applications on file and get in touch when the work matches. Open any role to see what it involves. If none of them fits you but you think you belong here, write anyway and tell us why.

Full-stack engineerOpen applications Build features end to end — the screen, the logic behind it and the data it reads.

What you would work on

  • Dashboards, ledgers and reports used daily by business owners and their teams
  • The services that keep a customer’s data in step across systems
  • Performance and correctness on data that people make decisions with

What we look for

  • Comfortable across front end and back end
  • Care about how things feel to use, not only whether they work
  • Able to read a business problem before writing code
Integrations engineerOpen applications Connect the systems businesses already run — accounting, spreadsheets, messaging — without disturbing them.

What you would work on

  • Reading from accounting systems safely and keeping them the source of record
  • Handling messy real-world data without losing or inventing a single figure
  • Making a connection that recovers on its own when a machine is switched off

What we look for

  • Patience with other people’s data formats
  • A habit of assuming the network and the other system will fail
  • Respect for the fact that these are someone’s real books
Mobile engineerOpen applications Apps used on a bike, in a shop and in low signal — not at a desk on office wifi.

What you would work on

  • Field visits, attendance and location, built to survive a dropped connection
  • Screens a field executive can use in thirty seconds between two shops
  • Battery, data use and offline behaviour treated as features, not afterthoughts

What we look for

  • Shipped a mobile app that real people used
  • Opinions about offline-first and syncing
  • Willingness to test in the field, not only the simulator
Product designerOpen applications Design for people who never asked to use software and have no patience for it.

What you would work on

  • Interfaces that a sixty-year-old distributor and a twenty-year-old executive both understand
  • Turning dense business data into something readable at a glance
  • The product surface and the brand, kept consistent as both grow

What we look for

  • A portfolio of real interfaces, not only visual studies
  • Clear reasoning about why a screen is laid out the way it is
  • Comfort designing in the browser, or close to the people who build it
Implementation & supportOpen applications Get a business live, then make sure it stays live and actually uses what it bought.

What you would work on

  • Setting up a new customer — their data, their people, their way of working
  • Training teams who are wary of new software, and winning them over
  • Being the person a customer trusts to tell them the truth about a problem

What we look for

  • Clear Hindi and English, in speech and in writing
  • Practical understanding of how a distribution or retail business runs
  • Ownership of a problem until it is genuinely solved
InternshipsOpen applications For students and recent graduates who would rather build something real than shadow someone.

What you would work on

  • A defined piece of the product, with a mentor and a deadline
  • Engineering, design or implementation, depending on where you are strongest

What we look for

  • Something you have already built, however small
  • Curiosity about how businesses actually work
  • Honesty about what you do and do not know yet

We are a small company and we are not hiring for every role at every moment. A role listed here means we want to hear from you and will keep your application on file — not that a seat is open today. We would rather say that plainly than waste your time.

How we hire

Four steps. No riddles.

  1. 01

    You write to us

    An email with your CV or portfolio, and a few lines about what you have built and why this work interests you. No form to fill in.

  2. 02

    A conversation

    A call about your work and ours — what we are building, what the job really involves, and whether it is what you want.

  3. 03

    Something practical

    A small exercise close to real work, or a walk through something you have already built. Nothing designed to trick you, and nothing that takes your whole weekend.

  4. 04

    An answer

    A decision either way, with a reason. If it is no, you will hear that too, rather than silence.

How to apply

One email is enough. The more clearly we can see what you have actually done, the better your chances — a link to real work counts for more than a long CV.

Where to write
admin@bizoratech.in
Subject line
The role, and your name
Attach
CV as a PDF
Include a link
GitHub, portfolio, an app, anything you built
Tell us
What you built, what was hard about it, and what you would do differently
Location
Varanasi, Uttar Pradesh

Applications are read by the team directly. Please do not send the same message to several of our addresses — one is enough, and it reaches us.

If you have read this far,
we would probably like your email.

Tell us what you have built.