Apple · Motivation & Culture Fit

Clarify status, education, and multi-role strategy

TrueInterview

October 7, 2026 · 9 min read

Where do you stand on U.S. employment and visa status, and what work authorization do you currently hold? Name the precise status (for example, F-1 OPT, STEM OPT, H-1B cap-subject or cap-exempt, EAD, green card, citizen), its expiration dates, any portability limits, and any constraints on your start date; outline what you would do if the start had to move up by 30 days. 2) What is the highest degree you have completed, which school awarded it, and in what month and year? Your resume seems to place your undergraduate major on the master's line — walk through why that happened, what the accurate entries are, and how you would fix it across your ATS profiles, LinkedIn, and every resume version. 3) You submitted applications at the same time for Manager, Senior Manager, and Senior Business Analyst within one job family. With a common scoring rubric and leveling decided after interviews, how do you shape your impact stories differently at each level (scope, decision rights, team size, dollar impact)? State the lowest level you would accept if your performance lands borderline, and how you will keep the requisitions from conflicting with one another. 4) Give three 60-minute slots this month when you could sit a minicase (include your time zone), how much preparation time you need, and how you would get ready within 48 hours (materials, frameworks, the data you would ask for).

Overview: This prompt measures how well a candidate can record and explain U.S. work authorization details, correct inconsistencies in a resume, position themselves across several role levels, and show minicase availability and preparation — in short, attention to detail, clear communication, coordination with stakeholders, and real readiness for data-science interviews. It appears often in Behavioral & Leadership screens for Data Scientist openings, where it checks eligibility, fit with the level being hired, and logistical readiness; it probes both the conceptual side of career leveling and contingency planning and the practical side of documentation, messaging, and time management.

Solution

How to Respond Well (templates and examples included)

This HR screen calls for exact, checkable facts and a straightforward plan. Keep statements short and unambiguous, put dates in, and show you are ready. Templates, examples, and guardrails follow.

1) U.S. Work Authorization

Approach: Give the status, the dates, portability, constraints, and a plan for pulling the start forward 30 days. Don't draw legal conclusions — stay with facts and supply supporting documents on request (I-20/DS-2019, EAD card, H-1B receipt or approval, I-94). Template:

Current status: [for example, F-1 STEM OPT, valid to 2027-06-30].
Employer authorization: [tied to one employer, or open via EAD].
Key dates: [EAD or I-797 validity], [I-94 expiry], [any grace periods].
Portability: [for example, H-1B portability under AC21; cap-exempt versus cap-subject].
Start-date constraints: [earliest date you can begin].
30-day pull-in plan: [what has to change if the start moves up 30 days]. Typical statuses and the points to record:
F-1 OPT / STEM OPT: EAD end date, unemployment days still available, STEM eligibility, and cap-gap if an H-1B has been filed.
H-1B cap-subject or cap-exempt: I-797 validity (from–to), portability (whether you may start on receipt or only on approval, per employer policy), and that the LCA is filed.
EAD (for example, AOS or TPS): category code (C09, A12, and so on), end date, and any automatic extension that applies.
Green card or citizen: no restrictions; give your available start date. Example (STEM OPT):
Current status: F-1 STEM OPT, EAD running 2025-07-01 through 2027-06-30.
Employer authorization: tied to one employer; I-983 and E-Verify are in place.
Key dates: I-94 shows D/S; 150 STEM unemployment days left in total; cap-gap does not apply yet.
Portability: cannot move to another employer without a new I-983, and the new employer must be enrolled in E-Verify.
Start-date constraints: can begin 2025-11-18; two weeks are needed for onboarding and SEVIS updates.
30-day pull-in plan: could start as early as 2025-10-20 by rushing the I-983, filing the SEVIS update within 10 days, and overlapping the current notice period with PTO (my manager is aware). No move is 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, though portability under AC21 applies; under policy a new start is possible once the new employer's H-1B filing is received.
Key dates: I-94 matches the H-1B validity; the passport runs to 2030-05.
Portability: able to start on receipt, and fine with waiting for approval if that is preferred.
Start-date constraints: available four weeks after accepting the offer.
30-day pull-in plan: start two weeks after acceptance if the portability filing is prioritized and the current notice period is shortened with PTO. Guardrail: immigration questions turn on individual facts — check with counsel. Hand over documents when asked.

