EB-2 NIW for Pakistani IT and Data Science Professionals

Mapping your background to the three-prong framework

USCIS evaluates NIW petitions under three prongs from Matter of Dhanasar: (1) substantial merit and national importance of the proposed endeavor, (2) whether the petitioner is well-positioned to advance it, and (3) whether waiving the job offer and labor certification benefits the US. A resume lists roles and tools. An endeavor statement describes a forward-looking undertaking and its consequences, supported by what the petitioner has already built.

Reframing technical work

• Resume language: "Built ETL pipeline processing 2TB/day using Airflow and Spark for retail client."

• Endeavor language: "Proposed endeavor: developing scalable data infrastructure methods that reduce latency and cost in supply-chain analytics for mid-size US manufacturers, addressing a documented gap in domestic logistics resilience."

• Resume language: "Published paper on transformer-based anomaly detection."

• Endeavor language: "Proposed endeavor: advancing anomaly-detection methods for industrial control systems to reduce cybersecurity exposure in US critical infrastructure, building on peer-reviewed work already cited by researchers in the field."

Organizing evidence by prong

For each project, deployment, or publication, note which prong it supports: merit/importance (impact, field relevance), positioning (credentials, track record, ongoing role), or waiver benefit (why standard labor certification is impractical given the endeavor's scope). A single artifact — a deployed model, a patent, a GitHub repository — can support more than one prong if described with enough specificity.

Credential evaluation for Pakistani degrees

Step 1: HEC attestation

Before a US evaluator will touch your transcript, it needs Higher Education Commission (HEC) attestation. Submit your degree and transcript to HEC (in person or through their online portal) for verification and attestation — this confirms the issuing university is recognized and the documents are genuine. Universities like NUST, LUMS, FAST, and COMSATS are all HEC-recognized, but attestation is still a required step, not a formality to skip.

Step 2: US credential evaluation

Once attested, send the documents to a NACES or AICE member organization for a US equivalency evaluation. Confirm current membership on naces.org or aice-eval.org before choosing an evaluator, and check fees and turnaround directly with them — both vary by evaluator and change over time.

Course-by-course vs. general evaluation

A general (document-by-document) evaluation states the US degree equivalent — useful as a baseline. A course-by-course evaluation breaks down individual classes, grades, and credit hours, mapping them against a US curriculum. For a BS/MS in Computer Science or a related field, course-by-course is the stronger choice when you need to demonstrate specific coursework (e.g., machine learning, distributed systems) relevant to your proposed endeavor, not just an equivalent degree level.

Building the personal statement / endeavor statement

Structure

Use six labeled sections, in this order: (1) Background — one paragraph on education and career trajectory; (2) Proposed Endeavor — a specific, bounded description of the work going forward, not a job title; (3) National Importance — tie the endeavor to a named sector (health data infrastructure, grid security, agricultural forecasting) with sourced statistics, not adjectives; (4) Methodology — datasets, platforms, and technical approach; (5) Why Well-Positioned — credentials, track record, prior results; (6) Why Waiver Benefits the US — why requiring a labor certification would slow or block the work. Target 4–6 pages, double-spaced, written in first person but factual — no promotional language.

Citing work without overstating it

Name the system, dataset, or repository, and attach the letter or exhibit that verifies it. Avoid adjectives that imply an outcome USCIS hasn't seen documented.

Vague: "My fraud detection model transformed risk management for banks." Specific: "The gradient-boosted fraud detection model I built for [Bank], described in Exhibit D at pp. 12–14, processed 2.3 million transactions daily and is referenced in the bank's 2023 technology report (Exhibit F, p. 3)."

Assembling recommendation letters that hold up

Petitions in this profile commonly include somewhere between five and eight letters. A useful split is roughly half from people who worked with the petitioner directly — supervisors, PIs, collaborators — and half from independent experts who know the work by reputation, publication, or review, but never worked with the petitioner. Too many letters in either direction invites scrutiny: all-independent looks unverifiable, all-supervisor looks self-interested.

What each letter needs to state

Every letter should, in the writer's own voice, identify one or two specific projects, describe the petitioner's specific contribution (architecture decision, model design, dataset built, pipeline deployed), and give a metric or concrete outcome — latency reduced, throughput handled, users served, citations received, adoption by other teams. A letter that could apply to any competent engineer is not doing its job.

Failure modes to check for before filing

• Multiple letters with matching sentence structure or phrasing — a sign of a shared template.
• Letters that paraphrase the resume rather than describe firsthand knowledge.
• Writers who never worked with or reviewed the petitioner's actual output.
• Praise with no attached project, number, or system name.

Draft each letter's content from the writer's own account, not a boilerplate the petitioner fills in for signature.

Documenting publications, patents, GitHub, and citation evidence

Citation counts

Pull a dated screenshot and CSV export from Google Scholar (author profile page) and from Semantic Scholar (author page, which also shows an influential-citations metric). Record the date pulled — these numbers move, and USCIS sometimes flags undated citation claims.

GitHub contributions

For each repository cited, capture: commit count and date range (git log --author), stars/forks at time of writing, and a short excerpt from the README or documentation showing what the project does and who uses it. A contributor graph screenshot is useful; a bare repo link is not.

Conference and journal papers

List each paper with venue, year, and — where the venue publishes it — the acceptance rate for that year (NeurIPS, ICML, and most IEEE conferences post this on their site or in post-conference summaries). Do not estimate an acceptance rate if it isn't published.

Patents

Include filing receipts, publication numbers, and current status (provisional, pending, granted) from USPTO's Patent Public Search or the relevant national office.

File organization

Use a flat, dated scheme inside the evidence folder, e.g.:

03-Evidence/Publications/2023-ICML-paper.pdf
03-Evidence/Publications/2022-IEEE-conf-acceptance-rate.pdf
03-Evidence/GitHub/2024-repo-contrib-summary.pdf
03-Evidence/Citations/2024-11-scholar-profile.pdf
03-Evidence/Patents/2023-provisional-filing-receipt.pdf

Salary, market-rate, and comparable-wage documentation

Pull the wage benchmark

1. Identify the SOC code closest to the proposed endeavor (e.g., 15-1252 Software Developers, 15-2051 Data Scientists, 15-1212 Information Security Analysts) using O*NET's SOC search.
2. Go to the FLC Data Center (flcdatacenter.com) and generate an OES wage report for the relevant metro area or national level, capturing Levels I–IV wage figures and the report date.
3. Save the PDF export as 06-Wage/OES-15-1252-[Area]-[Year].pdf; note that these figures update periodically, so pull a fresh report close to filing rather than reusing an old one.

Compare against actual compensation

• For Pakistan-based income, convert salary slips or employer letters to USD using a stated exchange-rate source and date, and place the conversion math in a short cover note rather than embedding it in the letter itself.
• For US-based income, compile W-2s, 1099s, and recent pay stubs covering the relevant period; label each 06-Wage/US-Income/[Year]-[DocType].pdf.

What to avoid

Do not present wage comparisons as proof of qualification — document them as factual compensation history only, letting the officer draw connections to the endeavor's value.

Assembling the petition packet and index

Before fixing exhibit letters and form numbers, decide on the physical and digital structure the whole packet will follow, since every later addition — a new letter, a late-arriving transcript evaluation — has to slot into that structure without renumbering everything.

Decide on filing format first

Check uscis.gov for the current filing method for the I-140 (paper or online) before building the packet, since pagination and exhibit tabbing differ slightly between a physical binder and a PDF bundle. If filing on paper, plan for a single continuously paginated PDF or physical stack per exhibit, not per document, so page numbers stay stable once referenced in the index.

Set a master folder structure

Mirror the eventual exhibit order in your working folders now: 00-Forms, 01-Cover-Letter, 02-Endeavor-Statement, 03-Evidence (with subfolders for credentials, letters, publications, wage data), and 04-Index. Keep a running draft of the evidence index inside 04-Index from the start, updating it every time a document is added or replaced, rather than reconstructing it at the end.

Reserve exhibit letters early

Assign exhibit letters to categories before every document exists, so a missing letter or a delayed evaluation doesn't force a full renumbering later — the specific letter-to-category mapping is covered in the next section.

Assembling the petition packet, form set, and evidence index

Core forms

• Form I-140, Immigrant Petition for Alien Worker — check uscis.gov for the current edition date before filing; USCIS rejects outdated editions.
• Form G-1145, e-Notification of Application/Petition Acceptance — optional but recommended for tracking receipt notices electronically.
• Fee worksheet — confirm the current filing fee and any applicable Asylum Program Fee on uscis.gov; do not rely on figures from older articles or forums.

Tabbed exhibit scheme

Use lettered exhibits, tabbed with physical or PDF bookmarks, in this order:

• Exhibit A — Endeavor statement
• Exhibit B — Credential evaluation (HEC attestation + NACES/AICE report)
• Exhibit C — Recommendation letters
• Exhibit D — Publications, patents, GitHub evidence
• Exhibit E — Wage and comparable-salary evidence

Keep exhibit letters stable across drafts so citations in the cover letter and endeavor statement don't drift.

Evidence index table

Place this immediately after the cover letter, before Exhibit A.

Paginate the entire packet sequentially and cross-check every page number in the index against the final assembled PDF before submission.

Common RFE triggers for this profile and how to preempt them

Before filing, reread the endeavor statement and every letter as if encountering the petitioner for the first time — flag any sentence that could apply to a different candidate.