Discuss salary expectations
Company: Samsara
Role: Machine Learning Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Onsite
What are your salary expectations for this role? Given that compensation is base salary only, what range are you targeting and how did you determine it? Are you open to discussing bonus or benefits trade-offs?
Quick Answer: This question evaluates a candidate's ability to communicate compensation expectations, justify a targeted base salary through market benchmarking and assumptions, and articulate openness to trade-offs for a Machine Learning Engineer role.
Solution
# How to Answer Compensation Expectation Questions (Base‑Only)
Goal: Provide a confident base salary range backed by market data, clarify your rationale, and signal thoughtful flexibility on non‑base levers.
## 1) Confirm role scope before naming numbers
- Clarify level and location, since these drive market rate.
- Script: "Before I share numbers, could you confirm the level and location for this role, and the budgeted base range? I want to stay aligned with your band."
If they share their band, anchor within or slightly above its midpoint (for strong fit), then justify.
## 2) Determine your market range (quick method)
- Sources: Levels.fyi, H1B Salary Database, Glassdoor, Payscale, peer conversations, recruiter ranges.
- Collect 5–10 data points for your level and location. Remove clear outliers.
- Compute a midpoint (median of the cleaned set). For base‑only packages, add a 5–15% premium because there’s no annual bonus or equity.
- Adjusted midpoint ≈ market median × (1.05 to 1.15)
- Build a range around that midpoint:
- Typical range width: ±10% of midpoint (avoid ranges wider than ~20%).
Note: As of 2024, typical U.S. base bands (very rough, level‑dependent):
- Major hubs (SF/NY/Seattle): ~180k–260k for mid‑to‑senior MLE roles.
- Secondary hubs (Austin/Boston/Atlanta): ~160k–220k.
- Other markets: ~140k–200k.
Adjust to your level and evidence.
## 3) Define your three numbers
- Minimum (walk‑away): The lowest base you’d accept, given base‑only.
- Target: What you believe is fair market for your impact.
- Anchor: The top of your range (ambitious but defensible, backed by data).
Example (Bay Area, mid‑senior MLE):
- Market median comps: ~$200k base.
- Base‑only premium (10%): $220k midpoint.
- Range: $210k–$235k. Minimum: $205k. Anchor: $235k.
## 4) Ready‑to‑use scripts
A) Direct answer with rationale
- "Based on the role scope, my experience deploying production ML systems, and current market data (Levels.fyi, H1B), for a base‑only package I’m targeting $210k–$235k. That reflects a modest premium for base‑only structures. I’m confident I can contribute at that level and I’m open to discussing details to make the fit right."
B) If you prefer they share the band first
- "I’m aligned to market for this level and location. Could you share the budgeted base range? If it’s helpful, my recent research for base‑only packages suggests a range around low‑200s to mid‑200s for this scope, and I’m comfortable within that depending on level and impact."
C) Openness to trade‑offs (even if plan is base‑only)
- "Base is my priority in a base‑only plan, so I’d target $210k–$235k. If there’s flexibility to add a sign‑on or a small performance bonus, I could be more flexible on base. For example, a 10% bonus or a meaningful sign‑on could justify considering the lower end of that range."
## 5) Trade‑off calculus you can cite
- Bonus: 1% target bonus ≈ 1% of base value annually. A 10% bonus on a $220k base ≈ $22k/year.
- Sign‑on: Amortize over 2–3 years when comparing to base. A $20k sign‑on over 3 years ≈ ~$6.7k/year.
- 401(k) match: A 4% match ≈ 4% of base value annually.
- Extra PTO: 5 additional days ≈ ~2% of annual workdays (assumes ~250 workdays), rough value ~2% of base if fully utilized.
Use these to explain why base should be higher if no bonus/equity exists, and how you’d flex if such levers are added.
## 6) Pitfalls to avoid
- Don’t share current salary. Focus on market and impact.
- Don’t give a too‑wide range (>20%) or an overly narrow one (<5%).
- Don’t ignore location/level specifics. Confirm them first.
- Get any non‑standard elements (sign‑on, review cycle) in writing.
## 7) Compact template you can reuse
- "Given a [level, location] MLE role and a base‑only structure, my research (Levels.fyi, H1B, recruiter ranges) supports a base range of [$X–$Y]. I derived this by starting from the local market median and adding a modest premium for base‑only. Base is my priority, though I’m open to discussing a sign‑on or modest bonus if that helps us align on total value."
Use this structure to answer crisply, show you’ve done your homework, and keep the door open for a collaborative close.