2) Education and Resume Consistency

Goal: name your highest completed degree and correct the master's/undergraduate major mix-up everywhere it appears. Template:

Highest degree: [degree], [institution], [month year].
Correction: my resume wrongly put my undergraduate major on the master's line. The right entries are:
- Master's: [degree name], [field], [institution], [month year].
- Bachelor's: [degree name], [field], [institution], [month year].
Remediation plan: I will correct every material today — resume (PDF/DOC), the LinkedIn Education section, and ATS profiles — so that titles, fields, and dates match exactly. The change will be noted in the file name (for example, Resume_2025-11-01.pdf), and I will send the corrected copy. Example:
Highest degree: M.S. in Data Science, University of X, May 2023.
Correction: the M.S. line wrongly showed "B.S., Applied Mathematics" as the field. Accurate entries:
- Master's: M.S., Data Science — University of X — May 2023.
- Bachelor's: B.S., Applied Mathematics — University of Y — May 2021.
Remediation: fix the resume, LinkedIn, and ATS today; make sure the Education section lists each degree on its own line with the right field and date; re-export the PDF; share the updated copy. Mistakes to steer clear of:
Blurring degree name and major between the two degrees.
Month/year that differs from one platform to the next.
Leaving out a thesis or concentration that would make the graduate focus clear.

3) Tailoring Across Levels (Senior Business Analyst, Manager, Senior Manager)

Principle: hold one factual base (metrics, numbers) and then adjust scope, decision rights, team leadership, and dollar impact to the level. What each level means:

Senior Business Analyst (individual contributor): runs deep analysis, shapes the roadmap, has no direct reports, and frames impact as product KPI movement and dollars delivered through experiments.
Manager: runs a small team (3–6), sets the roadmap, makes cross-functional calls, and answers for delivery and stakeholder alignment.
Senior Manager: leads several teams or a program, sets strategy, holds the portfolio P&L levers, and pushes change at the org level. A single story told at three scales (example: a churn-reduction effort):
Core facts (identical in every version): cohort churn was 22%. I built a survival model, targeted save-offers off it, and an A/B test showed −2.5 pp churn (95% CI: −1.8 to −3.2). ARR base was $60M, and the uplift came to roughly $6.8M in ARR net of COGS. How the framing changes:
Senior Business Analyst:
- Scope: designed and built the survival model and the targeting logic, wrote the SQL/Python, and worked alongside the PM.
- Decision rights: recommended the thresholds and persuaded the PM to run the A/B test.
- Team size: individual contributor who mentored one analyst.
- Dollar impact: put the ARR figure and its confidence interval on the table, and go into the experiment design and QA.
Manager:
- Scope: led a four-person team (2 data scientists, 1 data engineer, 1 analyst) and owned the problem framing and roadmap.
- Decision rights: approved the model deployment, decided how engineering time was spent, and set the guardrail metrics.
- Dollar impact: the portfolio view ($6.8M ARR) plus $400k in operating savings from automated retention work.
Senior Manager:
- Scope: a multi-pod program spanning two product areas (lifecycle and pricing), with legal and finance aligned and rollout to three markets.
- Decision rights: set the annual retention strategy, rebalanced the budget, and negotiated trade-offs with the GMs.
- Dollar impact: $12–15M in total annualized impact across the portfolio, with playbooks written down and monthly governance put in place. Lowest level you would accept (settle it once and give the reasoning):
Template: if the leveling call is borderline, the lowest level I will accept is [Senior Business Analyst | Manager]. Rationale: [for example, scope fit, leadership trajectory, compensation band].
Example stance: minimum acceptable is Manager. I have repeatedly led teams of 3–5 and owned cross-functional decisions, and I am looking for formal people leadership and roadmap accountability. Keeping the requisitions from colliding:
One source of truth: maintain a calibration sheet holding metric definitions, sample sizes, dates, and dollar impact.
Change the emphasis, not the numbers: the figures stay the same while the framing shifts (individual craft versus team leadership versus portfolio strategy).
Coordination: ask recruiting to route everything through one recruiter of record and to note that you applied at several levels in the same family. Step out of duplicate requisitions if they ask.
Document control: keep a single resume version, tune the summary at the top to the level, and never pad a title.

