Own whole surfaces, not tickets. TypeScript, Next.js, Postgres. You will build the ingestion pipeline that reads a dozen government portals, and the extraction layer that turns a 200-page scanned NIT into structured eligibility criteria.
Who fits: You have shipped something that ran unattended and stayed correct. You are comfortable being the person who decides what the schema should be.
Read tender documents for a living and turn what you learn into rules the product enforces. You will define what "similar work" means across categories, track how relaxations are actually granted, and be the reason our verdicts are right.
Who fits: Background in public procurement, bid management, or a contracting firm. You have watched a bid get technically rejected and know exactly why.
Sit with contractors in their office, watch how they currently decide what to bid on, and sell the thing that replaces it. This is a field role in the best sense.
Who fits: You have sold to Indian SMEs and can hold a conversation about EMD and turnover criteria without a script.
The product marks a judgement call as a judgement call instead of returning a confident verdict. We work the same way internally.
Whoever last sat with a bidder has more standing than whoever has the better slide. Opinions are cheap; the tender document is not.
Small team, no committees. You will push work that customers use the same week.
We do not hold anyone’s digital signature certificate, we do not take commission on wins, and we do not fabricate social proof. Those constraints are the product.
Write to us anyway. Tell us what you would build first and why. We read every one, and we have hired off exactly that before we had a role open for it.
Get in touchThe roles listed above are the ones we are hiring for now: a founding full stack engineer, a procurement research associate, and a founding go to market hire. Everything else on this page is context we would give you in a first conversation anyway, published here so you can rule us out without spending an hour on a call.
There is one pipeline and three surfaces on top of it, and every role touches all four.
The pipeline pulls live notices from NIC's Central Public Procurement Portal, the state procurement portals NIC aggregates, and GeM, refreshing every minute. That is the part with no substitute: portals that go down mid crawl, states whose forms changed last quarter, buying organisations whose names are spelled four ways across four records, categories that mean different things to different departments.
On top sit discovery, which is search and alerts across the whole live list; eligibility, which reads the tender document, extracts the criteria and checks them against a company's record with the clause and page cited for every verdict; and treasury, which tracks EMD and performance guarantees so a bidder knows what capital is committed and when it should come back. Intelligence works over award data.
The engineering role owns ingestion and extraction. The research associate decides what the extraction should conclude. The go to market role finds out whether any of it changed a bidder's decision, which is the only test that counts.
Nobody arrives fluent in this, and we do not expect it outside the research role. The fastest way to find out whether the subject holds your attention is to read what we already publish for bidders, because it is the same material a new joiner is handed.
Start with how to read a tender document, then eligibility criteria and EMD, and keep the glossary open while you do. The calculators are the arithmetic a bid team does by hand today, bid capacity being the one that decides whether a firm is even allowed to quote. Why tenders get technically rejected is the closest thing we have to a product spec.
The harder half is statute. Micro and small enterprises get specific relief under the Public Procurement Policy for Micro and Small Enterprises 2012, the MSMED Act sits behind it, and General Financial Rules 2017 governs how central purchases are run. Most figures that matter still vary by department and by tender, which is why we cite a clause rather than quote a rule of thumb. If that distinction reads as pedantry to you, this will be an irritating place to work.
We do not submit bids and we do not hold anyone's digital signature certificate. The DSC stays with the bidder, always. Reading what a DSC is and why that matters is worth ten minutes before you write to us, because candidates from adjacent industries usually assume we press submit, and the answer to why we do not tells you most of what you need to know about the company.
We take no commission on a win. We publish no customer names, testimonials or ratings, because we have none to publish and inventing them is not on the table. We are not affiliated with, endorsed by, or partnered with any government department or portal; we index what is published publicly and compete on what we do with it. Where the document is ambiguous the product says so instead of returning a confident verdict, and status shows when a source is behind.
Each of those closes off an easy growth tactic. Anyone joining should be at peace with that, because none of them are up for renegotiation in month three.
Use the Apply button on a role above. It carries the role through to the contact form so we know what you are writing about. You do not need a covering letter and there is no account to create.
Three things carry weight with us. One, something you shipped that ran unattended and stayed correct, with an honest account of where it broke. Two, a live notice picked from the tender list with a note on what you would have flagged in it, in whatever depth you can manage. Three, a bid you watched get technically rejected, and what would have caught it in time.
For the research associate, the third is close to mandatory. For engineering, a repository we can read beats a CV, and a schema you defended beats a framework you listed. For go to market, tell us how you would get a contractor in an industrial estate to show you the process he uses today, given that he has no particular reason to.
If none of the three roles fit, write anyway with what you would build first. We have hired that way before a role existed for it.
Most companies in this space hire for domain plus software, not one or the other, so the shortest route is to demonstrate both in the same paragraph. For Avsar specifically, apply against one of the roles listed above or send an open note. What moves an application forward is evidence you have engaged with the actual artefact: open a live notice from the tender list, read how to read a tender document, and tell us what you would flag in it. A CV full of government sounding keywords does less than one paragraph showing you understand why a technically compliant bid still gets rejected.
It depends on the role. For the founding engineer role, no. You will need the vocabulary within a fortnight, but the hard problems there are ingestion, extraction from scanned documents and keeping an unattended pipeline correct. For the procurement research associate, yes: the role exists to decide what a criterion actually means, so we are looking for time spent in public procurement, bid management or a contracting firm. For the go to market role, you should be able to hold a conversation about turnover criteria and EMD without a script, because contractors will test that in the first five minutes.
No. Avsar is a private company. We index tender notices that are already published publicly on NIC's Central Public Procurement Portal, the state procurement portals NIC aggregates, and GeM. We have no affiliation with, endorsement from, or partnership with any department, portal or procuring authority, and no role in how a tender is evaluated or awarded. We also do not submit bids and do not hold a digital signature certificate for anyone. If you are expecting a job where deals come from relationships inside departments, this is not that job.
This page does not publish a salary band, and we would rather not print a number we cannot hold to across every level of experience for three quite different roles. Put your expectation in your application. It is a normal question, we treat it as one, and it gets discussed early rather than sprung at the offer stage. We also do not publish headcount or funding details here, so if either matters to your decision, ask directly and you will get a straight answer.
As listed above: the founding engineer role is Mumbai or remote within India, the procurement research associate role is Mumbai, and the go to market role is Mumbai with travel. The go to market role involves sitting in contractors' offices and watching how they decide what to bid on, which is not work that survives being done over a call. The research role runs closest to the rest of the team because its output changes what the product asserts, and those arguments are faster in person.
The buyer of our product is the firm that bids, not the department that buys. That changes the job on both sides. There is no procurement cycle to win in order to earn revenue, and no department to keep happy, so the product can say plainly that a bidder does not qualify. It also means the standard is unforgiving: a contractor decides in a week whether we saved him effort or wasted it. You can see the surface everyone is judged on at discovery and eligibility, and how we position against alternatives at competitors.