Quick summary
Summarize this blog with AI
A data science career can develop through deeper technical work, broader project leadership, people management, or a move into an adjacent specialty. There is no universal sequence of titles, salary bands, or years of experience. Read a company’s level expectations and actual responsibilities before treating a title as equivalent to one elsewhere.
Compare scope rather than a fixed ladder
The table describes illustrative scopes, not a standardized industry framework. A company may combine them, name them differently, or have fewer levels.
| Scope | Example responsibility | Evidence to discuss |
|---|---|---|
| Supported individual work | Complete a defined analysis with review. | Correct results, clear assumptions, and use of feedback. |
| Independent project ownership | Turn an ambiguous request into an analysis or model and deliver it. | Problem definition, validation, tradeoffs, and a usable outcome. |
| Broader technical influence | Improve methods or decisions across several projects or teams. | Adoption, review quality, and evidence that the work helped others. |
| People management | Support a team’s performance, staffing, priorities, and development. | Clear expectations, coaching, fair feedback, and reliable delivery through others. |
These scopes can overlap. A senior individual contributor may mentor people without managing them. A manager may retain technical depth while spending less time implementing models. A “lead” title does not tell you whether it includes direct reports; ask.
Choose the work you want to practice
For a technical path, look for opportunities to solve harder problems, improve shared methods, review important work, and help others make better decisions. For management, explore whether you want recurring responsibility for hiring, feedback, prioritization, and resolving team constraints. Management is a different set of responsibilities, not a mandatory reward for technical competence.
A move into analytics engineering, data engineering, applied research, or product work may also fit your strengths. Compare the tasks and required evidence instead of assuming that every change must move “up” a single hierarchy.
Build a record of contribution and judgment
For each significant project, record the original problem, your contribution, a difficult decision, the validation performed, and the outcome you can substantiate. Include collaboration and maintenance work when they mattered. Keep confidential details out of public portfolios.
A useful record might say: “Identified duplicate events that inflated a product metric, agreed on a deduplication rule with engineering, and added a check to the reporting pipeline.” If you measured a downstream impact, document how. If you did not, describe the improved artifact or decision without inventing a revenue figure.
Agree on the next scope with your manager
Ask for the written expectations of your current and proposed level. Choose one or two gaps that can be demonstrated in normal work, then agree on a project, support, feedback checkpoints, and what evidence would show progress. Confirm who participates in promotion decisions and what the process can and cannot promise.
For example, moving from executing requests to independent ownership might involve defining a metric, aligning stakeholders on the question, delivering the analysis, and documenting follow-up. Success should be assessed against agreed expectations rather than the number of tools you learned or hours you worked.
Evaluate an external move on its own terms
Ask the hiring manager about decision authority, project complexity, review expectations, and team support. A larger title with narrower work may not provide the growth you want. A different title with clear ownership may be a useful step. Discuss actual compensation documents separately; this guide does not provide unsourced salary ranges or fixed experience thresholds.
Revisit your direction as you learn what work energizes you and where you are effective. A deliberate lateral move or a return from management to individual contribution can be a valid choice. Career progress is better described by fit, capability, and responsibility than by a universal list of titles.
