Hi Friends,

Even as I launch this today ( my 80th Birthday ), I realize that there is yet so much to say and do. There is just no time to look back, no time to wonder,"Will anyone read these pages?"

With regards,
Hemen Parekh
27 June 2013

Now as I approach my 90th birthday ( 27 June 2023 ) , I invite you to visit my Digital Avatar ( www.hemenparekh.ai ) – and continue chatting with me , even when I am no more here physically

Translate

Wednesday, 12 September 2007

SUBMIT RESUME FRESH GRADUATES

 

SN.

Website

email ID/chat

Jobsearch page URL

Search criteria

Log In

.

12

devseeker.in

http://www.devseeker.in/content/search.html

$\checkmark$ Keyword box

NO

Can be Incorporated


DESIGNS FOR "SUBMIT RESUME" FORMS - INDIA RECRUITER

Class of Candidates

IT

Non-IT

Fresh Graduates

Factory Workers

Clerical Staff

Main distinguishing factor/s

S/W or H/W Skills

Functions

Main Discipline/Branch

Trade

Vocation

Currently $\rightarrow$ 86 Skills

Currently $\rightarrow$ 43 Function

Principal "subjects"/ areas of study $\rightarrow$ B.A./B.Sc. etc $\rightarrow$ Politics/Chemistry

(as evidenced from designation) eg: Carpenter Welder Electrician

(as evidenced by designation) eg: Draftsman Receptionist Clerk (typist)

Can Main factor be used to generate "Population Frequency Distribution" Graph?

yes

yes

May be.

Unlikely

Unlikely

Graph will be plotted for? (Parameter for Xc axis)

Raw Score / Percentile Vs. % of Population

Raw Score / Percentile Vs. % of Population

% marks obtained in $\rightarrow$ final year $\rightarrow$ Average for all yrs

?

?

"Raw score" will be obtained from

Weightages of "Keywords" in each 86 Skills

Weightages of Keywords in each 43 Function

Can list of Main Factor grow with time?

yes

yes

yes

yes

yes.

What will be main source for expansion of Main factors?

Current Poll-&-Tricks

Current Poll-&-Tricks

Input U/I to be developed

Input U/I to be developed

Input U/I to be developed

User Generated New "Functions/Skills"

$\rightarrow$ Will these get transferred to "Submit Resume" form automatically?

NO

NO

NO

NO

NO

$\rightarrow$ If not, who will transfer & when?

We will transfer when we are satisfied that $\rightarrow$ These are broad/generic/universal, cutting across INDUSTRIES & DESIGNATIONS $\rightarrow$ Keywords for each are relevant/appropriate $\rightarrow$ At least each keyword has been voted for a minimum of 500 times

 

Class

IT

Non-IT

Fresh Graduates

Factory Workers

Clerical Staff

If the keywords under any given "Function/Skill" are only generic and not linked/related to any particular INDUSTRY, then we are in a ridiculous situation of developing a Common graph for, let us say "SALES" (Function) for professionals belonging to $\rightarrow$ Automotive Ind $\rightarrow$ Pharma Ind $\rightarrow$ Fin Service Ind $\rightarrow$ S/W Ind which is not a "Apple vs Apple Comparison" & is totally meaningless to most HR mgnt.

How do we solve this problem? How can we present to HR Mgnt. GRAPHS for people belonging to $\rightarrow$ same Function $\rightarrow$ same Design. Level

 

Message Batch

Resume Rater V 1.0

RR V 2.0

Undeclared?

1

04/08/07

21/09/07

14/08/07

2

14/08/07

26/09/07

3

24/08/07

4

03/09/07

5

07/09/07

13

14

14/10/07

16

16/11/07

Other Target Groups

  • Jobseekers
    • Starting Batch of 2.46 L $\quad \rightarrow$ Merge of Batch of 20,000 each
    • harvested thru. Resume Rater
  • Corporates
    • Starting batch of 40000/50000 $\rightarrow$ Merge of batch of 5000 each
    • Myriad batches $\quad$ 50000 +
  • Newspaper (Ed/Hrms etc) $\rightarrow$ Single batch $\quad$ 4"/1500
  • NHRD Network $\rightarrow$ -
  • Jobsites (from Jobbot directory) $\rightarrow$ 750 $\rightarrow$ on our website (Single batch)

Comments:

  • For each Target Group "Create such an EXCEL sheet to record details of
  • what message was sent $\rightarrow$ to whom (which batch) $\rightarrow$ To ensure that we do NOT duplicate same
  • when (date) message to same batch again $\&$ again
  • Keep a WEEK's gap between 2 messages $\qquad$ 13/09/07

to same BATCH

 






No comments:

Post a Comment