4) Minicase Availability and 48-Hour Prep Plan

Give firm windows in your own 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 Prep time needed:
3–4 hours in total, spread over two days. Two hours will do if that is all there is. 48-hour prep plan (Data Scientist minicase):
Day −2 (2 hours):
- Get the product context clear: the funnel, the primary KPIs (DAU/MAU, activation, retention, revenue), and the north-star metric.
- Frameworks: CRISP-DM for the flow, a hypothesis tree for the drivers, ICE for prioritization.
- Refresh the methods: experiment design, uplift modeling, segmentation, causal DAGs, plus the basics of sample size and power.
- Dry run: one practice case and a ten-slide outline (problem, metric, plan, risks, trade-offs).
Day −1 (1–1.5 hours):
- Build a structure you can reuse: problem statement, success metric, data plan, methodology, risks, decision.
- Draft two STAR stories that fit the role: 1) a product-growth A/B test, 2) cost reduction through automation.
- Prepare the sanity-check math for dollar impact: for example, if MAU is 5M, ARPU is $3 per month, and retention moves up 1 pp, the monthly uplift is about $1.8M.
Morning of (30 minutes):
- Formulas to have at hand:
  - Sample size (difference in proportions, two-sided):

$n \approx \frac{2\left(z_{1-\alpha/2} + z_{\text{power}}\right)^2 p(1-p)}{\Delta^2}$

- Lift converted to dollars:

$\Delta \text{KPI} \times \text{base} \times \text{monetization rate}$

Checklist: make the assumptions explicit, ask for the guardrail metrics, and state the risks and next steps. Data I would ask for (if that is permitted):
Event schema: user_id, timestamp, event_name, product area; the primary keys; the sessionization rules.
Core tables: users (cohorts, locale), events (clicks, conversions), revenue/subscriptions, experiments.
Metric definitions: how DAU/MAU are computed, how activation and retention are defined, and the attribution windows.
Constraints: data freshness, sampling, PII handling, tool access (SQL/Python), and the timebox. The structure I will follow in the interview:
Clarify the objective and the decision criteria, and agree on the success metric and guardrails (for example, no drop in NPS greater than 1 pp).
Baseline: where the KPIs sit today and how much they vary, plus a quick back-of-the-envelope impact model.
Plan: the analysis path (EDA → hypothesis → experiment or model), the data needed, and the timelines.
Risks and assumptions: bias, seasonality, gaps in logging, power — and how each would be mitigated.
Decision: what I would recommend right now, what I would need before recommending confidently, and the next steps. Last polish points:
Be exact with dates and numbers; skip ranges unless you also give the precise midpoint.
Keep one resume version and tailor the pitch rather than the facts.
Offer documents up front (updated resume, degree proof, status paperwork) and confirm your availability windows in the recruiter's time zone.

1) U.S. Work Authorization

Current status: [for example, F-1 STEM OPT, valid to 2027-06-30].

Employer authorization: [tied to one employer, or open via EAD].

Key dates: [EAD or I-797 validity], [I-94 expiry], [any grace periods].

Portability: [for example, H-1B portability under AC21; cap-exempt versus cap-subject].

Start-date constraints: [earliest date you can begin].

30-day pull-in plan: [what has to change if the start moves up 30 days]. Typical statuses and the points to record:

F-1 OPT / STEM OPT: EAD end date, unemployment days still available, STEM eligibility, and cap-gap if an H-1B has been filed.

H-1B cap-subject or cap-exempt: I-797 validity (from–to), portability (whether you may start on receipt or only on approval, per employer policy), and that the LCA is filed.

EAD (for example, AOS or TPS): category code (C09, A12, and so on), end date, and any automatic extension that applies.

