Phase 6 — Job Ready

Module 13: Interview Prep

SAP + Data Analyst Roles  ·  ~22 minutes  ·  5 sections

📄 Save or print this lesson:
Part 1 — Before You Start

What You Need Ready

This module is low-pressure. There are no right or wrong answers here — just practice. The goal is familiarity, not perfection.

Part 2 — The Concept

Common Interview Questions

Interviews for data analyst and SAP roles follow patterns. Here are the most common questions — and how to think about answering them.

General Data Analyst Questions
Walk me through your data analysis process.
Start with the business question, collect and clean the data, explore it, build visuals to find patterns, then present insights with a recommendation. Your capstone project is a perfect real example of this full process.
What tools have you used for data analysis?
SQL (SQLiteOnline), Google Sheets for quick exploration and pivot tables, Tableau Public and Power BI for dashboards, and Python with pandas in Google Colab for larger datasets and transformation work.
How do you handle missing or messy data?
First identify the type — is it missing, duplicate, or formatted wrong? Then decide: fill with a mean/median, flag it, or remove it if it's a small percentage. Always document what you changed and why, so your process is reproducible.
Describe a time you turned data into a business decision.
Use your capstone project here. Describe the dataset you chose, what you discovered, and the recommendation you made. Even a small personal project is a real answer.
How do you explain technical findings to non-technical stakeholders?
Lead with the insight, not the method. Instead of "I ran a GROUP BY query," say "I looked at sales by region and found that the North outperforms by 30%." Then offer to show the underlying data if they want to go deeper.
SQL Questions
What is the difference between WHERE and HAVING?
WHERE filters rows before aggregation. HAVING filters after. So WHERE sales > 100 filters individual rows; HAVING SUM(sales) > 100 filters groups created by GROUP BY.
Explain the difference between INNER JOIN, LEFT JOIN, and RIGHT JOIN.
INNER JOIN returns only matching rows from both tables. LEFT JOIN returns all rows from the left table plus any matches from the right (unmatched right rows are NULL). RIGHT JOIN is the mirror of LEFT JOIN.
What is a subquery?
A query nested inside another query. For example: SELECT * FROM employees WHERE salary > (SELECT AVG(salary) FROM employees). It runs the inner query first, then uses that result in the outer query.
SAP FI/CO Interview Questions
What is the organizational structure in SAP FI?
Client is the highest level (the whole company). Under that: Company Code (a legal entity — like one country's operation), which is assigned a Chart of Accounts (the master list of GL accounts), and within that are the individual GL Accounts where transactions post.
What is the difference between FI and CO in SAP?
FI (Financial Accounting) is external-facing — it produces the legal financial statements (balance sheet, P&L) required for regulators and auditors. CO (Controlling) is internal-facing — it tracks costs and profitability for management decisions. They share data: when FI posts a cost, CO captures it against a cost center or internal order.
What is a cost center in SAP CO?
A cost center is an organizational unit in CO that collects costs for a specific area — like a department, team, or function (HR, IT, Marketing). It helps management see where money is being spent internally. T-code KS01 creates a cost center; KSB1 shows its line items.
What is a reconciliation account?
A GL account in FI that is automatically updated when subledger postings occur. For example, when you post a vendor invoice in AP, the vendor's subledger is updated AND the AP reconciliation account in GL is updated simultaneously. This keeps FI and the subledgers always in balance without manual journal entries.
What is SPRO used for?
SPRO (SAP Project Reference Object) is the Implementation Guide (IMG) — it's the configuration menu. All SAP system setup happens here: defining company codes, chart of accounts, fiscal year variants, document types, and posting keys. It's where consultants configure SAP for a client's specific business needs.
Walk me through the procure-to-pay process in SAP.
Purchase Order created in MM → Goods Receipt posted (inventory increases, GR/IR account debited) → Vendor Invoice received in AP (MIRO — matches PO and GR) → Payment run clears the vendor open item (F110). Each step creates a linked FI document that auditors can follow.
Part 3 — Why It Matters

The Interview Is a Skill — and Skills Are Learnable

Many neurodivergent job seekers are stronger at the actual work than at talking about it under pressure. That's not a character flaw — it's a mismatch between the format (high-pressure spoken interview) and how many ND brains work best (written, prepared, structured).

The good news: interviews have predictable patterns. Most interviewers ask the same categories of questions. Preparing answers in advance and practicing saying them out loud — even to yourself or a mirror — dramatically reduces the cognitive load in the room.

The STAR Method

Use this structure for any "tell me about a time when…" question:

S
Situation

Set the scene in 1–2 sentences. What was the context?

T
Task

What was your specific responsibility or challenge?

A
Action

What did YOU do? Use "I" not "we." Be specific.

R
Result

What happened? Numbers are great. Learning is also a result.

Neurodivergent Interview Tips

Part 4 — Practice

Your 5-Step Interview Prep Routine

  1. 1
    Write your "tell me about yourself" script. Keep it to 3 parts: who you are professionally, what you've built (mention your capstone + SAP coursework), and what you're looking for. Write it, then say it out loud 3 times. Aim for 60–90 seconds.
  2. 2
    Write STAR answers for 3 situations from your learning journey. Use your capstone project, a challenging module, and a moment you figured something out independently. Write each one using the Situation → Task → Action → Result format. Doesn't need to be long — 4–6 sentences per answer is enough.
  3. 3
    Prepare your portfolio walkthrough. Open your GitHub portfolio and practice explaining it as if someone just asked "walk me through your work." Cover: what dataset you used, what questions you asked, what you found, and what you'd recommend. 2–3 minutes max.
  4. 4
    Review your SAP knowledge out loud. Pick 3 SAP concepts from Modules 10–12 (like the org structure, FI sub-modules, or FI-CO integration) and explain each one as if teaching it to someone new. Speaking it out loud — even alone — builds fluency.
  5. 5
    Prepare 3 questions to ask the interviewer. Good candidates ask questions. Examples: "What does a typical first month look like?", "What data tools does the team use daily?", "How does the team handle reporting — Tableau, Power BI, or SAP reports?" Write them down so you don't blank in the moment.

Your Prep Checklist

Part 5 — Brain Break

You Just Did a Lot — Rest for 2 Minutes

Interview prep is genuinely cognitively demanding. Your brain just processed dozens of Q&As, frameworks, and personal reflection. That's hard work.

Pick one:

Stand up and stretch Look out a window for 60 seconds Drink a full glass of water 5 slow deep breaths Doodle for 2 minutes Shake your hands out

The decompression is part of the learning. Don't skip it.

Part 6 — You Got This

Module 13 Complete

You now have a structured interview prep system. You know the patterns interviewers use, you have the STAR method to structure behavioral answers, you have SAP-specific Q&As to review, and you have concrete neurodivergent strategies to reduce the cognitive load of interviews.

The interview is not a test of your worth. It's a structured conversation where both sides are figuring out fit. You've built real skills and a real portfolio. That's what you're bringing to the table.

One module left. Let's talk about your first 90 days.