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

Saturday, 19 January 2008

PEER TO PEER IQ EXCHANGE

Keyword Tracking & Relevance Analysis (Google Search Logs – Dated 24/04/08)

You’ve cataloged numerous recruitment-related search terms, analyzing:

  • Indexing on Indra Pages (likely your platform’s internal metric)

  • Presence in Google’s top results

  • Global search volume comparisons

Notable Insights:

  • High-performing search terms for Indra pages: "Resume Blast" (#1), "Resume Courier" (#2), "Percentile Score" (#76), "Job Advert" (#6), "Jobseeker" (#42)

  • Some keywords had high web volumes but lacked platform visibility: "Job Search" (160M), "Keyword" (421M), "Education", "India"

  • Experimental or unique terms like "KarmaScope" and "Dead Sea Scroll" suggest innovation in branding and user metrics.


📋 Remaining Words (Uncrossed Keywords Master List)

From the "Remaining Words" scans:

  • Retained and circled keywords suggest a future taxonomy for payment/usage models and features:

    • Pay Per Use, Subscription, Micro Payment, Tariff, Payment, Balance, Credit

  • Others relate to platform logic or gamification:

    • Combo, License, Lock-in, Game, Parameter, Flexibility, Validity

Crossed-out terms suggest pruning for better UX clarity (e.g. “Comment,” “Opinion,” “Superman,” “Contribute”).


Mailing List Feature Concept (30/03/2008)

You’ve mocked up a “Reaching Out” form for visitors to join a mailing list categorized by:

  • HR Managers

  • Executives

  • Or both

Key Notes:

  • Option to auto-show past promo emails

  • Emphasis on hyperlink tracking and message preview

  • Related to the “Borrowed Ideas” module


🤝 IQ Exchange Strategy (19/01/2008)

You articulated a long-term goal for “IndiaRecruiter”:

  • Primary Objective: Turn self-created Interview Questions (IQs) into a marketing tool

  • Secondary Objectives:

    • Build the largest crowd-sourced IQ database

    • Disrupt the game by setting your own “rules” rather than playing by Naukri/Monster’s

    • Foster a Virtual Community of recruiters exchanging value

  • Would you like me to now compile all this into:

    1. A consolidated Word document (strategy + keyword tables + mailing form sketch + IQ exchange memo)?

    2. A visual infographic summarizing platform modules and insights?

    3. A modern-day adaptation of these concepts?

    Let me know your preferred output(s) and purpose — archival, blog post, investor pitch, or product roadmap.


Exchange of Self-Created Interview Questions

(IndiaRecruiter IQX Platform Proposal)
Date: 19 Jan 2008
Participants: Rahul → Swati → Shalaka


Primary Objective

To position the “Exchange of Self-Created Interview Questions” (IQX) as a powerful marketing tool and agent for IndiaRecruiter. This feature is intended to popularize and promote the IndiaRecruiter platform among professional recruiters.


Secondary Objectives

  • Build a Large, Crowdsourced IQ Database:
    Harvest interview questions (IQs) contributed by thousands of recruiters globally, capturing their collective knowledge and domain expertise.

  • Drive Mass Contribution to Stay Ahead:
    Encourage mass, ongoing contributions to the IQ repository, helping IndiaRecruiter overtake competing job portals and sustain leadership.

  • Change the Recruitment Game Rules:
    Shift the playing field by defining our own rules, rather than playing by those of Naukri, Monster, etc. Control the game by innovating the medium itself.


Strategy

1. Create a Virtual Community of Recruiters

  • Estimated 30,000 to 40,000 recruiters (including consultant-level professionals from 5,000 recruiting agencies).

  • No dedicated platform (forum or space, physical or virtual) currently exists for them to exchange insights.

  • Organizations like ERA represent only a small elite (140–150 companies).

  • Corporate recruiters are often treated as "second-rate citizens" in mainstream HR networks like NHRD.

Despite 1–2 lakh job ads carrying:

  • Recruiter name

  • Email ID or phone

  • Resume inbox

…there is no inter-recruiter dialogue or information sharing.

IQX aims to fill this void by creating a virtual peer community.


2. Create a Peer-to-Peer IQ Network

Target: 80,000 to 140,000 recruiters

  • Modelled after successful P2P file-sharing platforms (e.g., for music files).

  • Each recruiter creates IQs for 3–4 skills/functions they specialize in (out of 86 IT / Non-IT categories).

  • No one is expert across all domains.

  • Recruiters donate their IQs in exchange for access to others' IQs where they lack expertise.

Problem: Recruiters don’t know who has created which IQs.


3. Mechanism for Visibility & Harvesting

  • All users should be able to see a list of contributors and their respective domains of IQ creation.

  • When a recruiter downloads a candidate database:

    • We “harvest” the IQs they have created.

    • Their system auto-updates with the full IQ database from the main server.

  • Only incremental questions (new since last sync) are added — no duplication or bloat.

  • Each harvested IQ retains contributor's:

    • Name

    • Email ID


Prototype UI Idea for 'Reaching Out' Module

(Dated: 30/03/2008)

  • Collect email IDs from HR Managers and Executives.

  • Offer option:

    • "Add me to mailing list for: [✓ HR Managers] [✓ Executives] [✓ Both]"

  • Show list of past promo emails sent.

  • Users can opt to view or receive future promotional messages.

  • Message also includes hyperlinks and placeholders for future/batched emails.

Project Summary: Exchange of Self-Created Interview Questions (IQ)

✅ Primary Objective:

To popularize and market IndiaRecruiter by creating a viral feature that encourages recruiters to contribute and exchange self-created interview questions (IQs).


🎯 Secondary Objectives:

  1. Crowdsource a large IQ database from global recruiters across IT and non-IT domains.

  2. Create ongoing user contribution loops to consistently outpace traditional portals like Monster/Naukri.

  3. Change the game — play by “our” rules (open, transparent collaboration), not theirs.


🔧 Strategy & Mechanisms

🔁 A. Create a Recruiter Community (p2p network model)

  • Mimic peer-to-peer networks (e.g., music/file sharing).

  • Recruiters “donate” IQs on their 3–4 expert areas.

  • In return, they get access to IQs in areas where they are not experts.

📡 B. Harvesting Logic

  • When someone downloads a candidate database, their created questions are automatically harvested.

  • A mechanism ensures only incremental IQs are harvested since the last session.

🧩 C. Mapping IQs to Functions/Skills

  • Each IQ is tagged with:

    • Contributor Name/Email

    • Date of Contribution

    • Function or Skill

    • Actual Questions

📊 D. Admin Dashboard Views

  • Year-wise, month-wise, and date-wise contribution logs.

  • Cumulative stats of IQ contributions for platform insights.

UI Mockups & Features

1. Reaching Out UI (Page dated 30/03/2008)

  • Visitor selects if they want promo emails for:

    • HR Managers

    • Executives

    • Both

  • Submits email ID and preferences.

2. Contributor Display Table

  • Displays per-contributor IQ details (date, skill, actual questions).

  • Allows filtering and tracking.

3. Admin Harvest Panel

  • Tracks year/month/date-wise IQ upload counts.

  • Auto-increments with each user activity.

4. Peer-to-Peer Exchange Interface

  • Display by function (e.g., Sales, Mktg) or IT skills (e.g., Java, ASP, VB).

  • Select creators from a dropdown.

  • Shows number of questions and checkboxes to email.

  • "Open Outlook" button to initiate contact for exchange.

  • Final Concept: IQ Contributors’ Peer-to-Peer Network

    • Recruiters exchange IQs based on domain expertise and requirement.

    • A transparent, contributor-powered knowledge-sharing loop.


    ✨ Forward Path (Modernization Suggestions)

    Would you like me to now:

    • Convert this into a Word document for archiving or blog use?

    • Draft a landing page UI (React + Tailwind) for this exchange platform?

    • Build a proposal email to relaunch this feature under IndiaRecruiter or IndiaAGI?

    • Generate a visual storyboard or infographic showing the recruiter-IQ exchange loop?

    Just say the word.

  • Concept Note: Exchange of Self-Created Interview Questions

    Date: 19/01/08
    Routing: Rahul → Swati → Shalaka


    🎯 Primary Objective

    To use this feature as a marketing tool/agent for IndiaRecruiter. It should help popularize/sell IndiaRecruiter amongst recruiters.


    🎯 Secondary Objectives

    • Build a large database of IQs (Interview Questions) by harvesting the collective wisdom of thousands of recruiters globally.

    • Get thousands to contribute IQs on an ongoing basis, thereby overtaking rival job portals and remaining ahead.

    • Change the rules of the recruitment game—play it by OUR rules, not those of Monster/Naukri.


    🧩 Strategy

    1. Create a “Community” of Recruiters

    • Estimated 30,000–40,000 recruiters, across 5,000 recruiting agencies.

    • No current forum or platform, physical or virtual.

    • Existing bodies like ERA represent only 140–150 companies (mainly MDs).

    • Corporate recruiters are treated as "second-rate citizens" in professional networks like NHRD.

    🧠 Insight:
    There are 1–2 lakh job ads on portals like Monster/Naukri, with:

    • Contact person's name

    • Email ID / Phone number
      But no interaction, collaboration, or info exchange happens among them.
      IQ Exchange feature can build such a virtual community.


    2. Create a Peer-to-Peer Network (P2P)

    • Inspired by P2P music-sharing networks where members exchange files.

    • In our case, recruiters will exchange self-created IQs across 86 IT/Non-IT skills.

    • Since no recruiter is an expert in more than 3–4 functions, they will donate IQs in return for IQs they need.

    Challenge:

    • Recruiters don’t know who created what IQ.


    3. Visibility & Harvesting Logic

    Introduce a system where users can:

    • See a list of all IQ creators, by function/skill.

    • When someone downloads a “candidate database,” the questions they created get harvested.

    • Their local database gets updated from the webserver database.

    • Introduce incremental harvesting logic (new/modified questions only).

    • Track:

      • Contributor's name/email

      • Date

      • Skill/function

      • Questions added


    4. Admin Tools & Dashboards

    Sample Layouts:

    • Contributor Table → Name, Email, Date, Function, Questions

    • Admin Dashboard →

      • Year-wise → Count, Cumulative

      • Month-wise → Count, Cumulative

      • Date-wise (Feb 2008) → e.g., 1st = 30, 3rd = 60

    We aggregate contributor data and display metrics.


    5. User Display UI

    Display Module: IQ Creators Peer-to-Peer Network

    Instructions to Recruiters:
    “If you have created IQs and want to exchange them for others, here is a list of creators by skill/function. Approach them with your offer.”

    🔘 First select:

    • Non-IT Function (Sales / Mktg / R&D)

    • OR IT Skill (Java / ASP / VB)

    🧾 Then view creators:

    S.NoNameNo. of QuestionsSelect to Send Email
    1Mhatre[crossed out]☑️
    2Patel12☑️
    3Venkat16☑️

    Click: Open Outlook


    6. Email Sending Workflow

    • Outlook opens with:

      • Sender’s name auto-filled in “FROM”

      • Recipients in “BCC”

    • Sender composes message → Send

    ✅ Ensures authenticity – only verified IndiaRecruiter/Interviewer users.

    📌 Only one function/skill can be selected per exchange.


    7. Upload & Duplication Issue

    Once a recruiter receives IQs (Excel sheets), he/she uploads them to their local database.

    🧨 Problem:
    Since all created IQs are already:

    1. Uploaded to the central server, and

    2. Downloaded into the local database during PEN updates,

    → Same IQs may be received multiple times (once via peer exchange, and again via PEN sync).
    ➡️ Leads to duplication and frustration.


    Would you like the next step to be:

    • 📄 A Word document with this cleaned-up structure?

    • 📊 A visual infographic to convey the concept for potential investors or collaborators?

    • 💻 Or a prototype UI mockup for developers?

    Let me know how you'd like to proceed.

Concept Note: Peer-to-Peer Interview Question Exchange Network (PEN)

Objective:

To enable 80K/40K recruiters to create, share, and exchange interview questions (IQs) in a decentralized, expertise-driven manner, avoiding duplication and flooding, while fostering a dynamic peer-based community.


Key Concepts:

1. P2P IQ Creation & Exchange

  • Recruiters self-create their own IQs across any of the 86 IT/Non-IT functions.

  • A recruiter typically creates IQs for only 3–4 functions where they have expertise.

  • These IQs can then be donated and exchanged for other IQs from peers in domains they’re not experts in.

  • However, a recruiter does not inherently know who has created which IQs — necessitating a discovery mechanism.


2. Discovery Mechanism

  • A central list of all users and their created IQs (function/skill-wise) should be made viewable.

  • When a recruiter downloads a candidate database, their created IQs are "harvested", and their local database gets updated with all IQs harvested from the server.

  • To avoid duplication, only incrementally created IQs (new since the last sync) are harvested.

  • Metadata logged per contributor: name, email ID, date of contribution, function/skill, and actual questions.


3. Admin Dashboard View

  • Tracks harvest statistics:

    • Yearly → Monthly → Daily

    • Contributor-level contribution stats

  • Aggregated data allows tracking community contribution and trends.


4. PEN UI and Exchange Flow

  • Recruiters select a function or skill → See a list of IQ Creators.

  • View number of questions per contributor.

  • Select contributors to send an email request for IQ exchange.

  • Use Outlook to send emails with:

    • Sender’s details pre-filled in the "From" field.

    • Recipients auto-filled in "BCC".

  • Requester can specify:

    • What IQs they want.

    • What IQs they are offering in exchange.


5. Managing Duplication & Database Integrity

  • After receiving IQs from peers via email:

    • Requester uploads Excel sheets to their local IQ database.

  • Webserver does not auto-update local IQ databases during PEN downloads — thereby:

    • Maintaining the original 15,000 questions intact.

    • Preventing exponential duplication.

  • Each user adds to their local database only through direct peer-to-peer exchange.


6. System Flow & Logic (Diagram – Page 9)

  • Users A and B exchange IQs (Q = X ↔ Y) under the PEN program.

  • Their created questions are sent to the central server for metadata tracking, but not for auto-syncing to others.

  • Final architecture preserves the peer-to-peer spirit while maintaining a searchable creator registry via the central server.


Advantages

✅ Eliminates duplication
✅ Empowers recruiters as knowledge contributors
✅ Creates a vibrant community-centered exchange
✅ Encourages “give to get” behavior
✅ Systematic tracking through the Admin panel
✅ Builds a valuable national asset of domain-specific IQs


System Components

ModuleFunction
IQ Creator RegistryMaintains list of IQ creators function/skill-wise
Harvest EngineCaptures created IQs without updating local databases
Exchange DashboardUI for sending/receiving IQs
Admin Analytics ToolTracks contributions over time (year/month/day)
Local IQ DatabaseUpdated only by user-uploaded Excel files

Concept Title: Peer-to-Peer IQ Exchange via Interviewer + IndiaRecruiter


🎯 Core Objective

To enable authenticated recruiters to exchange self-created interview questions (IQs) in a decentralized, peer-driven manner—without central database duplication or server-pushed updates—ensuring freshness, engagement, and community formation.


📌 System Design Overview

1. Data Contribution

Each contributor submits:

  • Name, Email ID

  • Date of contribution

  • Function/Skill

  • Actual questions

2. Admin Harvesting

Admin tool aggregates IQs:

  • Year-wise and month-wise tracking

  • Cumulative counts

  • Contributor-wise tracking


💡 Exchange Workflow

A. UI Flow (Page 6)

  • User chooses a Function/Skill (e.g., Sales or Java)

  • Selects from list of question creators

  • Can tick names to send exchange offers

  • Clicks Open Outlook:

    • From: Auto-filled with sender’s email

    • BCC: Auto-filled with selected recipients

    • User composes the message and hits SEND


B. System Logic

  • Only one function or skill can be selected at a time.

  • A successful request implies recipient(s) send Excel sheets of IQs.

  • These IQ sheets can then be uploaded to the requester’s local database, not to the server.


🚫 Avoided Pitfalls

❌ Problem:

Duplicates flood local DBs because:

  • Same IQs are received via requests and again via server sync.

✅ Solution:

  • Webserver continues to harvest IQs for display/analytics.

  • But, it will not push updates to user’s local database.

  • Users manage their own IQ expansion via peer exchange only.


🌐 Network Strategy

⚙️ Key Mechanism: Network Externality

  • Peer-to-peer dependency encourages engagement.

  • No single-source delivery (like iPod/iTunes analogy).

  • Users must connect, collaborate, and contribute to gain.

💬 Notable Analogy:

“Just as iPod users can’t freely know or exchange songs among themselves, users must join the Interviewer + IndiaRecruiter platform to benefit from this IQ exchange.”


🏁 Outcomes Envisioned

  • Stop duplication

  • Enforce authentic peer interaction

  • Create a self-sustaining knowledge-sharing community

  • Position IndiaRecruiter + Interviewer as central hubs

Concept Summary: Peer-to-Peer Interview Questions Exchange Network (IndiaRecruiter / Interviewer)

1. Email Automation

  • When Outlook opens, sender's and recipients’ emails are auto-filled (From/Bcc).

  • Sender sends a "Request for Interview Questions Exchange."

  • Only one skill/function can be selected per request.

  • Once responses are received and IQs (Interview Questions) are emailed back, requester can upload Excel sheets to their local database.

2. Avoiding Redundancy

  • Problem: Same questions may be received repeatedly via webserver + peer downloads.

  • Central server should not auto-update users' local IQ databases.

  • Solution: Server continues harvesting created IQs for statistical display (e.g., Page 6), but does not push to local databases.

  • All additions happen via P2P exchange only.

3. Community Incentive

  • Prevent users from getting all new IQs from one central server.

  • Encourage sourcing from multiple peers → incentivizes engagement → grows community.

  • This builds Network Externality (value increases as users grow).

4. Social Recognition

  • Inspired by BitTorrent: rank users by how much they donate (not just consume).

  • Donor status = expert recognition + social prestige.

  • A "No. of Times Donated" counter is shown (e.g., on Page 6 table).

5. Architecture Guidance

  • Core architecture must stay open/flexible to incorporate future features.

  • Immediate focus: discuss and finalize minimum viable features for Phase 1.

Shared Access Protocol (Pg. 17)

  • The ADMIN shares a single User ID/Password with all 20 users.

  • Each user downloads the "Interviewer" tool individually but uses the common credentials to download the PEN database.

🔄 Example Scenarios:

UserDownload Source
ArchanaIndiaRecruiter.net
AparnaDownload.com
SonalSoftPedia.com
RishiVia email from Amit
RamyaFrom a DIGIT magazine CD

✅ Result: All access the same PEN database using Thakur's shared credentials.


🚫 Why Individual Registration is Impractical (Pg. 18)

  • It’s unacceptable to expect 20 users to:

    • Register individually on IndiaRecruiter.

    • Obtain separate User IDs.

    • Make individual payments or open separate accounts.

❗ This model is unsuitable for multi-user companies.


⚠️ Downside Acknowledged

  • All 20 users may unknowingly download the same PEN (e.g., 61140).

  • This may lead to the company paying Rs. 20 instead of just Rs. 1, due to multiple downloads.

💡 However, the low cost (Rs. 1 per download) makes this tolerable for most organizations.


However, when it comes to the question of being able to use:

“Peer-to-Peer IQ Exchange Program”

...can we insist that:

▶ Whosoever wants to “donate” or “borrow” a question, must be, not only a MEMBER, whose InterViewer is installed on his local PC and who has either independently obtained his User ID / Password or has been given User ID / Password by his company ADMIN

but

▶ Such a MEMBER must have also created at least ONE question (on any functional-skill).


Page 20

The idea / philosophy behind this is:

▶ How can we display your name in the “CREATORS LIST” (see pg. 6), unless you have created (and uploaded) at least ONE question?

We don’t want “FREE RIDERS”, who don’t want to create/contribute/share (their knowledge), but who are only interested in “borrowing”!

Hopefully, such a mandate will encourage InterViewer-Users to contribute (at least one question), in order to be able to “borrow” from others.

Of course, if I am not interested in “borrowing” any question from anybody, I can still use all the other features of InterViewer. No problem.


Page 21

Now, what happens when → Archana / Aparna / Ramya / Sonal etc. all do “create” some questions and click ADD QUESTION button?

Remember, they are all using Thakur’s User ID / Password (ADMIN).

On Pg. 6 (Creator’s List), all of these questions would appear (get listed) against Thakur’s name/email ID!

So, these contributors will not get “recognition”! They will get discouraged.

Again, how can they “borrow” from each other?

Perhaps, you will come up with some elegant solution.

🖋

(Signed & Dated: 20/01/08)