Green card or citizen: no restrictions; give your available start date. Example (STEM OPT):

Current status: F-1 STEM OPT, EAD running 2025-07-01 through 2027-06-30.

Employer authorization: tied to one employer; I-983 and E-Verify are in place.

Key dates: I-94 shows D/S; 150 STEM unemployment days left in total; cap-gap does not apply yet.

Portability: cannot move to another employer without a new I-983, and the new employer must be enrolled in E-Verify.

Start-date constraints: can begin 2025-11-18; two weeks are needed for onboarding and SEVIS updates.

30-day pull-in plan: could start as early as 2025-10-20 by rushing the I-983, filing the SEVIS update within 10 days, and overlapping the current notice period with PTO (my manager is aware). No move is 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, though portability under AC21 applies; under policy a new start is possible once the new employer's H-1B filing is received.

Key dates: I-94 matches the H-1B validity; the passport runs to 2030-05.

Portability: able to start on receipt, and fine with waiting for approval if that is preferred.

Start-date constraints: available four weeks after accepting the offer.

30-day pull-in plan: start two weeks after acceptance if the portability filing is prioritized and the current notice period is shortened with PTO. Guardrail: immigration questions turn on individual facts — check with counsel. Hand over documents when asked.

2) Education and Resume Consistency

Goal: name your highest completed degree and correct the master's/undergraduate major mix-up everywhere it appears. Template:

Highest degree: [degree], [institution], [month year].

Correction: my resume wrongly put my undergraduate major on the master's line. The right entries are:

Master's: [degree name], [field], [institution], [month year].
Bachelor's: [degree name], [field], [institution], [month year].

Remediation plan: I will correct every material today — resume (PDF/DOC), the LinkedIn Education section, and ATS profiles — so that titles, fields, and dates match exactly. The change will be noted in the file name (for example, Resume_2025-11-01.pdf), and I will send the corrected copy. Example:

Highest degree: M.S. in Data Science, University of X, May 2023.

Correction: the M.S. line wrongly showed "B.S., Applied Mathematics" as the field. Accurate entries:

Master's: M.S., Data Science — University of X — May 2023.
Bachelor's: B.S., Applied Mathematics — University of Y — May 2021.

Remediation: fix the resume, LinkedIn, and ATS today; make sure the Education section lists each degree on its own line with the right field and date; re-export the PDF; share the updated copy. Mistakes to steer clear of:

Blurring degree name and major between the two degrees.

Month/year that differs from one platform to the next.

Leaving out a thesis or concentration that would make the graduate focus clear.

3) Tailoring Across Levels (Senior Business Analyst, Manager, Senior Manager)

Principle: hold one factual base (metrics, numbers) and then adjust scope, decision rights, team leadership, and dollar impact to the level. What each level means:

Senior Business Analyst (individual contributor): runs deep analysis, shapes the roadmap, has no direct reports, and frames impact as product KPI movement and dollars delivered through experiments.

Manager: runs a small team (3–6), sets the roadmap, makes cross-functional calls, and answers for delivery and stakeholder alignment.

Senior Manager: leads several teams or a program, sets strategy, holds the portfolio P&L levers, and pushes change at the org level. A single story told at three scales (example: a churn-reduction effort):

Core facts (identical in every version): cohort churn was 22%. I built a survival model, targeted save-offers off it, and an A/B test showed −2.5 pp churn (95% CI: −1.8 to −3.2). ARR base was $60M, and the uplift came to roughly $6.8M in ARR net of COGS. How the framing changes:

Senior Business Analyst:

Scope: designed and built the survival model and the targeting logic, wrote the SQL/Python, and worked alongside the PM.
Decision rights: recommended the thresholds and persuaded the PM to run the A/B test.
Team size: individual contributor who mentored one analyst.
Dollar impact: put the ARR figure and its confidence interval on the table, and go into the experiment design and QA.

Manager:

Scope: led a four-person team (2 data scientists, 1 data engineer, 1 analyst) and owned the problem framing and roadmap.
Decision rights: approved the model deployment, decided how engineering time was spent, and set the guardrail metrics.
Dollar impact: the portfolio view ($6.8M ARR) plus $400k in operating savings from automated retention work.

