Market intelligence

Which employers are hiring, in which sector, in which city.

29,648 employers posted 114,948 roles across 16 markets in the last ninety days. Filter that to the city and the sector your graduates actually enter, and the placement conversation changes.

29,648 employers114,948 roles16 markets
Roles posted by cityLast 90 days
  1. 1Dubai12,766
  2. 2Bengaluru8,494
  3. 3Riyadh7,128
  4. 4Abu Dhabi5,727
  5. 5Mumbai3,092

29,648 employers · 114,948 roles · 16 markets in this window

Where the hiring is

Twenty sectors, and IT is not the whole story.

The company count matters as much as the role count.

SectorRolesCompanies hiring
IT & Software22,1437,091
Real Estate & Construction9,4743,295
Manufacturing8,3523,538
BFSI7,3572,103
E-Commerce & Internet6,5062,919
Healthcare & Pharma6,1861,848
Energy & Utilities6,0211,876
FMCG & Retail5,2131,956
Consulting & Professional Services4,9921,528
Why a tenth of the corpus sits under “Others”.

22,651 roles from 8,956 companies have not been confidently classified into a named sector. That bucket is shown rather than distributed, because spreading unclassified volume proportionally across the named sectors would make every sector figure marginally wrong and completely unfalsifiable.

Where your graduates would move

Where the roles actually are: Gulf and India, side by side.

Willingness to relocate is the single biggest constraint on a student's offer set.

CityRolesCompanies hiring
Dubai12,7664,839
Bengaluru8,4942,914
Riyadh7,1282,038
Abu Dhabi5,7271,519
Mumbai3,0921,548
Hyderabad2,9291,262
Pune2,5001,049
Gurugram2,114951
Chennai1,908880
Jeddah1,382607

Why the employer count holds

Two records that look like one company are not merged quietly.

Employer counts only mean something if the employers are real and distinct.

One company recordIts own postings, sector and size
A second company recordA near-identical name

Flagged, not merged.A repeated link is a hint, not proof. A person decides.

  • 71,785 records, not strings

    Every posting attaches to a company record. 4,003 records were added in the last cycle alone.

  • Industry and size, where known

    Company profiles carry sector and size where they can be established. Where they cannot, the field stays empty rather than guessed.

Putting it to work

Four questions this answers before your next placement season.

  1. 01

    Which employers should we be calling?

    Rank live posting volume in your city and sector, then work down it. The list is ordered by what is open now, not by who came to campus last year.

  2. 02

    Is our sector mix wrong?

    Compare where your graduates went against where the roles are. A programme feeding a sector that is contracting shows up as a divergence, not as a hunch.

  3. 03

    Should we be pointing students at the Gulf?

    Dubai, Riyadh, Abu Dhabi and Jeddah together carry more posted roles than the comparison most placement cells assume.

  4. 04

    What do our top recruiters ask for?

    Take the employers your cell already works with and read their last ninety days of requirements against your syllabus.

Explore Nexus

Five capabilities, one evidence base.

Each one is a different question about the same corpus. They share a vocabulary, so a finding in one holds up inside another.

Before you ask

What placement heads ask first.

Is this a list of companies that hire from us?

No, and the distinction matters. This is observed hiring volume - who posted a role, where, in what sector, over the last 90 days. It says nothing about whether they have ever hired one of your graduates. Cross-referencing the two is what alumni intelligence is for, and the two datasets stay visibly separate.

How current is "live"?

The default window is a rolling 90 days, because a hiring signal shorter than that is noise and one longer than that is history. Collection runs continuously against per-market schedules; the partner dashboard is versioned quarterly so a figure in a board paper is still on screen when the board meets.

How do you know two postings are the same company?

Carefully, and with a human in the loop when it is not obvious. Every posting resolves to a company record rather than a free-text employer string - 71,785 records so far. Where a match is only probable, the platform flags it for review rather than merging, because a wrong merge is invisible after the fact and silently corrupts every count built on it.

Can we filter this to our city or our sector?

Yes - country, city and sector are first-class filters, and most placement teams live in a filtered view rather than the national one. A Pune engineering campus cares about 2,500 roles across 1,049 companies in Pune far more than about the national total.

Can we see which skills a specific employer asks for?

Yes, where those postings carry descriptions. It is one of the most direct uses of the corpus: take the twenty employers your placement cell actually works with, and read what they have asked for across their last ninety days of hiring - in governed vocabulary, so it lines up with your syllabus.

Bring your recruiter list. We will show you their last ninety days.

Forty-five minutes, your employers on screen, live posting data behind them.

We reply within 48 hours. +91 88796 54341