About
I’m Eric Wang, an infrastructure engineer based in Sydney. I’ve worked in production operations for about twenty years (since 2006), and I care about systems that are reliable, secure and fast, and about explaining the trade-offs between those three honestly.
In brief
| Based in | Sydney, Australia |
| Roles | DevOps Engineer · Site Reliability Engineer · Platform & Infrastructure Engineer · Linux Systems Engineer |
| Focus | Reliability, Linux performance, cloud infrastructure, security |
| Languages | English and Mandarin Chinese |
Where I’ve worked (by phase, not by employer)
- Enterprise Unix/Linux and data-centre operations: large bank, 2006–2017. Physical servers, OS hardening, change control, and the habits that come from running systems people’s money depends on.
- Big data and DevOps/SRE: consulting-style engineering team, 2017–2023. AWS, Terraform, Ansible, Kubernetes, Kafka, Spark.
- Trading infrastructure (SRE, Infra Engineer, DevOps): trading firm, September 2023–present. Building and operating latency-sensitive infrastructure on AWS: platform, delivery, observability, network connectivity, access control and data-platform integration.
How I work
- Production reality beats diagrams.
- Reliability is an engineering discipline: SLIs, SLOs, error budgets, and post-incident learning.
- Every decision is a trade-off; I write the trade-off down.
- Security and performance are designed together, not bolted on.
- Depth over breadth, but I keep learning: see the Lab.
What I work with
| Area | Tools and topics |
|---|---|
| Linux performance | CPU affinity, NUMA, HugePages, IRQ, kernel and network tuning, time sync, latency measurement |
| Cloud | AWS: EC2, VPC, IAM, EKS, S3, CloudWatch, Route 53, RDS |
| Infrastructure as code | Terraform, Ansible |
| Containers and delivery | Kubernetes, Helm, Argo CD / GitOps, Jenkins, Bamboo, GitHub Actions |
| Observability | Prometheus, Alertmanager, Grafana, Loki, ELK |
| Data | PostgreSQL, MySQL, Redis, Kafka, RabbitMQ, Spark, ClickHouse |
Everything above is a statement of working familiarity. Anything I am only exploring is labelled as such in the Lab.
What I write about
Start with the Writing archive or the Lab notes.
Boundaries
- I don’t publish employer names, internal architecture, hostnames, IPs, account identifiers or screenshots.
- Case studies use synthetic or reproducible environments, never employer data.
- Corrections are logged on Errata.
- Opinions are my own.
Contact
Email eric.wang984@gmail.com or find me on LinkedIn. Open to consulting and part-time work. See Contact.