Senior Manager:

Scope: a multi-pod program spanning two product areas (lifecycle and pricing), with legal and finance aligned and rollout to three markets.
Decision rights: set the annual retention strategy, rebalanced the budget, and negotiated trade-offs with the GMs.
Dollar impact: $12–15M in total annualized impact across the portfolio, with playbooks written down and monthly governance put in place. Lowest level you would accept (settle it once and give the reasoning):

Template: if the leveling call is borderline, the lowest level I will accept is [Senior Business Analyst | Manager]. Rationale: [for example, scope fit, leadership trajectory, compensation band].

Example stance: minimum acceptable is Manager. I have repeatedly led teams of 3–5 and owned cross-functional decisions, and I am looking for formal people leadership and roadmap accountability. Keeping the requisitions from colliding:

One source of truth: maintain a calibration sheet holding metric definitions, sample sizes, dates, and dollar impact.

Change the emphasis, not the numbers: the figures stay the same while the framing shifts (individual craft versus team leadership versus portfolio strategy).

Coordination: ask recruiting to route everything through one recruiter of record and to note that you applied at several levels in the same family. Step out of duplicate requisitions if they ask.

Document control: keep a single resume version, tune the summary at the top to the level, and never pad a title.

4) Minicase Availability and 48-Hour Prep Plan

Give firm windows in your own 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 Prep time needed:

3–4 hours in total, spread over two days. Two hours will do if that is all there is. 48-hour prep plan (Data Scientist minicase):

Day −2 (2 hours):

Get the product context clear: the funnel, the primary KPIs (DAU/MAU, activation, retention, revenue), and the north-star metric.
Frameworks: CRISP-DM for the flow, a hypothesis tree for the drivers, ICE for prioritization.
Refresh the methods: experiment design, uplift modeling, segmentation, causal DAGs, plus the basics of sample size and power.
Dry run: one practice case and a ten-slide outline (problem, metric, plan, risks, trade-offs).

Day −1 (1–1.5 hours):

Build a structure you can reuse: problem statement, success metric, data plan, methodology, risks, decision.
Draft two STAR stories that fit the role: 1) a product-growth A/B test, 2) cost reduction through automation.
Prepare the sanity-check math for dollar impact: for example, if MAU is 5M, ARPU is $3 per month, and retention moves up 1 pp, the monthly uplift is about $1.8M.

Morning of (30 minutes):

Formulas to have at hand:
- Sample size (difference in proportions, two-sided):

n \approx \frac{2\left(z_{1-\alpha/2} + z_{\text{power}}\right)^2 p(1-p)}{\Delta^2}

- Lift converted to dollars:

\Delta \text{KPI} \times \text{base} \times \text{monetization rate}

Checklist: make the assumptions explicit, ask for the guardrail metrics, and state the risks and next steps. Data I would ask for (if that is permitted):

Event schema: user_id, timestamp, event_name, product area; the primary keys; the sessionization rules.

Core tables: users (cohorts, locale), events (clicks, conversions), revenue/subscriptions, experiments.

Metric definitions: how DAU/MAU are computed, how activation and retention are defined, and the attribution windows.

Constraints: data freshness, sampling, PII handling, tool access (SQL/Python), and the timebox. The structure I will follow in the interview:

Clarify the objective and the decision criteria, and agree on the success metric and guardrails (for example, no drop in NPS greater than 1 pp).

Baseline: where the KPIs sit today and how much they vary, plus a quick back-of-the-envelope impact model.

Plan: the analysis path (EDA → hypothesis → experiment or model), the data needed, and the timelines.

Risks and assumptions: bias, seasonality, gaps in logging, power — and how each would be mitigated.

Decision: what I would recommend right now, what I would need before recommending confidently, and the next steps. Last polish points:

Be exact with dates and numbers; skip ranges unless you also give the precise midpoint.

Keep one resume version and tailor the pitch rather than the facts.

Offer documents up front (updated resume, degree proof, status paperwork) and confirm your availability windows in the recruiter's time zone.