Connecting requirement framing, system design, platform modules, and operating outcomes.
Architect Profile
From backend systems to Digital Twins and AIoT field integration, I design systems that can actually run
I did not grow out of one framework or one role. My path moved from backend systems into platforms, Digital Twins, and field integration, which is why I now work best as an architect connecting abstraction to operation.
That is the biggest difference in how I work. I am not only concerned with a stack or an isolated codebase. I care about how a system is framed, deployed, adopted, and eventually turned into an operating product.
Backend → Platform → ArchitectAIoT / Digital TwinsOT ↔ IT / Product / Ops
Profile SnapshotEN
AIoT / Digital Twins Solution Architect
Most useful in environments where devices, software, and operations must align.
Make it run first, then grow it into a reusable and scalable platform.
Technology should support workflow, decisions, business models, and maintainability.
Journey
From backend engineering to Digital Twins and AIoT platform architecture, my scope kept moving toward system ownership
My foundation came from Node.js microservices, high-concurrency APIs, and Kubernetes / Docker deployment at scale, building a strong sense of system boundaries and reliability.
Working on Digital Twins, DCIM, and smart factory cases pulled me into the relationship between Twin models, visualization, event streams, and operational decision-making.
Now my focus is on requirement framing, platform modules, OT / IT integration, commercialization paths, and cross-project reuse so technology becomes part of an operating product.
How I Work
My design process starts by making systems deployable, then making them grow
This is not just a technical delivery pipeline. It is a path that aligns requirements, architecture, platform design, and operations.
Frame the problem
Clarify scenario, stakeholders, data sources, and the operating problem that actually matters.
Design the system
Define data flow, module boundaries, event structure, and future extensibility instead of just features.
Build the platform
Turn IoT, Twins, SaaS, workflow, and permissions into a usable product structure.
Integrate the field
Bridge devices, gateways, private networks, OT / IT systems, and the real environment of use.
Scale operations
Make the system reusable, evolvable, and strong enough to support business models and multi-project growth.
What I Believe
A few principles that define how I think about systems and products
Technology should land in the real world and create operational value.
Platformization is worth more than one-off delivery.
AIoT is fundamentally about data loops and decisions, not device counts.
Good architecture shapes cost, speed, operations, and business models at the same time.
Selected Depth
Depth matters more than breadth when it reaches the core of the system
Where I Go Deep
AIoT SystemsDigital Twins PlatformsOT / IT IntegrationPlatform ArchitectureSmart Building / PropTechSmart Factory / Manufacturing
Why Teams Bring Me In
When requirements need to become a clear system blueprintWhen a project needs to become a reusable platformWhen devices, gateways, and cloud products must connect cleanlyWhen technical design must align with operations and business models
Work Together
If you need someone who can think beyond implementation and move a system toward real operations, we should talk
The role I fit best is not patching one feature, but bringing clarity to uncertain requirements and complex systems so they can become deployable products.