PYRAMID OF JOB MARKET

(Top right: "50th Anniversary of leaving for USA" - "04-09-05")

THE PYRAMID OF JOB-MARKET.

HIGHLY VISIBLE

• [HEAD-HUNTING] Senior Executives 3P
• DATABASE SEARCH [Placement Agencies] Strategic HR Professionals [Eng-Mgmt-Mktg-Sales] - CITIES
• Factory Workers-Clericals-BPO-Retail Asst [Vocational] in CITIES Global Recruiter Jobseekers searching on JOB SITES.

NON-CONSUMERS

• 44 million (17% Graduates) registered with 984 Employment Exchanges World-Wide-Jobs (JAM-JAB)
• Rural Jobseekers (Manual Workers/Seasonal Jobs) Carpenters/Masons/Potters/Farm Labors

INVISIBLE

• UNEMPLOYABLE
• Need "Skills" to become employable.

(Arrows/Notes)

• Adding 3 million/yr.
• Self Employed/Owners
• Small Town Jobseekers/Fresh Graduates (5000 towns/poor internet penetration/Cannot afford Rs. 20,000 PC/can afford Rs. 2000 Mobile Phone/No job-info in local/vernacular newspapers.)

Abhi Rajeer Rajji Oct. 3, 2005

Permutations & Combinatrons

Resumes

1. Prelaunch "Starting Database" 3 Lakhs
2. Postlaunch Daily download from NON-Partners (Structured Resumes) \} \quad (\text{say})**1000/\text{day}
3. Postlaunch Daily resume-posting on PARTNER jobsites (Structured & with job-pref/mobile-no) \} \quad (\text{say})**200/\text{day}

Job Advts

1. Prelaunch "Starting Database" 50,000 (last 30 days download)
2. Post Launch daily download from NON-PARTNERS \} \quad (\text{say})**2500/\text{day}
3. Post Launch daily job-posting on PARTNER websites by their Corporate Clients (Contain Recnm. Mgr's mobile + Resume pref) \} \quad (\text{say})**200/\text{day}

In enclosed matrix, I have tried to examine various combinations of

• Job Advts
• Resumes

to understand / figure-out

Where (i.e. in case of which particular combination), it is possible to generate & deliver JAM/RAM

Where it is NOT possible to generate JAM/RAM and why? Of course, I may have overlooked some, not-so-obvious reasons.

From this matrix, following conclusions emerge:

Prelaunch databases (either of job-advts or of resumes) will not help us in generating JAM/RAM

Even daily download (of job-advts as well as resumes) from NON-PARTNER Websites (Monster-Naukri-JobsAhead) is not going to help much in generating JAM/RAM.

Generation of JAM/RAM {and even} JAB/RAB) can only come from

PARTNER WEBSITES

{i.e. Jobs \& Resumes getting posted on partner websites, because}

• Jobs & Resumes will be STRUCTURED
• Jobs will contain

Resume Pref.

Recn. Mgr's Mobile No.

• Resumes will contain

Job-Pref.

Jobseeker's Mobile No. )

So, let us stick to right-hand bottom corner only, and not waste time/effort to match any other combination.

Of course, daily downloading of job-ads must continue to sustain/grow WWJ.

But why download 1000 resumes/day from Monster-Naukri etc; even if these are STRUCTURED?

These cannot be offered for Resume-Search on partner websites, since, these do NOT show

• Industry
• Design-Level.

JAM cannot be sent to these 1000 jobseekers because, even though STRUCTURED, these resumes do NOT contain JOB PREFERENCE (May be Mobile Nos too!)

Using these 1000 resumes, we cannot generate RAM against 200 job-advts getting posted on partner websites everyday.

While filling in their "resume-pref" these 200 recruitment managers would have specified

• Industry
• Design. Level.

Which these downloaded 1000 resumes do NOT contain! Hence no RAM.

Given this situation, would it not be better to simply download only the Candidate Name / Email ID / Mobile No - instead of downloading entire resume? It will be much faster.

With this much data, we can send them email (or get PARTNERS to send) asking them to register on any partner website.

That way daily 200 resumes

can go upto 2000!

While sending email, we can also point out that

"We offer FREE resume-blasting - and that too, to the Placement Agencies of his choice"

