1) What is your current employment/visa status and work authorization in the U.S.? Specify the exact status (e.g., F-1 OPT, STEM OPT, H‑1B cap-subject/cap-exempt, EAD, GC, citizen), expiration dates, portability limits, and any start-date constraints; describe your contingency plan if a start must move up by 30 days. 2) What is your highest completed degree, which institution granted it, and the month/year awarded? Your resume appears to list your undergraduate major under your master’s entry—explain the discrepancy, what the correct entries should be, and how you would rectify it across ATS/LinkedIn/resume versions. 3) You applied simultaneously to Manager, Senior Manager, and Senior Business Analyst in the same job family. Given a shared scoring rubric with post-interview leveling, how will you tailor impact narratives for each level (scope, decision rights, team size, $ impact)? Specify your minimum acceptable level if performance is borderline and how you will avoid conflicts across requisitions. 4) Provide three 60‑minute windows you can attend a minicase this month (include time zone), your required prep time, and how you’d prepare in 48 hours (materials, frameworks, data you’d request).
Quick Answer: This question evaluates a candidate's ability to document and communicate U.S. work authorization details, resolve resume inconsistencies, articulate multi-level role positioning, and demonstrate minicase availability and preparation—assessing attention to detail, clarity of communication, stakeholder coordination, and practical readiness for data-science interviews. Commonly asked in Behavioral & Leadership screens for Data Scientist roles to verify eligibility, alignment with role expectations, and logistical readiness, it tests both conceptual understanding of career-leveling and contingency planning and practical application of documentation, messaging, and time-management.
Solution
# How to Answer Effectively (with templates and examples)
This HR screen asks for precise, verifiable facts and a clear plan. Use short, unambiguous statements, include dates, and demonstrate readiness. Below are templates, examples, and guardrails.
## 1) U.S. Work Authorization
Approach: Provide status, dates, portability, constraints, and a 30‑day acceleration plan. Avoid legal conclusions; stick to facts and attach supporting docs if asked (I‑20/DS‑2019, EAD card, H‑1B receipt/approval, I‑94).
Template:
- Current status: [e.g., F‑1 STEM OPT (valid through 2027‑06‑30)].
- Employer authorization: [Employer‑specific or open (EAD)].
- Key dates: [EAD/I‑797 validity], [I‑94 expiration], [grace periods].
- Portability: [e.g., H‑1B portability under AC21; cap‑exempt vs cap‑subject].
- Start‑date constraints: [earliest available date].
- 30‑day pull‑in plan: [what changes if start must move up 30 days].
Common statuses and what to note:
- F‑1 OPT/STEM OPT: EAD end date, remaining unemployment days, STEM eligibility, cap‑gap if H‑1B filed.
- H‑1B cap‑subject/cap‑exempt: I‑797 validity (from–to), portability (start upon receipt vs approval, per employer policy), LCA filed.
- EAD (e.g., AOS, TPS): Category code (C09, A12, etc.), end date, automatic extensions if applicable.
- Green card/citizen: No restrictions; available start date.
Example (STEM OPT):
- Current status: F‑1 STEM OPT (EAD valid 2025‑07‑01 to 2027‑06‑30).
- Employer authorization: Employer‑specific; I‑983 and E‑Verify in place.
- Key dates: I‑94 D/S; 150 STEM unemployment days remaining across total; Cap‑gap not applicable yet.
- Portability: Not portable between employers without new I‑983; new employer must be E‑Verify.
- Start‑date constraints: Available to start 2025‑11‑18; need 2 weeks for onboarding and SEVIS updates.
- 30‑day pull‑in plan: Can start as early as 2025‑10‑20 by expediting I‑983, SEVIS update within 10 days, and overlapping current notice period with PTO (manager informed). No relocation required.
Example (H‑1B, cap‑subject):
- Current status: H‑1B cap‑subject; I‑797 valid 2024‑10‑01 to 2027‑09‑30.
- Employer authorization: Employer‑specific, but eligible for portability (AC21). New start possible upon receipt of new employer’s H‑1B filing per policy.
- Key dates: I‑94 matches H‑1B validity; passport valid through 2030‑05.
- Portability: Can start upon receipt; comfortable starting after approval if preferred.
- Start‑date constraints: Available 4 weeks from offer acceptance.
- 30‑day pull‑in plan: Start 2 weeks from acceptance if portability filing is prioritized and current employer notice period reduced using PTO.
Guardrail: Immigration is fact‑specific; confirm with counsel. Provide documents upon request.
## 2) Education and Resume Consistency
Goal: State your highest completed degree and fix the master’s/undergraduate major mismatch everywhere.
Template:
- Highest degree: [Degree], [Institution], [Month Year].
- Correction: My resume mistakenly listed my undergraduate major under my master’s entry. Correct entries are:
- Master’s: [Degree Name], [Field], [Institution], [Month Year].
- Bachelor’s: [Degree Name], [Field], [Institution], [Month Year].
- Remediation plan: I will update all materials today—resume (PDF/DOC), LinkedIn (Education), and ATS profiles—to ensure identical titles, fields, and dates. I will annotate the change log in file name (e.g., Resume_2025‑11‑01.pdf) and send the corrected version.
Example:
- Highest degree: M.S., Data Science, University of X, May 2023.
- Correction: The M.S. entry incorrectly showed “B.S., Applied Mathematics” as the major. Correct entries:
- Master’s: M.S., Data Science — University of X — May 2023.
- Bachelor’s: B.S., Applied Mathematics — University of Y — May 2021.
- Remediation: Update resume/LinkedIn/ATS today; ensure the Education section shows each degree on separate lines with correct field and date; re‑export PDF; share updated copy.
Pitfalls to avoid:
- Mixing degree name and major across degrees.
- Inconsistent month/year across platforms.
- Omitting thesis or concentration that clarifies the graduate focus.
## 3) Tailoring Across Levels (Senior Business Analyst, Manager, Senior Manager)
Principle: Keep one truth base (metrics, numbers), then tailor scope, decision rights, team leadership, and dollar impact for each level.
Define the levels:
- Senior Business Analyst (IC): Owns deep analysis; influences roadmap; no direct reports; impact framed as product KPI lift and $ via experiments.
- Manager: Leads a small team (3–6), sets roadmap, owns cross‑functional decisions, accountable for delivery and stakeholder alignment.
- Senior Manager: Leads multiple teams or a program; sets strategy; owns portfolio P&L levers; drives org‑level change.
One story, scaled three ways (example: churn reduction initiative):
- Core facts (same for all): Cohort churn = 22%. Built survival model; targeted save‑offers; A/B test showed −2.5 pp churn (95% CI: −1.8 to −3.2). ARR base = $60M; uplift ≈ $6.8M ARR net of COGS.
Tailoring:
- Senior Business Analyst:
- Scope: Designed and implemented survival model and targeting; wrote SQL/Python; partnered with PM.
- Decision rights: Recommended thresholds; influenced PM to run A/B.
- Team size: IC with mentorship of 1 analyst.
- $ impact: Quantify ARR and confidence; detail experiment design and QA.
- Manager:
- Scope: Led 4‑person team (2 DS, 1 DE, 1 analyst); owned problem framing and roadmap.
- Decision rights: Approved model deployment, allocation of engineering time, and guardrail metrics.
- $ impact: Portfolio view ($6.8M ARR), plus ops savings ($400k) from automated retention ops.
- Senior Manager:
- Scope: Multi‑pod program (two product areas, lifecycle + pricing); aligned legal/finance; scaled to 3 markets.
- Decision rights: Set annual retention strategy; rebalanced budget; negotiated trade‑offs with GMs.
- $ impact: Total annualized impact $12–15M across portfolio; codified playbooks; instituted monthly governance.
Minimum acceptable level (decide once and state rationale):
- Template: If leveling is borderline, my minimum acceptable level is [Senior Business Analyst | Manager]. Rationale: [e.g., scope fit, leadership trajectory, compensation band].
- Example stance: Minimum acceptable: Manager. I’ve consistently led teams of 3–5 and owned cross‑functional decisions; I’m seeking formal people leadership and roadmap accountability.
Avoiding cross‑requisition conflicts:
- Single source of truth: Keep a calibration sheet with metric definitions, Ns, dates, $ impact.
- Tailored emphasis, not numbers: Keep numbers identical; change framing (IC craft vs team leadership vs portfolio strategy).
- Coordination: Ask recruiting to consolidate under one recruiter of record and note that you applied to multiple levels in the same family. Withdraw from duplicative reqs if requested.
- Document control: Use one resume version; adjust cover summary to the level; do not inflate titles.
## 4) Minicase Availability and 48‑Hour Prep Plan
Provide concrete windows in your time zone. Example (Pacific Time, November 2025):
- Tue Nov 4, 2025: 1:00–2:00 PM PT
- Thu Nov 6, 2025: 9:00–10:00 AM PT
- Mon Nov 10, 2025: 4:00–5:00 PM PT
Required prep time:
- 3–4 hours total (spread across two days). I can proceed with 2 hours if needed.
48‑hour prep plan (Data Scientist minicase):
- Day −2 (2 hours):
- Clarify product context: Funnel, primary KPIs (DAU/MAU, activation, retention, revenue), north‑star metric.
- Frameworks: CRISP‑DM for flow; hypothesis tree for drivers; ICE for prioritization.
- Methods refresh: Experiment design, uplift modeling, segmentation, causal DAGs; sample size/power basics.
- Dry run: 1 practice case; 10‑slide outline (problem, metric, plan, risks, trade‑offs).
- Day −1 (1–1.5 hours):
- Build a reusable structure: Problem statement, success metric, data plan, methodology, risks, decision.
- Draft two STAR stories aligned to role: 1) Product growth A/B, 2) Cost reduction via automation.
- Prepare sanity‑check math for $ impact: e.g., If MAU=5M, ARPU=$3/mo, +1 pp retention → ≈$1.8M/mo uplift.
- Morning‑of (30 minutes):
- Quick formulas:
- Sample size (difference in proportions, two‑sided): n ≈ 2*(z_{1−α/2}+z_{power})^2 * p(1−p) / Δ^2
- Lift to $: ΔKPI × base × monetization rate
- Checklist: Clarify assumptions; ask for guardrail metrics; communicate risks and next steps.
Data I’d request (if allowed):
- Event schema: user_id, timestamp, event_name, product area; primary keys; sessionization rules.
- Core tables: users (cohorts, locale), events (clicks, conversions), revenue/subscriptions, experiments.
- Metric definitions: How DAU/MAU are computed; activation and retention definitions; attribution windows.
- Constraints: Data freshness, sampling, PII handling, tool access (SQL/Python), timebox.
Case structure I’ll follow in interview:
- Clarify objective and decision criteria; align on success metric and guardrails (e.g., no −NPS > 1 pp).
- Baseline: Current KPI levels and variance; quick back‑of‑envelope impact model.
- Plan: Analysis path (EDA → hypothesis → experiment/model), data needs, timelines.
- Risks/assumptions: Bias, seasonality, logging gaps, power; mitigations.
- Decision: What I’d recommend now; what I need to recommend confidently; next steps.
Final polish tips:
- Be specific with dates and numbers; avoid ranges unless you share the exact midpoint.
- Keep one resume version; tailor the pitch, not the facts.
- Proactively offer documents (updated resume, degree proof, status docs) and confirm availability windows in the recruiter’s time zone.