Solutions · Business software

Job portal app: what to decide, build and test.

Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.

Decisions to make before you brief a job portal

A job portal is two products glued together, and the cold-start problem is the hardest part: no candidates means no employers, and the reverse. Most of the early decisions are about which side you fill first.

  • Candidate-first or employer-first. Candidate-first needs advertising to job seekers before there are jobs. Employer-first usually means you already have employers, for example a staffing agency or a group hiring at scale, and the portal starts as their tool.
  • Open marketplace or curated. Open posting grows listings faster but invites fake jobs and duplicates. Curated listings, where every employer is checked, are slower but easier to trust.
  • Who pays. Employers pay per job post or by subscription, or per hire. Candidates paying for placement is the model that fake-job scams use, so decide now that candidates are never asked for money and put it in the product.
  • One sector and city or everything. Frontline roles (delivery, retail, warehouse) need distance, shift and pay in the match. Office roles need skills and experience. One product rarely serves both well.
  • Your own ATS or a link to the employer's. An applicant tracking board is the reason employers come back. Linking out is faster to build but you lose the data.

Checklist for the first call:

  • Which side you already have, and how many names
  • The job families and cities in the first release
  • How you will verify an employer
  • Languages candidates speak
  • What an employer pays, and when

What goes in version 1, and what waits

ModuleFirst versionAdd laterWhy
Candidate sign-upPhone and OTP, name, city, job typeResume upload, referral linksFewer fields mean fewer drop-offs
ProfileForm with voice input in the main languagesResume parsing, skill testsVoice helps people who find typing hard
Job feedFilter by city, role, shift and payLearned matching and rankingFilters work with little data; learning needs volume
Employer accountCompany details, verification, post a jobTeam seats, bulk uploadVerification is the trust layer
Pipeline boardApplied, shortlisted, interview, offer, hiredResume search, bulk messagingWhere employers spend their day
Interview bookingPick a slot, reminder on WhatsAppCalendar sync, video interviewCuts no-shows
VerificationPhone OTP, employer documents, manual reviewID checks for candidates, background checksFake jobs ruin a portal quickly
Salary guidanceRanges entered from employer postsBenchmarks from real dataNeeds enough posts to be honest
ModerationReport button, admin queue, post takedownAutomatic scam detectionA human queue is enough at launch
PaymentsJob-post packs or subscription, GST invoicePer-hire billingBilling for results needs tracking you do not yet have

Our concept build Rolecall demonstrates a voice-profile demo in English, Hindi and Tamil, a salary check, an employer pipeline and plan pricing, all with sample data.

How the 8 to 12 weeks run, and what you supply

Seed jobs before launch. A feed with nothing in it kills the first week.
WeeksWhat we buildWhat you supply
1Scope, job categories, screens for both sidesTarget roles and cities; a list of employers you can approach
2–4Candidate sign-up, profile, voice input, job feedLanguage review for prompts, with a native speaker
3–6Employer account, job posting, verification flowYour employer verification policy and documents list
5–8Pipeline board, interview booking, notificationsWhatsApp Business account and message templates
7–9Admin and moderation queue, plans and invoicingGST details, payment aggregator account
9–12Seed jobs, beta with real employers, fixes, launchAt least a few verified employers with real openings

See the MVP guide for how to cut scope, and launching on Play Store.

How we work with you each week

The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.

  • Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
  • Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
  • Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
  • Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
  • One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.

The full version, including how the beta and user testing work across every kind of project, is on our process page.

The beta: real openings, one city

The beta is the real-employer stage in weeks 9–12. It starts once a verified employer can post a job, a candidate can apply from the feed, and the employer can move them to an interview with a WhatsApp reminder, all without an admin stepping in.

  • What's in it. OTP sign-up, the voice profile in the launch languages, the job feed with city, role, shift and pay filters, employer verification and posting, the pipeline board, interview booking with reminders, the report button and the moderation queue.
  • What stays out. Paid plans and invoicing (the beta employers post free), resume parsing, team seats, salary benchmarks and any matching beyond filters.
  • Who uses it. One city and one or two job families: five to eight verified employers with real openings, such as a retail chain's store managers or a warehouse supervisor, plus their recruiters, 40 to 60 real job seekers for those roles, and the admin running verification. You recruit the employers; the candidates come from their usual sources, job fairs or local placement contacts. Your own team posting test jobs proves nothing.
  • How they get it. Candidates install through Google Play testing, since most are on Android, or TestFlight for the few on iPhone. Recruiters use the web pipeline on a laptop and the app on their phones.
  • How long. Three to four weeks, so at least some candidates move from apply to interview to a hire or a no. Every listing in the beta is a real, checked opening.

A new personal Google Play developer account has to run a closed test with at least 12 testers for 14 days before it can publish. Count the beta candidates towards that, or use an organisation account.

What we test with real people, and the tasks we set

Testing here means handing someone a goal and watching them reach it, or not. They use their own phone, speak or type in their own language, and we don't help. About five sessions for each role shows the main gaps. We fix them and run the task again with new people.

Candidate sessions run on entry-level Android phones, often outdoors or on a shop floor.
WhoThe taskWhat we watch for
Candidate"Make a profile by speaking in Hindi or Tamil, then find a warehouse job near you on the night shift."Does voice input catch their words? Do they understand the shift and pay filters? How many give up before the feed?
Candidate"Apply for the store assistant job and book an interview slot for Saturday."Is the employer's verified badge visible? Do they get the reminder on WhatsApp? Does anything ask them for money?
Employer"Verify your company and post an opening for ten pickers with shift timing and monthly pay."Which document step stalls them? Is pay entered as a range candidates will understand?
Recruiter"Shortlist this morning's applicants and move three to interview."How fast can they move many people? Can they call the candidate from the board once the candidate has applied?
Admin"A candidate reported a job that asks for a registration fee. Deal with it."How quickly do they find the post and the employer? Is takedown one step, and is the employer flagged?

