IAN TORRES
Bachelor of Engineering Sciences
Civil Industrial Engineer
Bachelor of Computer Science · Computer Science Engineer
Expertise
Distributed Systems & Real-Time Infrastructure
Raft consensus, gossip protocols, leader election, failure detection, binary wire protocols, pub/sub messaging, event-driven pipelines, low-latency transport, and congestion-aware backpressure. Systems designed to survive partitions and heal without intervention.
Software Engineering & Architecture
End-to-end system design from bare-metal C++ to SPA frontends. C, C++, C#, Java, TypeScript, PHP, Rust. Clean architectures with explicit boundaries, intentional dependency flow, and minimal surface area. Code that reads like a proof, not a puzzle.
Infrastructure, Data & Cloud
Database administration, server provisioning, cloud architecture, CI/CD pipelines, devops automation. SQL at scale, in-memory data structures, distributed storage, and the operational discipline that keeps production boring.
Industrial Engineering & Operations
Process optimization, operations research, decision analysis, composite metrics, supply chain logic, production line modeling. The same mathematics that stabilizes a refinery also stabilizes a software system. Same constraints, same trade-offs.
Technical Leadership & Project Governance
Full project lifecycle management, agile/scrum, hiring, team building, cross-functional coordination, CTO-level advisory. Twelve years leading technical organizations from the code up. Credible leadership means you have done the work.
Systems Thinking & Cross-Domain Analysis
Engineering principles apply everywhere, from consensus protocols to material science, from queuing theory to thermodynamics. The underlying logic does not change with the domain. The ability to reason across them is what makes novel solutions possible.
Approach
Engineering is the same language regardless of domain. A consensus protocol and a production line share the same logic: state, flow, constraints, failure modes. The mathematics that stabilizes a grid also stabilizes a distributed system.
I treat every system the same, whether software, industrial, or organizational: understand the primitives, model the edges, validate under load. Clean boundaries, explicit contracts, minimal assumptions. No speculation, no dogma.
It took fifteen years to learn this. I apply it in one.
Stack
Playground
1 / 4Contact
