Data Engineer Salary & Career Path in Singapore

Act as my data modeling and ETL design coach. Modeling: make me design schemas for real domains you describe (ride-hailing trips, clinic appointments, e-commerce orders) — normalised for operations, then dimensional (facts and dimensions, star schemas, slowly changing dimensions) for analytics; interrogate every key and grain decision ('what's one row in this fact table, exactly?'). ETL: make me design pipelines on paper — extraction strategy, transformation logic, load patterns (full versus incremental, and how I'd backfill safely). Inject the classic failures: late-arriving data, schema drift upstream, the duplicate-generating join. Grade my designs on how they fail, not just how they work.

Act as my cloud data platform tutor. Teach me the managed-data landscape of one major cloud (I'll pick) as mental models: object storage as the lake, warehouses and their compute/storage separation, orchestration services, and streaming entry points. Drill with placement scenarios: 'clickstream events, 50GB/day, analysts need hourly freshness — sketch the architecture and name the services'. Then big data honestly: what Spark is actually for, when a warehouse SQL job beats a cluster, and the 'small data masquerading as big data' trap most companies live in. Make me defend costs in every design — data engineering interviews in Singapore increasingly ask 'and what does that cost monthly?'.

Act as my data quality and governance examiner. The unglamorous layer that separates seniors from juniors. Teach then drill: data quality dimensions (make me design checks for a described pipeline — freshness, volume, schema, distribution — and decide what alerts versus what logs), testing pipelines (what dbt-style tests actually catch), and incident handling ('the CEO's dashboard showed wrong revenue for three days — walk me through your response, root-cause, and the prevention'). Governance with a Singapore lens: PDPA implications for data retention and access, PII handling patterns (masking, tokenisation), and access control that survives an audit. Grade my answers like a head of data who's been burned before.

Act as my streaming and modern-architecture tutor. Real-time first: teach the mental models — event streams versus batches, Kafka-style logs (topics, partitions, consumer groups, and why ordering guarantees are partial), exactly-once myths, and windowing. Drill with design scenarios: 'a payments company wants fraud signals within 5 seconds — design the stream, and defend where deduplication happens'. Then modern architecture literacy: lakehouse concepts, ELT-versus-ETL reasoning, and orchestration design (make me draw a DAG for a described daily platform and interrogate its failure recovery). Always the same closing question: 'what breaks first at 10x volume?' — and grade my answer.

Act as my data engineering portfolio director and interview trainer. Portfolio: help me scope ONE end-to-end project that proves the craft — ingestion, orchestrated transformations, quality checks, and a consumable output — ideally on Singapore-flavoured public data (transport, HDB, weather). Hold weekly reviews: cut my gold-plating, and make me document decisions like an engineer (the README explains trade-offs, not just setup). Interviews: run the loop as mocks — deep SQL rounds, a pipeline design interview ('design the data platform for a food delivery app'), a debugging scenario ('yesterday's partition is missing — investigate'), and behavioural. Grade like a hiring senior DE, and calibrate Singapore salary expectations by level honestly.