Product-to-platform ownership
Aligning product, embedded R&D, vendors, factory systems, backend teams, and cloud architecture into one system that can actually ship.
Principal Cloud Platform Engineer · St. Gallen, Switzerland
Backend-focused engineer working across Go, AWS, Terraform, microservices, and distributed systems—from production architecture to the code and operational details that make it hold up.
Engineering focus
Profile
I started building and operating systems in my teens, then learned large-scale, low-latency engineering in Beijing. I work best at the seam between product, embedded devices, backend software, cloud infrastructure, and production operations.
I joined AirVisual/IQAir in Beijing as a Senior Software Architect in 2017. After moving to Switzerland as Cloud Architect, I designed and built the global IoT foundation for new device generations. From 2021, Lead DevOps was added to my architecture remit. Today I focus on hands-on backend and platform engineering as Principal Cloud Platform Engineer.
Where I create leverage
Aligning product, embedded R&D, vendors, factory systems, backend teams, and cloud architecture into one system that can actually ship.
Building and operating Go, Node.js, and Python services with clear contracts, low latency, controlled failure modes, and safe migrations.
Treating performance, reliability, scalability, security, and cost as one engineering problem—measured in live systems, not slide decks.
Experience
IQAir is the latest chapter, not the beginning. Each role added a different layer: direct user responsibility, product engineering, scale, architecture, international alignment, and global platform ownership.
Hands-on principal engineering
Focused on backend and cloud-native platform design, modernization, infrastructure, performance investigations, security, developer tooling, and production problem-solving across global services.
Lead DevOps mandate added from 2021
Owned architecture across cloud, backend, and IoT; developed technology direction with product and R&D; aligned international teams and vendors; advised on technical risk, security, reliability, cost, and production readiness; and mentored engineers while remaining hands-on.
Architecture, backend, and engineering practices
Built and operated air-quality services, supported the move from on-premises infrastructure to AWS, and introduced code review, TDD, CI/CD, infrastructure as code, containerization, database indexing, and observability practices.
High-scale advertising, WiFi, and analytics systems
Where I learned scale directly: low-latency DSP/DMP/SSP services, APIs and captive portals used across major retail deployments, deployment automation and Nginx load balancing across hundreds of commodity servers, and technical leadership in a small team.
Commerce and operational software
Built a localized e-commerce CMS, payment and CRM integrations, Windows Mobile barcode applications, database structures, security controls, documentation, and multi-region release processes.
Started building in my teens
Ran and extended an online-game hosting operation, then worked across Linux administration and hardening, PHP/.NET, SharePoint, ASP.NET, Android, MySQL, Apache, synchronization tooling, automation, and user support.
Selected work
Representative, non-confidential summaries. The emphasis is on the engineering decisions, ownership boundaries, and production outcomes behind the technology.
01 · Flagship system · Global IoT platform
Designed and implemented the platform that allowed new IQAir device generations to bootstrap securely, connect to the closest regional broker, and integrate with the existing AirVisual backend ecosystem.
Registration, provisioning, firmware identity
Trust, configuration, nearest-region routing
Active/active MQTT connectivity worldwide
Telemetry, control, data, and existing services
System decisions
End-to-end ownership
Backend performance & migration
Rewrote a major device API from Node.js to Go and migrated it incrementally without breaking compatibility. In separate performance work, streamed database changes into Redis for a nearest-station service that moved lookups from seconds to microseconds.
Reliability, observability & FinOps
Introduced infrastructure as code, CI/CD, tracing, structured logging, alerting, error tracking, service dashboards, autoscaling, and scheduled scaling. Built the first integrations and patterns, handled MongoDB and traffic incidents, and used operational evidence to improve reliability and cost.
Scale before cloud defaults
At Goyoo, built high-scale advertising, WiFi, social, and analytics systems on commodity infrastructure. Developed a router API and captive-portal ecosystem used in KFC and Pizza Hut locations in China, with WeChat and Weibo login integrations.
Technical leadership
Worked across technology strategy, R&D direction, product and engineering alignment, architecture, technical risk, mentoring, vendor evaluation, code review, and production readiness—turning broad business goals into systems teams could implement and operate.
AI-assisted engineering
I am developing a practical framework for building applications with AI agents: written specifications, milestone-based execution, self-contained prompts, and explicit verification instead of hidden conversational context.
Current tools: OpenAI Codex / GPT-5.6 Sol · ChatGPT · DeepSeek V4 Flash
Capture constraints, specifications, decisions, interfaces, and acceptance criteria in versioned Markdown so the agent and the team share the same source of truth.
Break work into bounded, reviewable milestones with self-contained prompts, explicit scope, and a verifiable definition of done instead of one oversized generation step.
Use repeatable builds, tests, review gates, and fresh-context checks so results can be reproduced, challenged, and handed to another engineer or agent without hidden context.
How I operate
The work matters when it removes a visible constraint for a customer, teammate, or product—not when it merely adds technology.
Trace the real path, establish a baseline, and optimize the bottleneck—not the loudest theory.
Timeouts, retries, backpressure, idempotency, rollback, and degraded modes belong in the design from day one.
Architecture, code, rollout, observability, security, and cost are parts of one production responsibility.
Technical range
Technologies are grouped by how I use them, so earlier foundations and adjacent exposure are not presented as equal to current production depth.
Core today
Core today
Deep production
Deep production
Production
Production
Production
Earlier foundations
Current practice
Best role fit
Start a conversation