4 min readLearningUpdated
From Civil Engineering to Data Engineering
I trained and worked as a civil engineer. The move into data happened gradually, through the information the engineering work kept producing, and the way of thinking came with me.
I did not start in tech
I studied Civil Engineering at Universiti Putra Malaysia from 2017 to 2021. Mathematics had always been one of my stronger subjects, and engineering connected with the direction my family knew.
I started on construction sites, coordinating workers, reviewing drawings and checking measurements against the design. Once something is built, a mistake is expensive to undo. Checking carries on throughout a project, but the checks made before the work carry a lot of weight. Then came BIM, turning 2D drawings into coordinated 3D models, and in 2022 geotechnical engineering at G&P Geotechnic. I liked the work, and I still think of myself as an engineer.
The data was already there
Part of my work at G&P involved time-series readings from engineering equipment, and some of those datasets contained millions of readings. The engineering question was simple to state: is this behaving the way it should? Answering it meant getting through the data first, plotting readings, finding abnormal values and comparing them with the history.
I cannot show any of that here. The data belongs to the projects it came from. What I can describe is where the time went, and that it was the part of the job I kept thinking about after the task was done.
I started automating the boring parts
The questions were small ones. Could I automate this calculation? Could I process this with Python? Could I make this Excel workflow easier with VBA?
VBA came first, because Excel was where the work already lived. Python came in where a spreadsheet stopped being comfortable. Each tool arrived the same way: a specific annoyance, a small experiment, and something I could reuse next time. The tools changed. That way of learning stayed.
In 2023, still working as a geotechnical engineer, I took four data credentials: Azure Data Fundamentals, the Certified Data Analyst Associate at APU, PCEP and Power BI Data Analyst. I did not take them as an exit plan. The data side of the work had become the part I most wanted to do properly. I also practised in public, cleaning the London bike-sharing data in Python (opens in a new tab) and a raw bike sales dataset in Excel (opens in a new tab).
Fig. 1 / The path, dated
3 undated credentials not plotted
Data became the work
In May 2024 I joined EISmartwork as a Data Analyst: Power BI dashboards with MSSQL underneath, on reporting datasets with millions of records. The longer I worked on dashboards, the more of my attention went below them. A dashboard is only as reliable as the model under it, and the model is only as reliable as whatever prepared the data.
What happens before the dashboard?
I kept moving upstream
Since June 2025 I have worked as an AI Data Engineer at AEM Energy Solutions, on data migration, automation, data quality and the pipelines between systems. One example is a Python migration of around 700,000 records from an MSSQL source into a NoSQL target through an existing API. Moving the records was the simple part. Most of the effort went into understanding how the API behaved and handling the cases that could fail partway through.
In engineering, the conditions on the ground are not always as clean as the drawings suggest. Data migrations have their own version of that problem: sooner or later the source contains cases the specification did not describe. This is where data engineering stopped feeling like a career choice and started feeling like the natural place for the way I already worked.
Data led me to AI
AI grew out of the data work. Machine learning was close to what I had already done with equipment readings. In September 2024 I started a Master of Science in Artificial Intelligence at UMPSA while working, and finished in 2025. My research project asked whether duplicate questions could be detected accurately without the heaviest models.
Some of my work now uses agentic workflows, such as QualityPlus, which I wrote about in Where AI Belongs in a Data Quality Workflow. Much of it does not use AI at all. The question I find most useful is which parts of a system should stay deterministic, and where a suggestion would actually help a person.
Building became how I learn
- FORMA came from writing similar ETL logic again and again. I wrote about that in Why I am building FORMA.
- VSB came from organising volleyball sessions through messages and individual coordination.
- Sepang Vision Lab came from following Formula 1 and wanting to see what a 3D replay built from real race data could show.
- BALANG is a party game about probability and kuih, with rooms that need no server.
The path changed. The way I think did not.
The medium changed more than the method. Engineering taught me to be careful with inputs, because they do not tell you everything on their own. It taught me to respect constraints that are real, to think about the whole system rather than one part of it, to ask how something fails before asking how well it performs, and to treat the first design as something to test and revise.
On this site I call it input, process, iterate, progress. I was working that way long before I wrote it down.
