Phase 6 — Job Ready

Module 14: Your First 90 Days

Starting Your Career  ·  ~20 minutes  ·  Final Module

This Is the Last Module

You've built SQL skills, Tableau and Power BI dashboards, a Python data analysis, a capstone portfolio, and SAP FI/CO knowledge — using only free tools. That is not a small thing.

This final module is about what happens after you land the role. The interview gets you in the door. The first 90 days determine whether you stay, grow, and thrive.

No tools needed. Just read, reflect, and plan.

The 90-Day Framework

Most organizations — whether they say it explicitly or not — evaluate new hires across three 30-day windows. Knowing this lets you set appropriate expectations for yourself and pace your energy correctly.

Days 1–30

Listen and Learn

  • Your job is to observe, not to fix. Resist the urge to suggest changes immediately.
  • Learn the actual data: what systems exist, where data lives, how reports are built today.
  • Understand the business language — every team has its own vocabulary for metrics, KPIs, and processes.
  • Build relationships with 2–3 people: your manager, a peer analyst, and ideally someone in finance or operations who uses the data you'll produce.
  • Set up your tools: access permissions, Tableau / Power BI connections, SAP read access if applicable.
  • Take notes on everything. Create your own "new joiner wiki" — what you wish you'd known on day 1.
Days 31–60

Contribute and Connect

  • Start owning small deliverables: a report refresh, a dashboard update, a data quality check.
  • Identify one thing you can make better — and fix it. Document what you did and why.
  • Ask your manager: "What does success look like at 90 days?" If they haven't told you, ask now.
  • Join team meetings actively — you don't need to lead, but follow along and ask one thoughtful question per meeting.
  • If you're in an SAP environment: shadow a user during month-end close to see real T-codes in action.
Days 61–90

Lead a Small Win

  • Take ownership of a project — even a small one. Propose it, scope it, deliver it.
  • Present findings to at least one stakeholder. Practice translating data into business language.
  • Update your portfolio: add a real-work example (anonymized if needed) or a new case study.
  • Have a check-in with your manager. Come prepared with: what you've done, what you're working on, and what you want to learn next.
  • Start thinking about what skill to grow in months 4–6.

Your First-Week Priorities

Before the 30-day framework kicks in, survive the first week with these:

  1. Write down every tool, system, and login you get access to. You will forget. Write it down the moment it happens.
  2. Find out how the team communicates. Slack? Email? Standing meetings? Async docs? Match the culture or ask directly.
  3. Locate the data. Where does the raw data come from? What's in the database? What reports already exist? Don't reinvent anything until you know what exists.
  4. Meet your manager for a 1:1 in week 1. Ask: "What are the top 3 things I can help with in my first month?"
  5. Be kind to yourself. Starting a new job is cognitively exhausting for everyone — and especially for ND brains adapting to a new environment, new people, new systems, and new routines simultaneously.

Tools You'll Actually Use

Here's how your course tools map to real workplace situations:

SQL
Querying databases, ad-hoc analysis, data validation, pulling export files
Google Sheets / Excel
Quick calculations, sharing results with non-technical teams, pivot tables
Tableau / Power BI
Recurring dashboards, executive reports, self-service analytics
Python / pandas
Automating data cleaning, complex transformations, large datasets
SAP T-codes
Reading FI/CO data, supporting month-end, validating financial postings
GitHub
Version control for scripts and notebooks, code sharing, portfolio maintenance

Being Neurodivergent at Work

The workplace is designed for neurotypical brains. That's a structural reality, not a personal failure. Understanding your own needs and building systems around them — before problems arise — is the most practical thing you can do for your career.

Managing Overwhelm

  • Build a "shutdown routine" for the end of each workday: write 3 tasks for tomorrow, close tabs, step away
  • Batch similar tasks (all emails at 10am, all analysis at 2pm) to reduce context-switching cost
  • Identify your 2–3 peak focus hours and protect them for deep work
  • It's okay to say "Can I send you my thoughts in writing?" instead of answering verbally on the spot

Communication Strategies

  • If verbal meetings drain you, follow up with a written summary: "Just to confirm, we decided X and Y is the next step" — this protects you and your colleagues
  • Ask for agendas before meetings so you can prepare
  • If you miss something, ask. "Could you clarify what you meant by X?" is professional
  • Over-communicate progress on tasks — brief status updates reduce anxiety for everyone

