DK

Profile Submission, Screening, and Immigration Q&A – Comprehensive Notes

Utility Bill Submission Requirements

  • Only utility bills are accepted as address proof when submitting documents.
    • Ensure the bill is dated within the last one month (i.e.
      \leq 30 days old).
  • Double-check that the name on the bill matches the name on the submission profile.

Profile Submission & Record-Keeping Protocol

  • Maintain a detailed, up-to-date Excel sheet for each profile submitted.
    • Mandatory columns:
    • Candidate name (as on resume).
    • Date of submission \text{(dd/mm/yyyy)}.
    • Client name / project.
    • Prime vendor name.
    • Recruiter or manager who submitted the profile.
    • Screening date (once arranged).
  • Send a confirmation email to the team containing:
    1. Candidate name.
    2. Date & time of submission.
    3. Client enrolled.
    4. Prime vendor involved.
  • Keep copies of all correspondence (emails, chat logs, attachments) in a centralized folder or file manager.

Screening Call Preparation (Typical Questions)

  • Immigration & work authorization:
    • "What is your current visa status?"
    • "When did you enter the US and on which visa?"
    • "Are you willing to provide your passport number?"
    • "Can you work on W!!2?"
  • Current engagement:
    • "When is your current project ending?"
    • "Are you still working there? If yes, explain your current responsibilities."
  • Availability & logistics:
    • Requested time slots for interview.
    • Preference for on-site vs. remote work.
  • Motivation / job-change rationale:
    • "What is the reason for this short change?"
  • Personal identifiers:
    • Last four digits of SSN if required by the client.

Questionnaire Preparation Process (For Technical Screening)

  1. Gather sample resumes related to the specific technology stack (e.g. .NET developer) from the internal ISB database or higher IP archive.
  2. Use Ctrl+F to locate and copy key technical terms, frameworks, and tools mentioned across multiple resumes.
  3. Download the resumes to the file manager.
  4. Create a Word or WordPad document and:
    • Paste each technical term.
    • Add a one-sentence explanation of usage / context beside every term.
  5. Structure the questionnaire in three prompt blocks:
    1. Introduction Prompt: asks the candidate to introduce themselves based on the resume.
    2. Technical Points & Usage Prompt: requests detailed explanations of each tool/technology relevant to the client’s environment.
    3. Recent Client Details Prompt: drills into the most recent client/project—objectives, environment, team size, challenges, achievements.
  6. Append conclusion questions:
    • "Is this a new project or an existing application?"
    • "What future enhancements or features are planned?"
    • "Do you have any questions for us?"
  7. Finish with filler / compliance questions (passport, W-2, timeline, etc.) to capture mandatory HR data.

Timeline & Visa / Green-Card Scenarios (Illustrative Examples)

  • Date of first US entry: 02/2017 on H!1!B.
  • Green-card path example 1:
    1. Filed I\text{-}140 through employer.
    2. Approved under EB\,3 category.
    3. Received GC; later shifted to E\,P1 / E\,P2 / E\,P3 as applicable.
  • Green-card path example 2 (Derivative Applicant):
    • Came to the US on H!1!B.
    • Married a green-card holder in 2020.
    • Spouse held an approved I\text{-}140 under EB\,3 → derivative code E\,39.
    • Obtained own GC as derivative (E\,39 class).
  • Family-based scenario:
    • Married a US citizen → received CR\,6 (two-year conditional).
    • Filed I\text{-}751 to remove conditions → permanent GC upon approval.

Sample Answers to Common Immigration Questions

  • "How did you obtain your GC?"
    • "I was selected in the H!1!B lottery while working in India, joined the US client in 2017, filed my I\text{-}140 under EB\,3, and received my green card once it was approved."
  • "Explain your derivative E\,39 status."
    • "My spouse’s I\text{-}140 was approved in EB\,3. As a derivative applicant I was classified under E\,39 and received my GC accordingly."

Reason for Project Change (Suggested Response)

  • "I have successfully completed the system-development phase of my previous project. I am now seeking a new opportunity that allows me to grow further, tackle new challenges, and contribute to impactful solutions."
    • Emphasize desire for skill growth, alignment with company goals, and readiness for immediate contribution.

Practical & Administrative Reminders

  • Always save questionnaires and resume versions using a clear naming convention (e.g. _v.docx).
  • Use Ctrl+P → Save as PDF to preserve layout before sharing.
  • Store any chat transcripts or WhatsApp voice notes related to submissions in the same project folder for audit readiness.
  • Confirm every scheduled screening with both candidate and vendor to avoid no-shows.

Closing & Next Steps

  • Ask candidates: "Do you have any final questions for us?"—encourages engagement and uncovers hidden concerns.
  • Thank all participants and reiterate next milestone (e.g. client interview date, documentation deadlines).
  • End communications with a courteous sign-off: "Thank you, looking forward to working with you."