(Other jobsites do not reveal the names of the placement agencies AND also charge between Rs. 900-1500 for blasting).

I hope jobseekers will fall for this offer. But, when they ask us to blast their resume, two benefits accrue to us, viz:

They must FIRST submit their resume [We may insist that we will blast resumes of only those candidates, who give their mobile no/give their job-preferences/give their consent to receive JAB {not JAM})]

Placement Agencies will start receiving "Knowledge profiles" - along with resumes. In turn they will forward these to their own Corporate Clients, so "Knowledge-Profile" becomes INDUSTRY STANDARD -

	Pre-launch - downloaded during preceding 30 days (say) 50,000 Advts. (Starting Database)	After launch - Daily download from NON-PARTNERS (Monster-Naukri-JobsAhead) 2500/DAY (ONGOING D’BASE)	After launch Daily posted on PARTNER Websites (say) 200/DAY (Job Advts) ONGOING DATA-BASE
Resumes Starting database 3 LAKH {Received from API / Monster - Naukri / JobsAhead}) (say)	These 50000 Advts could be from 5000 CORPORATES. Each Adv. can be treated as "Resume Preference" of all 5000 Corporates can be treated as "Registered - but no mobile no of Recnm. Mgr." So, even if we match 3 lakh resumes with 50000 advts, we still cannot send RAM to those Recn. Mgrs. (No Recnm. Mgrs Mobile and 3 LAKH because WE DO NOT KNOW their mobile no.)	No mobile no. of Recn. Mgrs in these 2500 advts - so no RAM. {Even if Adv. treated as Res. Pref.})	RAM: These 200 advts will certainly contain Resume Pref \& Mobile no. of Mgr. But 3 lakh resumes are NOT Structured for matching against "Resume Pref" hence no RAM.
PRE-LAUNCH	RAM	RAM	RAM
	JAM	JAM	JAM: 3 lakh have not given their job-pref hence matching not feasible so, no JAM.
		No job-pref for these 3 lakh Resumes hence no JAM (even if 3 lakh have given their mobile no.)
Daily download from NON-PARTNERS (Monster / Naukri etc) 1000/day	Daily download even though resumes getting downloaded daily are STRUCTURED, we do not have their "job-preferences" so we cannot send JAM to these 1000 (for these 50000 advts) - even if all have mobile nos!	No mobile no. of Recnm. Mgr in daily 2500 jobs downloaded	RAM: mobile no - in
AFTER LAUNCH	Nor can we send RAM {to these 50000 advts}) \text{ziz} \rightarrow because, we do not have their mobile no!	No job-pref. in daily 1000 resumes downloaded hence no JAM	RAM: Adv. will Contain "Res. Pref" + Mobile no Downloaded resumes are STRUCTURED Hence RAM {can be sent}). \text{RAM} \checkmark \quad \text{but without industry / Design - level}
	RAM	RAM	RAM
	JAM	JAM	JAM: "No job-pref" in downloaded resumes (even though Structured) hence no JAM
Daily posted on PARTNER Websites (Resumes) 200/day	These 200 jobseekers would have certainly given their "Job-Pref \& mobile" would have given their Mobile no {while wishing to receive JAM/JAB}).	RAM: No mobile no hence no RAM	This is what we have in mind (all along) and it is for this SCENARIO, that we are designing our Architecture / Mat SMS generation / Aggregation or Instant broadcast etc. BUT, there will be very few JAB {Since as of today, we have only 309 registrations on WWJ}) also very few RAB {because, initially there will be very few CORPORATE REGISTRATIONS on partner jobsites}).
AFTER LAUNCH	It is possible to match these 200 daily batches with 50000 {starting advts} database) and Generate JAM? [but JAB] {of course, only for those Recnm. Mgrs who have given their pref. \& mobile No}!) If they get their own post day after posting their resume on a partner website, they would be highly impressed with results! No RAM generation in this scenario Since we do not have mobile no of 5000 Recnm. Mgrs.	JAM: Can be sent for these resumes which contain Mobile no Job-pref. [Against which, these 2500 daily download gets matched]	JAM/JAB \checkmark RAM/RAB \checkmark
	JAM	JAM \checkmark	JAM \checkmark
	JAB