Workplace Accommodations

  • Many countries require employers to provide reasonable accommodations — quiet space, flexible hours, written instructions
  • You don't have to disclose a diagnosis to ask for accommodations — you can describe what you need functionally
  • HR is required to keep accommodation requests confidential from your team
  • Accommodations are most effective when requested early, before problems build up

Building Sustainable Habits

  • Use a task manager (Notion, Trello, a paper list — whatever sticks) and review it every morning
  • Time-block your calendar — don't leave it open for meetings to fill
  • Build in buffer time: things always take longer than estimated
  • Find one colleague you trust. ND professionals thrive with even one person who "gets it"

Your neurodivergent traits are also assets. Pattern recognition, deep focus on problems that matter, systematic thinking, attention to detail, ability to work independently, creativity under constraints — these are not incidental. They are what make many ND analysts genuinely excellent at the work.

Your 5 Pre-Start Tasks

Do these before your first day (or in your first week if you've already started):

  1. 1
    Write your personal "user manual." A 1-page document about how you work best: your peak hours, how you like to receive feedback, what helps you focus, what drains you, how you prefer to communicate. You don't have to share it immediately — but having it ready helps you articulate your needs when the time comes.
  2. 2
    Set up your task system before day 1. Whether it's Notion, a notebook, a whiteboard, or a simple text file — have your task management system ready before you start. New jobs generate enormous cognitive load. Don't figure out your system at the same time you're figuring out everything else.
  3. 3
    Update your LinkedIn profile. Add your new role, your capstone project in the Featured section (link to GitHub), your Tableau Public profile, and your openSAP certificates. Your online presence is a living portfolio — keep it current.
  4. 4
    Bookmark your tools and add them to your browser profile. SQLiteOnline, Tableau Public, Power BI, Google Colab, your GitHub, openSAP — bookmark them now so they're ready when you need them. Small friction reduction adds up.
  5. 5
    Plan your decompression for your first week. Starting a job is exhausting. Book something restorative for each evening of your first week — a walk, your favorite meal, a game, a show. Don't make big decisions in week 1. Don't judge how the job is going in week 1. Just absorb, rest, and repeat.
Bonus: Write Your Own 90-Day Plan

Open a Google Doc, Notion page, or notebook and write 3 goals — one for each 30-day block. Keep them realistic and specific to your actual role and company. Review it at day 30, day 60, and day 90. Adjust as you learn more. The act of writing it is the point — it gives your brain a structure to move toward.

Last One. Make It Count.

This is the last brain break of the course. You've earned it more than once.

Pick something that actually restores you — not just a quick scroll:

10-minute walk outside Make a proper cup of tea or coffee Lie on the floor for 5 minutes Listen to one full song you love Call someone you like Draw or doodle freely Do absolutely nothing for 3 minutes

Come back when you're ready for the final section.

You did it.

Data Analyst Course: Complete

You built real skills using real tools. You learned SQL, cleaned data, built dashboards in Tableau and Power BI, wrote Python, built a portfolio, learned SAP FI and CO, and prepared to walk into interviews and your first 90 days with a plan.

Every module was designed for your brain. And you showed up — through the hard parts, the confusing parts, the "I need a break" parts — and you finished.

14 modules · 6 phases · 100% free tools

What's Next

The course is complete. But learning doesn't stop here. Here are concrete next steps based on where you want to go:

🔍

Keep the Portfolio Growing

Add one new project every 1–2 months. Choose datasets from your actual interests — sports, music, social trends, finance. Real curiosity makes better analysis.

📊

Go Deeper on One Tool

Pick one: advanced SQL (window functions, CTEs), Python (Matplotlib, Seaborn, scikit-learn), or Power BI DAX. Depth beats breadth at the junior level.

🌐

SAP Certifications

openSAP is free and adds credibility. SAP Associate certifications (paid, ~$500 USD) are worth pursuing once you have 6–12 months of work experience with SAP.

🤝

Find Your Community

Reddit (r/dataanalysis, r/SQL), LinkedIn groups, local Tableau or Power BI user groups. ND communities in data exist too — you are not alone in how you work.

📝

Keep a Learning Log

A simple weekly note: what did I learn, what did I struggle with, what am I curious about? It compounds. In six months you'll be astonished at how far you've come.

💙

Rest Is Also Progress

Not every week needs a new skill. Rest, recover, consolidate. Your brain learns while you sleep. Taking breaks is not falling behind — it's how learning works.

You built this. It's yours. Good luck out there.