Data scientist interviews in Lagos test four layers: SQL fluency (the daily reality), statistics and ML fundamentals (the foundation), a business case framed in Nigerian data conditions (the differentiator), and the communication round where your take-home write-up matters as much as your model. With Nigerian data scientists averaging around ₦8M/year (BusinessDay) and fintech driving demand, here are the 15 questions that decide Lagos loops — with answer frameworks.
TL;DR:
SQL is tested mercilessly; notebooks impress nobody who can't query.
Local cases (fraud, credit scoring, messy data) separate prepared candidates from imported answers.
The write-up is the silent half of every take-home grade.
How Lagos data loops are structured
Typical sequence: recruiter screen → SQL/Python technical → take-home (48–72 hours, usually a messy real-ish dataset) → presentation and defence → stakeholder/culture round. Banks add statistics depth and governance questions; fintechs add fraud/credit scenarios; internationals add live coding. The bands you're interviewing for are mapped in our data scientist salary guide — know them before the final round asks your expectations.
SQL and data handling (questions 1–5)
"Write a query: top 5 customers by transaction value last month, excluding reversed transactions." Joins, filters, aggregation, ranking — the bread-and-butter screen. Practise window functions (ROW_NUMBER, LAG) until automatic; Lagos interviews love them.
"This table has duplicate transactions from a double-webhook bug. Find and remove them safely." Very Nigerian-fintech: dedupe logic with idempotency awareness. Discuss identifying true duplicates (same reference, amount, window) versus legitimate repeats.
"How would you handle 30% missing values in the income field?" No single right answer — they want reasoning: missingness mechanism, imputation options and their bias trade-offs, or modelling missingness as signal (in Nigerian credit data, missing income is often informative).
"Explain a time you found a data quality issue that changed a conclusion." Have a real story: the metric that doubled because of a logging bug, the duplicated rows that flattered retention. Data scepticism is a hireable trait here.
"Pandas or SQL for this task — and why?" Judgment question: volume, repeatability, where the data lives. "SQL for anything the warehouse can do; Python for what it can't" is a safe spine.
Statistics and ML fundamentals (questions 6–10)
"Explain precision vs recall to a non-technical manager — using fraud detection." The Lagos framing writes itself: precision = of the transactions we blocked, how many were truly fraud (false blocks anger customers); recall = of all fraud, how much we caught (misses cost money). Pick the trade-off based on which error is costlier.
"Your model shows 94% accuracy on fraud data. Why am I unimpressed?" Class imbalance — if 1% of transactions are fraud, predicting 'never fraud' scores 99%. Discuss precision-recall curves, F1, and cost-weighted evaluation.
"Explain overfitting and how you'd detect it with limited data." Train/validation gaps, cross-validation on small Nigerian datasets, regularisation, and the honesty to prefer simpler models when data is thin.
"When would you NOT use machine learning?" Senior signal: rules beat models when patterns are simple and explainability is regulatory (CBN cares), when data is too scarce, or when a SQL threshold solves it. Knowing when not to model is the difference between a scientist and a notebook operator.
"Explain how you'd validate a credit scoring model before deployment." Out-of-time validation, population stability, fairness across segments, and a backtest narrative — borrowed straight from what Lagos lenders actually do.
The business case (questions 11–13)
"Design a churn early-warning system for a Nigerian neobank." Define churn first (dormancy ≠ closure here — wallets sleep and wake), pick observable signals (transaction frequency decay, airtime patterns, login gaps), propose intervention windows, and name the metric the bank actually moves (reactivation rate, not AUC).
"Our agent network's float requests spike unpredictably. How would you forecast them?" Local texture matters: payday cycles, market days, fuel scarcity shocks, regional events. A candidate who mentions naira cash-cycle seasonality instantly outranks one reciting ARIMA hyperparameters.
"You have three months and one analyst. Which data project do you pick for maximum business value?" Prioritisation under constraint — pick something measurable, near revenue or risk, shippable in weeks (the data career-path guide explains why deployed beats elaborate).
Communication and behavioural (questions 14–15)
"Walk us through your take-home." Structure the defence: business question → data issues found (there are always planted ones) → approach and trade-offs → result → what you'd do with more time. Defending a simple, honest model beats overselling a complex one — interviewers probe the parts you understand least.
"Tell me about yourself" + salary expectations. The PPF framework answer in 90 seconds, and a researched band (₦6M–₦10M mid-level; see the salary guide) delivered with the negotiation scripts' calm.
