I'm Pieter Leek
Technical Systems Architect | Technical Ground Truth for Complex Systems | Built for Problems Without a Manual
I step into technical and organisational environments where systems stop talking, integrations stall or ownership is unclear. I map what is actually happening, find the constraint behind the symptoms and replace assumptions with evidence—so management can decide and teams can move again.
Complex Systems • OT/IT Integration • IoT Architecture • Technical Ground Truth
Where I Help
Technical architecture, diagnosis and recovery when systems, people and decisions no longer align.
Architecture Between Boardroom and Floor
Technical problems rarely live in one place. They often sit between systems, teams, priorities and decisions. I connect the technical reality with the organisational context, so decisions are based on how the environment actually works. I create overview, identify the real bottlenecks and translate complex technical situations into a direction that teams and decision-makers can act on.
Legacy, Middleware & Connectors
When machines, applications, databases and cloud platforms do not speak the same language, I design and build the layer in between: protocol translators, edge data services, API wrappers, message pipelines and practical middleware that makes information flow again.
Sensor-to-Cloud Architecture
From field sensors and edge devices to dashboards, databases and cloud services. I design practical architectures where data can be measured, transported, stored and used for research, monitoring and decision support.
Complex System Diagnosis
Something keeps breaking and nobody can pin down why — or worse, everyone has a theory and the fix never holds. I read the system as a whole: network, software, integration, data, process and the way people are actually using it. Usually the cause sits across two of those, which is why nobody found it. I trace it, explain it and help make sure it does not come back.
Technical Recovery & Go-Live Support
Go-live coming up, a project drifting, or a technical environment that has become too unclear to steer? I step in quickly, create overview, separate symptoms from causes and help move the project back to a state where delivery is possible again.
Python
JavaScript
IoT
Linux
About
I work where technology, people and decision-making meet — especially when the situation no longer fits a standard manual.
Driven by execution. I work best in situations that need rapid technical progress and pragmatic problem-solving. My focus is on creating robust architecture, restoring momentum and getting systems operational.
The bigger picture. I do not stop at the visible symptom. I follow the technical and organisational dependencies until the real constraint becomes clear. That creates the overview needed to make decisions and move forward.
A broad toolkit. My background is deliberately broad: software development, infrastructure, IoT, education, team leadership, governance and process improvement. I've built environments from hardware sensor to cloud dashboard and connected operational systems to business processes. I use the part of that toolkit the situation actually needs.
Technology and the human side. A system only works when the people around it can work with it. I move between software stacks, the shop floor and the boardroom to understand how the environment operates in practice.
Short, intense and results-driven. My engagements range from a two-week deep-dive diagnosis to a three-to-six-month recovery project. I establish what is true, repair or build what is needed, secure the quality and hand it back cleanly. I build solutions; I do not stay for maintenance.
Available for complex international project assignments. Remote-first by design; on-site when the hardware, integration or situation requires it.
The name Qman is a nod to Q from the James Bond series—the quartermaster who stays out of the frontline politics, works from his own lab, and builds exactly the custom hardware and software needed to survive the mission.
Reference Work
Amerta One — Solar-Powered Field Module for Rice Fields
Amerta One is a Qman reference project: a compact solar-powered field module that measures local salinity stress risk in rice fields, gives farmers a simple LED status indication and sends measurement data to Tirta Cloud for research, calibration and future advisory services.
The project combines the kind of work I like most: field hardware, ESP32/LoRa, power design, cloud data, practical research and a clear human purpose. It is a sensor-to-cloud system built for real environments, not just a dashboard demo.
The first prototypes are being developed for field testing, with the long-term goal of placing multiple modules in Central Java to support salinity monitoring and farmer advice.
The architecture reflects my broader way of working: connecting hardware, software, data, people and decision-making into one understandable system.
>>> Download the technical paper: Designing Defensible Industrial Systems.
Recent Deployments & Rapid Prototyping
I regularly design, build and deploy systems for real users in operational environments. This keeps my work grounded in practice: architectures have to work reliably, not just look convincing on paper.
[DEPLOYMENT_01] High-Density AI Infrastructure
Designed, orchestrated, and deployed a high-availability environment for 150+ concurrent users. Built on a stack of 30 isolated Docker containers, routed through a Caddy reverse proxy, featuring a custom Python backend with integrated AI-evaluation tools.
Infrastructure as Code, Load Balancing, AI Integration, Security.
[DEPLOYMENT_02] Automated Compliance Engine
Developed a custom data-evaluation engine that maps unstructured user inputs against complex,
formal regulatory frameworks and turns them into immediate, structured feedback.
Business Logic Automation, Data Parsing, Regulatory Compliance.
[DEPLOYMENT_03] OT/IT Hardware Integration (MQTT)
Built an edge-to-cloud bridge integrating analog hardware with modern network protocols. Used MQTT to translate digital commands from a central dashboard into physical actions via hardware relays.
IoT/OT Interoperability, Legacy-to-Cloud Bridging, Protocol Translation.
Contact
Dealing with a complex, stalled or technically unclear situation? Send me the context at pieter@qman.io or send a message on LinkedIn.
From sensor to cloud, from shop floor to boardroom.