Exploring Careers in Data Science, Data Analysis & Business Analysis

The Spaces brought together practitioners to demystify data analysis, data science, and business analysis, outlining what each role does, required skills, and realistic career paths. Olani traced a non‑linear move from construction to data, clarifying: data analysts explain what happened and why, business analysts define problems and improve processes, and data scientists predict and optimize. He detailed a data scientist’s day: querying databases, building models in Python, and projecting outcomes. Esther, a statistics‑trained analyst in audience engagement, showed how data underpins content strategy, stressed that cleaning can consume 80% of effort, and urged beginners to learn Excel, SQL, and Power BI rather than fixate on a single tool. She mapped niche analyst roles and warned against FOMO and “certificate collecting,” advocating building in public. Victor explained BA as people‑centric problem solving powered by data, differentiating BA from PM and DA, and emphasizing stakeholder communication, negotiation, and process optimization. Joshua shared his transition from microbiology to data entry, DA, and BA, highlighting transferable skills, root‑cause analysis, and why AI won’t replace entry‑level analysts but should be leveraged responsibly. Q&A covered startup vs enterprise team composition, tool choices, and sustainable learning.

Tech Crash Mentorship: Data Science, Data Analysis, and Business Analysis – Roles, Skills, and Career Paths

Session overview

A live mentorship session for Tech Crash boot camp applicants explored three closely related but distinct career paths: data analysis, data science, and business analysis. The conversation covered how the roles differ in scope and outputs, day-to-day work, essential skills (technical and soft), realistic learning roadmaps, collaboration patterns in organizations, career sustainability, and practical advice for beginners. The session closed with an audience Q&A tackling common concerns about tools, team composition at startups, and the impact of AI on entry-level roles.

Speakers and roles

• Olani – Data Analyst and Data Scientist (bridges data analysis and data science)
• Esther – Data Analyst specializing in audience engagement analytics
• Victor Quay – Senior Business Analyst (business transformation lead) in insurance
• Joshua Gideon – Business Analyst (formerly data entry and data analyst; half a decade in BA)
• Host/Moderator – Tech Crash team (name not stated)
• Audience Q&A – Kennedy, Taiwo, Aneeb, Legend, Favor (participants)

Role distinctions and how they work together

What each role focuses on (per Olani)

• Data Analyst: Explains what happened and why it happened to support decisions. Primary outputs include reports, dashboards, and recommendations. Tools typically include Excel, SQL, and BI platforms.
• Business Analyst (BA): Frames and prioritizes business problems, elicits requirements, and drives process/systems change to improve delivery. Outputs include problem statements, business/functional requirements, process maps, and change recommendations.
• Data Scientist: Predicts what is likely to happen next and how to optimize outcomes. Outputs include predictive models, forecasts, experiments, and optimization solutions built with Python/ML.

Olani’s analogy: Think of a hospital—data analysts diagnose what’s wrong now; business analysts determine why hospital processes aren’t working and what must change; data scientists predict future problems before they occur.

Collaboration and overlap

• All three work with data; core tasks like data cleaning are universal. In startups, a single professional may wear multiple hats (e.g., a data scientist cleaning data, exploring, and modeling; a BA doing lightweight analysis). In larger organizations, functions are more specialized.
• Victor’s perspective: Every business analyst is (to some extent) a data analyst—the BA must analyze processes and supporting data to propose improvements. But the BA’s core is people, alignment, and process optimization.

Inside the roles: day-to-day and workflows

Data Scientist (per Olani)

• Work varies by organization maturity and problem context.
• Typical activities:
  • Data discovery: Querying databases (SQL), extracting datasets, exploratory analysis.
  • Modeling: Coding in Python (e.g., linear/logistic regression, other ML models), training/validating, and deploying models.
  • Collaboration: Working with analysts, BAs, and stakeholders to connect models to business value and projections.
• Not a static routine—tasks oscillate between data work and modeling, depending on project phase.

Data Analyst practice (per Esther)

• Data’s value: Organizations often have lots of raw information that “says nothing” until analyzed. Analysis turns numbers into insight about what is happening and why.
• Data gathering:
  • Use internal company data (provided access).
  • Conduct surveys/questionnaires when needed.
  • Often combine both to fill gaps.
• Data cleaning: The critical 80%—“garbage in, garbage out.” Poorly cleaned data yields misleading insights. Clean thoroughly before analysis; avoid insights driven by assumptions or sentiment.
• Outputs and recommendations:
  • Build dashboards/visuals and deliver data-backed insights.
  • Keep recommendations grounded in the analyzed data.

