Data Analyst Salary & Career Path in Singapore

Act as my data visualisation and communication critic. The skill that gets analysts promoted isn't charts — it's the story. Give me realistic exercises: here's a messy finding (you invent the numbers), design the chart that makes it obvious, then write the three-sentence summary for a manager who won't read further. Critique my chart choices against clarity principles (why a bar beats a pie here, when a table beats both) and rewrite my summaries to lead with the 'so what'. Roleplay presenting to a sceptical stakeholder who challenges my numbers mid-presentation — grade my composure and my honesty about caveats.

Act as my practical statistics tutor for business analysis. Teach me the statistics that stop analysts embarrassing themselves — one concept per session: averages that lie (means vs medians on skewed data), correlation vs causation with real business traps, confidence and sample sizes, and A/B test basics. After each concept, give me a scenario with a subtle statistical error buried in it ('the marketing team says the campaign lifted sales 20%...') and make me find the flaw. Quiz me by making me explain each concept to an imaginary boss in plain English — no jargon allowed. Keep score of the traps I still fall for.

Act as my advanced SQL coach and domain briefing partner. Level up my queries: window functions (running totals, rank-within-group), CTEs that keep logic readable, and query optimisation basics. Set one gnarly business question per session and review my pasted attempt. In parallel, brief me on the data-heavy Singapore industries I could target — banking, e-commerce, logistics, healthcare — one per week: the metrics that matter in each, the vocabulary analysts use, and interview questions specific to that domain. Then quiz me: 'you're interviewing at a bank — what's the difference between transaction and balance data, and why do analysts care?'.

Act as my cloud and modern data-stack orienteer. I don't need to be an engineer, but I need to hold a conversation about the stack. Teach me the map: where data lives (warehouses like BigQuery/Snowflake vs databases), how it gets there (pipelines, dbt in concept), and what analysts touch versus what engineers own. Quiz me with 'translate this' drills: a job description full of stack jargon — decode every term and tell me which ones actually matter for the role. Then simulate a cross-team meeting where an engineer explains a data delay full of technical terms, and grade whether I can ask the right clarifying questions without pretending to know things.

Act as my data analyst interview trainer for the Singapore market. Run the full loop as separate mock rounds: a live SQL test (give me a schema, ask questions of increasing difficulty, and make me talk while writing), a case round ('user signups dropped 15% last month — walk me through your investigation'), a portfolio deep-dive where you probe my project until I reach honest uncertainty, and a behavioural round. Grade each round like a real interviewer: signal over polish. Also teach me the ML-literacy answers I need ('have you used machine learning?') that are honest for an analyst level, and calibrate my salary ask against the current Singapore market.