I'm Hassan Kadiwal — Head of DevSecOps and Cloud Architect. I help regulated and high-growth companies replace fragile, manual infrastructure with automated, observable, audit-ready platforms across AWS, Azure, and GCP.
12.8+ years in IT — 9+ years leading DevOps and DevSecOps transformation, and 3.8 years in systems administration before that. I've led infrastructure, DBA, and security teams end to end, from core banking platforms to trading systems processing real client volume.
If it's done twice by hand, it becomes a pipeline. Manual steps are where outages and breaches start.
Identity, secrets, and network policy are built into the architecture — not bolted on before an audit.
Every system is built to be observed, alerted on, and recovered — before it becomes a 2am incident.
Architecture decisions are judged by the cost, risk, and speed they buy the business — not by novelty.
I'm Hassan Kadiwal. Since 2022 I've served as Head of DevSecOps at iDigiCloud Technologies, where I lead the DevOps, Infrastructure, DBA, and Security teams delivering scalable, secure enterprise solutions — including architecture work on a core banking platform now in its client-facing phase. Before that, I spent over five years as Team Lead, DevOps at Choice TechLab, building a trading platform from scratch to production and supporting 70+ client projects.
My background spans hybrid and multi-cloud architecture across AWS, Azure, and GCP, infrastructure automation with Terraform and Ansible, containerized platforms built on Docker, and CI/CD pipelines engineered in Jenkins and GitLab that ship safely, not just quickly. I integrate security directly into the pipeline — shift-left SAST/DAST scanning with SonarQube, secrets management with Vault, and centralized SIEM — rather than treating it as a final review step.
I also design identity and access layers, harden API surfaces behind gateways like NGINX and HAProxy, and build the monitoring stack — ELK, Grafana, Zabbix, Prometheus, and Wazuh — that tells you what's actually happening in production before a customer does.
Before any of that, I spent 3.8 years as a System Administrator managing Linux and Windows environments — which is exactly why I design for the operator who gets paged at 3am, not just the architecture diagram. Clients bring me in for one reason: they need infrastructure that holds up under real load, real attackers, and real audits.
Every engagement starts with the business problem — cost, risk, speed, or scale — and works backward to the architecture.
Tools chosen for what they need to do in production, not what's trending.
A sample of engagements and the measurable outcomes they produced.
A timeline of the programs and transformations I've led.
Representative feedback from engagement stakeholders.
Tell me about the problem you're solving — migration, security, scale, or AI infrastructure — and I'll respond within one business day with next steps.