01 A little introduction
Rujikorn Ngoensaard
Senior Data Engineer
I build and operate
enterprise data platforms.
Where I started
Bachelor’s in Electrical and Electronic Engineering,
Ubon Ratchathani University, 2013–2017.
Outside of work
02 The journey
An evolving practice across manufacturing, commerce and enterprise data.
2013–2017 · The foundation
Electrical and Electronic Engineering
Ubon Ratchathani University
Nov 2017–May 2020
Process Engineer, Engineer I
Developed diagnostic and repair-routing automation for HDD testing. Operated scripts across 130+ Linux VMs and coordinated technical repair and retest work.
May 2020–Dec 2021
Product Design Engineer
Promoted from Senior to Staff Engineer
Automated reporting and centralized data workflows with Airflow. Redesigned ML prediction services for HDD testers.
Jan 2022–Jan 2023
Data Engineer
Built personalization pipelines, search and product-discovery services. Selected website placements recorded more than 50% relative improvement in click-through rate.
Feb 2023–Jul 2024
Data Engineering Specialist
Delivered AWS lakehouse pipelines for 150+ sources within assigned domains. Built governance foundations and enabled experiment tracking through a private MLflow deployment.
Oct 2024–Present
Senior Data Engineer
Build and operate enterprise data platforms across integration, analytics, governance and production support. Lead technical delivery with three outsourced engineers and design target architecture with infrastructure and security stakeholders.
03 Selected work
Senior Data Engineer
October 2024–Present
I build and operate enterprise data platforms across integration, analytics, governance and production support. I lead technical delivery with three outsourced engineers, setting priorities, reviewing solutions and coordinating incident response.
Reconstructed lineage and moved Tableau analytics to Microsoft Fabric and Power BI. Delivered in three months.
Daily access updates for Fabric and Power BI, replacing Excel macros. Rolled out in July 2026.
Target design defined across governance, ownership and workload boundaries. Transition preparation ongoing.
Build and validate pipelines from SAP FI/RE, Salesforce, databases, APIs and files with ADF, Databricks and ADLS Gen2.
Developed naming, metadata, ownership and lifecycle standards, plus Databricks access controls. Adoption in progress.
Investigate Fabric throttling and integration-runtime bandwidth to guide capacity and scheduling decisions; coordinate incidents and vendor follow-up.
Analytics Migration Central Pattana
I led the migration from Tableau to Microsoft Fabric and Power BI, reconstructing dashboard-to-source lineage and coordinating technical delivery.
Delivered scope
Three months.
Data dictionaries and business specifications were missing, with no clear source contact or owner. I manually reconstructed dashboard-to-source lineage to establish the dependencies.
I led technical delivery and coordinated with existing Airflow workflows and Infrastructure under compute and scheduling constraints.
Direct source-database access was restricted for this migration. Source delivery used data files plus accompanying metadata files for file-level validation.
Source delivery
ADF
Zero records Skip
Skip all remaining downstream tasks for that batch.
Nonempty batch Databricks
Check row counts and columns against the accompanying metadata.
Power BI results must match the equivalent Tableau report for the same reporting period.
RLS Automation Central Pattana
I automated daily row-level security processing with ADF and Databricks, bringing together the master registry and access-review inputs.
Excel macros
Used to produce access updates.
Daily RLS updates
ADF and Databricks processing supports Microsoft Fabric and Power BI, using the registry and access-review inputs.
Users without an access assignment receive no data visibility.
If processing cannot safely produce a valid replacement, preserve the last-known-valid access state.
Target Architecture Central Pattana
I designed the Azure and Fabric target architecture, aligning responsibilities, workload boundaries and transition dependencies with infrastructure and security stakeholders.
| Design concern | My contribution |
|---|---|
| Tenant and governance boundaries | Assessed cross-tenant access and governance concerns and addressed unnecessary data duplication in the target direction. |
| Hub-and-spoke responsibilities | Aligned cloud foundation and data-platform workload responsibilities with infrastructure and security stakeholders. |
| Domain ownership | Defined a direction that distinguishes shared platform responsibilities from domain ownership of data assets. |
Target architecture defined and responsibilities aligned; assessment and transition preparation continue.