Business Analyst (per Victor and Joshua)

• Scope: Identify and prioritize business problems; elicit and document requirements; align cross-functional stakeholders; shepherd solutions; and ensure realized value post-delivery.
• Daily activities:
  • Upstream discovery: Value chain analysis to surface process gaps and needs (sometimes BA discovers problems before a project is defined).
  • Stakeholder engagement: Continuous communication with management (sponsors), delivery teams (devs, testers, PMs), and end users to align on problem and solution.
  • Documentation and facilitation: Draft business cases, BRDs/FRDs, acceptance criteria; run workshops; manage change.
  • Data support: Analyze turnaround times, process metrics, and other indicators to substantiate recommendations.
• What sets BA apart from DA:
  • DAs center on making sense of data to inform decisions.
  • BAs examine and improve the processes that generate those data, ensuring better experiences and outcomes for internal and external users.
• BA and Project Management (PM): Significant overlap in soft skills (communication, facilitation, negotiation). Differences:
  • BA is heavily involved pre-project (problem discovery, business case) and post-project (value realization, feedback, improvements).
  • PM focuses on managing scope, time, budget during project execution and closing the project.

Career journeys and lessons learned

Olani’s path: Nonlinear entry and progression

• Background in quantity/infrastructure; pivoted during pandemic downtime.
• Discovered data analysis and later data science via self-research and online courses.
• Tool progression: Excel → SQL → Python → BI → ML.
• Key insight: You don’t need to “start in tech” to thrive in data roles; consistency and curiosity matter more than background.

Esther’s path: From statistics to audience analytics and content strategy

• Studied statistics; early realization that degree alone didn’t guarantee employability.
• Tried frontend/backend; discovered data analysis as a better fit with statistics.
• First role: Audience engagement analyst; used data to guide content strategies by evaluating what worked historically.
• Insight: Data underpins decisions across functions (e.g., content, marketing, finance). Analytics is the “cement” that binds and guides actions.

Victor’s path: From marketing and digital strategy to business transformation

• Math background; freelanced in SEO, digital marketing, campaign operations.
• Sought structured corporate environment; joined a business transformation program and discovered BA.
• BA unified prior skills (analytics, strategy, light frontend) and passion for problem-solving with people.
• Enjoys working across compliance, marketing, audit—continuous learning via cross-functional exposure.

Joshua’s path: From medical aspirations to business analysis via data

• Studied microbiology; intended medical career.
• Worked in health department (WHO-related) as data entry; later upskilled to data analysis.
• Realized data analysis tells “what happened,” while BA uncovers “why” and drives change—transitioned to BA full-time.
• Emphasizes stakeholder management, communication, and presentation as BA core skills.

Skills and learning roadmaps

Data Science and Data roles: beyond technical skills (per Olani)

• Problem-solving: Ability to frame and solve ambiguous problems is foundational.
• Communication: Translate insights/models into stakeholder-friendly narratives.
• Consistency and lifelong learning: Embrace continuous learning to stay current.
• Curiosity: Ask the right questions; proactively seek knowledge and mentorship.
• Teamwork: Collaborate with analysts, BAs, DBAs, and engineers effectively.

Data Analyst tools and strategy (per Esther)

• Don’t lock into one tool—excel by learning across the stack:
  • Excel for analysis and quick checks.
  • SQL for data retrieval and manipulation.
  • BI tools (e.g., Power BI) for dashboards and visuals.
• Rationale: Job postings vary—some want a single tool, others multiple. Broader coverage increases opportunities.

Data Analyst career opportunities and progression (per Esther)

• Start as a generalist Data Analyst; specialize over time by sector or function:
  • Product Analyst, Marketing Analyst, Content/Strategy Analyst, Financial Analyst, Data Quality Analyst, Healthcare Analyst, Risk Analyst, or Consulting across sectors.
• Choose niches based on interest, industry exposure, or emerging opportunities.

Business Analyst transferable skills from Data Analysis (per Joshua)

• Analytical foundations remain crucial for BAs:
  • Excel for analysis and stakeholder/task tracking.
  • Power BI for visualization and presenting findings.
  • Basic SQL is helpful, especially where DB support is limited.
• Core BA soft skills:
  • Communication and stakeholder management (elicitation, negotiation, alignment).
  • Root cause analysis to find the true drivers behind observed outcomes.
  • Presentation skills for communicating findings and recommendations.

Choosing between Data Analysis and Business Analysis

• Consider your strengths and interests:
  • Prefer heads-down analysis and storytelling with data? Data Analysis may suit you.
  • Enjoy people-centric work—eliciting needs, aligning teams, resolving conflicts, and shepherding change? Business Analysis is a strong fit.