The numbers that say it's working

In week 1 you name two or three of these. If you already place people through a spreadsheet or WhatsApp, we take today's figure, like time from opening to first interview, as the baseline. The tracking is in place before the beta. We report at launch and 30 days on. We don't promise outcomes; we make them measurable.

GoalWhat we measureWhere it comes from
Candidates finish signing upShare who start sign-up and reach a complete profile, by languageApp analytics
Jobs get applicationsApplications per live opening, and openings with noneJob and application records
Employers keep using the boardRecruiters who move candidates on the board at least weeklyPipeline activity log
Interviews happenBooked interviews where the candidate turned upInterview booking and employer marks
The feed stays cleanReports per 100 posts and time to take a bad post downModeration queue
Openings get filledTime from posting to first hire markedPipeline board

What a job portal costs, and what pushes it up

A candidate side, an employer side and an admin console put this in the "two user types plus admin" tier of our app development cost guide, a ballpark of ₹10–25 lakh from a small studio. A candidate-only app for one city is closer to the single-user-type band of ₹3–10 lakh. These are ballparks, not a quote.

  • Both sides or one. The employer pipeline is roughly as large as the candidate app.
  • Voice and languages. Each language needs prompts, speech handling and review. Three languages cost much more than one.
  • Matching. Filters on city, shift and pay are quick. Ranking by learned fit needs data, and we would not build it before you have that data.
  • Verification. Manual review is cheap to build and costs staff time. Automated document checks add integrations.

Add running costs for messaging and verification, which grow with users.

India rules and habits for a job portal

  • WhatsApp reminders. Meta's platform requires the candidate's opt-in before template messages, and it must name your business. Outside the 24-hour customer service window only approved templates can be sent, and messages are billed per delivered message. Collect the opt-in at sign-up. See WhatsApp for business apps.
  • Candidate data. Resumes hold phone numbers, addresses and sometimes ID numbers. Under the DPDP Act, ask consent for specific purposes, give a notice in English or a language from the Constitution's Eighth Schedule, and let people delete their profile. Most obligations are reportedly phased in about 18 months after the November 2025 Rules. See the DPDP checklist.
  • Jobs abroad. Recruiting for overseas jobs requires registration as a recruiting agent under the Emigration Act 1983. If you will list overseas roles, check with the Protector General of Emigrants before you do.
  • Invoices. Employers will want a GST invoice for job-post packs. Set up billing details early.
  • Phones and language. Many frontline candidates use entry-level Android phones and speak Hindi or a regional language. Use OTP login, voice and short screens. See regional language apps.
  • Habits. Candidates trust a phone call more than an app notification. Recruiters live in WhatsApp. Build to hand over to both.

This is general information, not legal advice. For recruitment licensing and data protection, speak to a lawyer.

Common job portal mistakes and what to do instead

  • Opening posting to everyone on day one. Fake and duplicate listings follow. Verify employers first and publish only reviewed posts.
  • Charging candidates. It is the pattern of job scams. Charge employers, and say plainly on the site that candidates never pay.
  • Long sign-up forms. Every field loses candidates. Ask phone, city and job type, then build the profile gradually or by voice.
  • Launching with an empty feed. Recruit employers before candidates and seed real openings.
  • Showing made-up salary figures. Use ranges from actual posts and say how many posts they come from.
  • Ignoring the employer's workflow. Recruiters want to move many candidates quickly. Test the pipeline board with two real recruiters.
  • Letting contact details leak. Hide candidate phone numbers until the employer is verified and the candidate applied.
  • No retention rule for resumes. Decide how long you keep data after someone stops using the app, and write it into the notice.

Cost and timeline

8–12 weeks for a first version.

Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.

  • Candidate and employer sides, or just one
  • Languages and voice input
  • Resume parsing and matching logic
  • Verification and moderation
  • Payments for job posts or subscriptions

How app costs work in India →

Questions

About your job portal app.

What does a job portal app cost?

It depends on whether you need both sides, the matching logic and verification. Every project gets a fixed quote within 48 hours of your brief. Our guide to app development cost in India explains typical ranges. A candidate app for one city and sector costs much less than a two-sided platform with voice profiles and an employer ATS.

How do you keep fake jobs off the platform?

With employer verification, limits on new accounts, report buttons and a moderation queue. Rules such as never asking candidates for money are built into the posting flow, and suspicious posts are held for review. Candidates can see which employers are verified.

Can candidates apply without typing?

Yes. Voice profiles let candidates speak their work history in their own language, and the app turns it into a structured profile they can check. See our guide to regional language apps. Employers then see a clean, comparable profile for every applicant.

Will it work on basic phones?

Yes. The candidate app is designed for entry-level Android phones and patchy data, with a small download and screens that load fast. Many frontline job seekers use shared or entry-level phones, so we also keep sign-in simple, with a phone number and OTP instead of passwords.

Who owns the code and candidate data?

You do. Code, designs and all data are handed over in full. We also help you plan consent and data handling under India's data protection law. Nothing stays locked in our accounts. Candidate records live in your own database and cloud account.

Start a project

Tell us how your business runs. We'll build what it runs on.

Four taps, about a minute. Fixed quote within 48 hours.

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert