Career Guide · Commerce · Jobs & Salary

How to Become a Data Analyst After B.Com and M.Com: Skills, Salary, Jobs and Projects

SECTION 01The five skills that get tested

Job descriptions list fifteen tools. Interviews test five things. Prepare in this order and you cover the vast majority of what you will face.

SECTION 02Salary — what the role actually pays

Ranges below reflect analyst hiring in India during 2026. Treat them as bands, not promises; company type moves the number more than city does.

What moves your number

• Company type — product companies and analytics consultancies pay above service firms and captives, often by 40–60% at the same experience level.
• SQL depth — window functions and query optimisation reliably shift offers upward.
• Python — adding working‑level Python typically moves a profile up one band.
• Domain — finance, risk and pricing analytics pay more than generic reporting.
• Switch timing — the biggest single jump usually comes at the two‑year mark, not at the first job.

SECTION 03SQL — the round that decides most outcomes

If you prepare one thing properly, make it this. Analyst SQL rounds are live, timed and unforgiving, and they follow a predictable pattern.

What you’ll learn

• Joins — inner, left, and diagnosing a doubled row count
• Aggregation — GROUP BY, HAVING, conditional sums with CASE
• Subqueries and CTEs — building a multi‑step answer readably
• Window functions — ROW_NUMBER, RANK, LAG, running totals
• Date handling — month‑on‑month, year‑to‑date, ageing buckets
• Second‑highest, top‑N‑per‑group and duplicate‑detection patterns

Job titles

Data Analyst SQL Analyst Reporting Analyst BI Analyst

-- SQL: the single most important skill for an analyst
-- Question: which product category earned the most last quarter?

SELECT
    p.category,
    COUNT(DISTINCT o.order_id)      AS orders,
    ROUND(SUM(o.amount), 2)         AS revenue,
    ROUND(AVG(o.amount), 2)         AS avg_order_value
FROM orders o
JOIN products p ON p.product_id = o.product_id
WHERE o.order_date >= '2026-04-01'
  AND o.order_date <  '2026-07-01'
  AND o.status = 'completed'
GROUP BY p.category
HAVING SUM(o.amount) > 100000
ORDER BY revenue DESC
LIMIT 10;

-- If you can read this query, you can already do 40% of an analyst's daily work.

' Excel / Google Sheets - the formulas that get asked about in interviews

' 1. Lookup a value from another sheet (modern, safe version)
=XLOOKUP(A2, Customers!$A:$A, Customers!$D:$D, "Not found")

' 2. Conditional total with two criteria
=SUMIFS(Sales[Amount], Sales[Region], $A2, Sales[Month], B$1)

' 3. Count unique customers
=SUMPRODUCT(1/COUNTIF(Sales[Customer], Sales[Customer]))

' 4. Month-on-month growth %
=IFERROR((C2-B2)/B2, "")

' 5. Clean text before analysis
=TRIM(PROPER(CLEAN(A2)))

' Master these five and pivot tables, and Excel stops being a blocker.

# Python + pandas: clean a messy sales file and answer a business question
import pandas as pd

df = pd.read_csv("sales_2026.csv")

# 1. Clean
df.columns = df.columns.str.strip().str.lower()
df["order_date"] = pd.to_datetime(df["order_date"], errors="coerce")
df["amount"] = pd.to_numeric(df["amount"], errors="coerce")
df = df.dropna(subset=["order_date", "amount"])

# 2. Answer: monthly revenue per region
monthly = (
    df.groupby([df["order_date"].dt.to_period("M"), "region"])["amount"]
      .sum()
      .unstack(fill_value=0)
      .round(0)
)
print(monthly.tail(6))

# 3. Flag the drop that a manager will actually ask about
change = monthly.pct_change().iloc[-1] * 100
print(change[change < -10].sort_values())

SECTION 04Excel and dashboards — the practical rounds

The Excel round is usually a deliberately messy file and a 40‑minute clock. The dashboard round tests judgement more than tooling — can you decide what belongs on the page?

What you’ll learn

• Cleaning at speed — text‑to‑columns, TRIM, duplicate removal, Power Query
• Lookups and multi‑criteria aggregation under time pressure
• Pivot tables with grouped dates and calculated fields
• Power BI — Power Query, relationships, DAX measures
• Dashboard judgement — one question per page, ranked bars over pie charts
• Explaining what a manager should do differently after reading it

Job titles

MIS Analyst BI Analyst Power BI Developer Reporting Analyst

SECTION 05Business reasoning — where commerce wins

You will get a question like “monthly revenue fell 12%, what do you check?”. Interviewers are not testing knowledge; they are testing whether you have a structure. Use this one.

1. Verify before investigating — is the drop real, or a data issue? Check row counts, a missing region, a delayed feed, a changed definition.
2. Split the metric — revenue is volume × price. Which side moved?
3. Cut by dimension — region, product, channel, customer segment, new versus repeat. Find where the drop concentrates.
4. Compare like with like — month‑on‑month, same month last year, working‑day adjusted.
5. Check known events — price change, stockout, campaign end, competitor action, seasonality.
6. State the finding and the action — one sentence on cause, one on what you recommend, one on what you are still unsure about.

SECTION 06Who hires commerce graduates for analytics

Not all employers are equally open. These categories hire non‑engineering candidates most readily.

How to reach them

• Referrals first — a message to an alumnus with your dashboard link outperforms fifty portal applications.
• Apply within 48 hours of a posting going live; shortlists close fast.
• Target the role names, not the title “Data Analyst” — search MIS, Reporting, Business Analyst, Category Analyst, Credit Analyst too.
• Keep a project link in your CV header so a recruiter can verify you in one click.

SECTION 07Five projects that get replies

Each of these uses data a commerce graduate can explain confidently, and each answers a question a real manager would ask.

• 1. Revenue and margin dashboard. Twelve months of transactions in Power BI: revenue, gross margin, top customers, product mix, variance against budget.
• 2. Receivables ageing and cash risk. SQL buckets by days outstanding, concentration of risk by customer, and the cash impact of a 15‑day collection improvement.
• 3. Discount leakage analysis. Quantify how much margin discounting cost last year by product and salesperson, then recommend a ceiling with numbers behind it.
• 4. Expense classification with AI. Use an LLM to categorise several thousand free‑text expense descriptions, then measure accuracy against 200 rows you labelled by hand.
• 5. Automated monthly reporting pack. A Python script that reads raw exports, cleans, merges and outputs a formatted Excel file. Report the hours saved.

# Working with an LLM API - the everyday skill in AI-era analytics
import os, json, requests

def classify_feedback(text):
    """Turn free-text customer feedback into structured data."""
    prompt = (
        "Classify the customer feedback below.\n"
        "Return ONLY JSON with keys: sentiment (positive/neutral/negative), "
        "topic (delivery/pricing/quality/support/other), urgent (true/false).\n\n"
        f"Feedback: {text}"
    )
    r = requests.post(
        "https://api.example-llm.com/v1/messages",
        headers={"x-api-key": os.environ["API_KEY"]},
        json={"model": "small-fast", "max_tokens": 200,
              "messages": [{"role": "user", "content": prompt}]},
        timeout=30,
    )
    return json.loads(r.json()["content"][0]["text"])

rows = [classify_feedback(t) for t in open("feedback.txt")]
print(rows[:3])
# 2,000 rows of text become a table you can chart. That is the new analyst workflow.

SECTION 08M.Com specifically — where your extra two years pay

An M.Com does not automatically raise your analyst salary, but it opens doors that B.Com alone does not.

SECTION 09Step‑by‑step plan — six months to skills, 90 days to a job

Two phases. Do not run them in sequence — overlap the last two months of study with the first month of applications.

1. Month 1: Excel — cleaning, lookups, SUMIFS, pivots, Power Query. Deliverable: a rebuilt messy workbook.
2. Month 2–3: SQL — joins to window functions, 120 solved problems. Deliverable: Project 2, receivables ageing.
3. Month 4: Power BI — modelling and DAX. Deliverable: Project 1, the revenue and margin dashboard.
4. Month 5: analysis thinking and Python basics — variance, trends, pandas. Deliverable: Project 3, discount leakage.
5. Month 6: AI tools and automation — Deliverables: Projects 4 and 5, plus a tidy GitHub and a one‑page CV.
6. Job days 1–30 — 10 applications a week, 5 referral messages a week, daily timed SQL practice.
7. Job days 31–60 — adjust based on rejections: no calls means fix the CV, failed SQL rounds mean more drills, failed case rounds mean rehearse the framework aloud.
8. Job days 61–90 — widen to MIS, reporting and operations analyst titles, and to tier‑2 cities. Take the offer that gives you real data to work on.

SECTION 10Skills to learn — the complete list

The core list is the interview syllabus. The specialisation row decides which team you land in.

Core skills (needed on every path)

• Excel / Google Sheets — formulas, lookups, pivot tables, charts
• SQL — SELECT, JOIN, GROUP BY, window functions, CTEs
• Python — variables, loops, functions, pandas, numpy
• Statistics — mean, median, distribution, correlation, hypothesis testing
• Visualisation — Power BI or Tableau, plus matplotlib / seaborn
• Business sense — asking the right question before touching the data
• Communication — explaining a number to someone who did not build it
• Version control — Git and GitHub for your portfolio

Path‑specific skills

SECTION 11Interview Q&A — B.Com and M.Com candidates

SECTION 12Test yourself — B.Com / M.Com analyst job readiness

SECTION 13Frequently asked questions

SECTION 14Continue from here