• Communication note: Even introverts can succeed in BA with intentional practice. BA requires frequent speaking, facilitation, and engagement—be prepared to grow these muscles.

Pitfalls, challenges, and how to overcome them

Common beginner mistakes (per Esther)

• FOMO and constant switching: Jumping from data to cybersecurity or other shiny paths dilutes mastery. Focus, build depth, then expand.
• Certificate collecting without real projects: Practice matters more; solve real problems.
• Building only in private: Share your learning and projects publicly to attract early opportunities.

Learning BA: typical hurdles (per Joshua)

• Self-doubt: Confidence grows with practice—lean into deliverables like BRDs, FRDs, business cases.
• Communication discomfort: BA requires heavy stakeholder interaction; commit to improving.
• New concepts: Requirements documentation, elicitation methods, stakeholder mapping—expect a learning curve.
• Overreliance on AI for documents: Prompted outputs may not reflect real stakeholder context. BAs must conduct elicitation, observe processes, and ground documents in reality.

On-the-job challenges in BA (per Victor)

• People friction: Misaligned interests, changing requirements, slow approvals, and interpersonal issues can slow progress.
• Delivery pressures: Devs/testers/PMs may be sources of constraints or blockers.
• Time management: Too many meetings across multiple projects—learn to prioritize and say “this can be an email.”
• Success factors: Build relationships, learn to push back diplomatically, and stay centered as the “orchestra conductor” bringing alignment.

Sustainability and the AI question

• Data careers are sustainable long-term: Organizations will always generate data and need to understand it. Continuous upskilling is necessary as tools evolve.
• Will AI replace entry-level Data Analysts? Joshua’s view: No. AI augments work but doesn’t replace human judgment, context, and stakeholder engagement. Companies increasingly seek analysts who can use AI responsibly, not be replaced by it.
• In BA specifically, core activities—elicitation, observation, negotiation, change facilitation—are deeply human and context-rich.

Startups vs. established organizations: team composition

• Startups often cannot hire separate DA, DS, and BA roles; one generalist may cover multiple functions. What matters is that the functions (data cleaning, analysis, requirements, process mapping) are performed—even if by the founder or a hybrid hire.
• Established organizations are more likely to field specialized, robust data/BA teams based on specific business needs.

Audience Q&A highlights

• Do you need to train as a Data Analyst before becoming a Business Analyst? No. It helps, but it’s not required. BA training starts from fundamentals: role scope, tools, documentation, elicitation, and process improvement.
• Which visualization tool is “best” (Power BI vs. Tableau)? Tools are context-dependent. Employers vary in tool preferences. Learn the BI tool(s) most accessible to you (Power BI commonly mentioned), but remain adaptable.
• Do startups need DA, DS, and BA from day one? Not necessarily. It depends on business needs and resources. Early-stage teams should ensure the underlying functions are covered, even if one person handles multiple responsibilities.
• Is AI taking over entry-level DA roles? No. AI can automate tasks but cannot replace human-driven problem framing, interpretation, and stakeholder-facing communication. Analysts who can leverage AI effectively will be more valuable.
• ML engineering path? Referenced as part of a prior AI-focused session; recommended to consult that replay for a dedicated deep dive.

Practical takeaways and next steps

• If you’re undecided:
  • Sample the foundations of data analysis (Excel, SQL, BI) and business analysis (requirements, process mapping, stakeholder engagement) to gauge fit.
  • Reflect on whether you gravitate toward working primarily with data artifacts or towards people/process alignment.
• Skill-building priorities:
  • Data roles: Excel → SQL → BI; adopt Python/ML for data science progression.
  • Business analysis: Communication, elicitation, stakeholder management, process mapping, documentation (BRD/FRD), basic analytics and visualization.
• Career strategy:
  • Start broad, then niche into industry/function as you gain exposure.
  • Build a public portfolio of projects, case studies, and reflections.
  • Embrace continuous learning; avoid tool tunnel vision.
• Work ethos:
  • Clean your data thoroughly; back insights with evidence.
  • Don’t outsource your thinking to AI—use it as a helper, not a crutch.
  • In BA, invest in relationships and facilitation skills; in DS, prioritize problem framing and communication.

Closing note

The session emphasized that while data analysis, data science, and business analysis are interconnected, they add value in different ways—diagnosing the present, predicting the future, and orchestrating change. Regardless of starting point or academic background, consistent learning, curiosity, and strong communication can power a successful career in any of these paths.