Tithi MondalBlog

Article6 min readUpdated

Job Portal Design: Screens, Filters and Resume Upload

Job portal design for India: job search filters, resume upload flow, apply steps and a recruiter dashboard, with the mistakes to avoid on each screen.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Job Portal Design: Screens, Filters and Resume Upload: cover illustration

Suppose a young woman in Asansol finishes her degree and wants her first job. She has a phone, a PDF resume made in a hurry and 15 minutes after dinner. If your job portal design asks her to fill 40 fields before she sees one job, she leaves. A job portal is a product with two sides. Job seekers want to find and apply. Recruiters want to post a job and shortlist the right people quickly.

This article covers the screens for both sides, the resume upload flow, the filters that matter, and the mistakes I would fix first.

Who uses a job app, and what does each user need?

A job app has three users: the job seeker, the recruiter and the platform admin. Each has a different goal, so each needs a different set of screens.

  • Job seeker: wants relevant jobs, clear salary and location, and an easy way to apply. Many are fresh graduates, or workers moving from a small town to a city. Most use a mid-range Android phone.
  • Recruiter: a small company owner, an HR person or an agency. They want to post a job in minutes and see the best candidates first.
  • Admin: checks company accounts, removes fake jobs and handles complaints. The same care applies to admin tables and filters.

Do not design all three at once. Start with the job seeker, then the recruiter, then the admin. The seeker side brings the traffic, but the recruiter side brings the jobs, so neither can be weak.

What are the 6 screens a job portal needs?

The six screens are search, job detail, resume upload, application tracker, recruiter dashboard and candidate profile. Together they cover the whole journey.

One search box at the top, with two fields: "Job title or skill" and "Location". Below it, show 3 to 5 recent searches and a few role categories. Show jobs in a clean list. Each card carries the job title, company, location, salary range, job type and the posting date.

2. Job detail

Put the apply button at the bottom of the screen so it stays visible while the user scrolls. Above the description, show a small summary: salary, experience needed, location, work mode (office, remote, hybrid) and last date to apply. People decide in the first few seconds, so this summary matters more than the long text.

3. Resume upload

Let the user upload a PDF or DOC from the phone, or build a simple profile instead. Many first-time job seekers do not have a resume at all. A short profile form that creates a resume for them is a real help. I cover the details in the next section.

4. Application tracker

A list with one status per job: Applied, Viewed, Shortlisted, Interview, Rejected, Offer. The tracker is the screen most portals skip, and it is the one candidates return to every day.

5. Recruiter dashboard

Show open jobs, number of applicants per job and a pipeline: New, Shortlisted, Interview, Hired. A recruiter should see the day's new applicants in one click.

6. Candidate profile

For the recruiter, show the candidate on one page: name, skills, experience, education, resume preview and action buttons for Shortlist, Reject and Message. Add a note field.

How should a resume upload flow work?

A good resume upload flow lets the user add a file in one tap, checks it immediately and shows what the system understood. The user must never wonder if the file went through.

  1. Show an "Upload resume" button and a "Build my resume" link side by side.
  2. Open the phone's file picker. Accept PDF and DOC files. State the size limit in plain words, such as "Up to 5 MB".
  3. Show the file name and a progress bar.
  4. After upload, show the fields read from the resume: name, phone, skills, last job. Let the user correct each one.
  5. Ask only for what is still missing, such as expected salary and notice period.
  6. Save the resume to the profile so the next application needs no upload.

If the resume cannot be read, say so and ask for the missing fields by hand. An error that says "Upload failed" with no reason teaches the user nothing. My guide on form design best practices explains how to keep these fields short.

How do you design job search filters people actually use?

Job search filters work when they match the questions a seeker asks: where, how much, what level and when. Show the top 4 or 5 filters, and hide the rest behind "More filters".

  • Location: allow several cities, and add "Work from home".
  • Salary: use ranges in rupees per month, because most Indian job seekers think in monthly pay.
  • Experience: fresher, 1 to 3 years, 3 to 5 years and so on.
  • Job type: full time, part time, internship, contract.
  • Posted: last 24 hours, last 7 days.

Show the number of results as the user changes a filter, such as "Show 124 jobs". Put an "Apply" and a "Clear all" button at the bottom. Save the user's last filters. For more on this topic, read my post on search and filter UX design.

What does a recruiter dashboard need to show?

A recruiter dashboard needs to answer one question: who should I call today? Everything else is secondary.

  • A "Post a job" button that is always visible.
  • A list of active jobs with applicant counts and days left.
  • A pipeline view where candidates move from New to Hired.
  • A filter by skill, experience and location inside each job.
  • Bulk actions, so a recruiter can reject 30 unfit candidates in one go.
  • A simple message template for interview invitations, sent by email or WhatsApp.

The job posting form deserves care. Keep it to title, location, salary range, experience, description and skills. Offer a preview before publishing. Small employers in tier-2 cities often post from a phone, so the form must work on a small screen too.

What trust and safety points matter on a job app?

Job seekers are often anxious and sometimes targeted by fake offers, so the app must show who is real. Trust is a design task, not only a policy.

  • Mark verified companies and explain what "verified" means in one line.
  • Never show a candidate's phone number to every recruiter. Share contact details only after the candidate applies or agrees.
  • Warn users that a real employer will not ask for money to give a job. Put this note on the job detail and chat screens.
  • Give a clear "Report this job" option.
  • Let candidates control who can see their resume.

For more ideas, see trust signals in website and app design.

What mistakes hurt a job portal?

The most common mistakes make the user work harder than the product does. These are the ones I check first.

  • Forcing a full profile before showing jobs. Let people browse first and ask for details at the moment of applying.
  • Hiding the salary. If the salary is unknown, say "Not disclosed". Do not leave a blank.
  • No application status. Silence feels like rejection.
  • Long, many-page apply forms. Reuse the saved profile and resume.
  • A crowded recruiter screen. Too many charts, too few actions.
  • English only. Many seekers are more comfortable in Hindi or Bengali. Read about regional language app design in India.

A designer maps these flows before drawing any screen. My process has five stages: understand, map the flow, wireframe, design the interface, and prototype and hand off. For a two-sided product, the flow map for the seeker and the recruiter are separate. App design usually takes 2 to 4 weeks, and the quote depends on the screens and user roles. You can read more in my guide on app design cost per screen.

If you are planning a hiring product, my UI/UX design page explains how I work, and you can reach me through get in touch.

Frequently asked questions

What filters should a job search app have?

+

Location, monthly salary range, experience level, job type and posting date. Show these first and keep the rest under a More filters option.

How many steps should it take to apply for a job in an app?

+

Three or four taps for a user with a saved resume: open the job, tap Apply, confirm the resume and submit. Ask for extra details only when the employer needs them.

What should a recruiter dashboard show first?

+

New applicants for active jobs, with a pipeline from New to Shortlisted, Interview and Hired. A Post a job button should always be visible.

How can a job portal reduce fake job posts?

+

Verify company accounts, add a Report this job button, hide candidate contact details until the candidate applies, and warn users that real employers do not ask for money.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.