{
  "_README": "Facts here come from Mihir's CV (Aug 2026). House style: no em dashes; no ampersand in anything rendered in the display serif (Fraunces uses a swash ampersand, write 'and'); refer to the company as Ploytech or nimbus Cloud and never by product name; describe the functions led rather than how many people are in them.",

  "name": "Mihir Sheth",
  "shortName": "Mihir",
  "role": "Head of Engineering",
  "company": "nimbus Cloud",
  "companyUrl": "https://www.nimbus.cloud/",
  "location": "Melbourne, Australia",
  "availability": "Open to advisory work, speaking and mentoring conversations",

  "headlines": ["Engineering Teams", "Cloud Platforms", "Secure Systems", "Quality Practices", "Delivery Pipelines"],

  "tagline": "I lead the engineering functions that turn strategy into secure, well-tested software in production.",

  "summary": "Head of Engineering at nimbus Cloud, leading software development, quality engineering and CloudOps. Fifteen years from QA analyst to senior technology leadership, with SOC 2 and ISO 27001 behind me and a remit covering cloud architecture, delivery, security operations, endpoint management and AI in the software lifecycle.",

  "bio": [
    "I am a senior engineering leader in Melbourne. As Head of Engineering at nimbus Cloud I lead the software development, quality engineering and CloudOps functions, and I own the technology strategy, the delivery roadmap and the operational risk that comes with running a platform customers depend on every day.",
    "The remit is broader than any one discipline. It covers software development and quality engineering, cloud architecture and infrastructure as code, security operations including our SOC 2 and ISO 27001 programs, endpoint and identity management built on Intune, and vendor negotiation. Most recently I designed and built our AI capability for the software development lifecycle, which is my own work rather than a vendor product we switched on.",
    "I came up through quality, which is unusual for someone in this seat and is the single biggest influence on how I lead. I started as a QA analyst in 2011 testing ERP and point of sale systems, moved into test management, then into DevOps and platform engineering, and then into leadership. Fifteen years of watching software fail in every way it can fail teaches you that quality, security and reliability are not phases you add at the end. They are properties you design in, or you do not get them at all.",
    "I have also spent most of that time on one platform. I ran QA and then DevOps for the business when it traded as Ploytech, left for two years at MYOB, and came back after the restructure into nimbus Cloud to lead the whole engineering function. Roughly eight years on the same system, seen from three different altitudes, which is a rare thing to be able to say and it shows up in every architecture decision I make.",
    "That background is also why I care so much about feedback loops. Every good engineering organisation I have worked in was really just a machine for shortening the distance between an idea and honest signal about whether it worked. Most of my best work has been widening that machine: automating the manual, making the invisible measurable, and giving teams the paved road and the authority to ship without asking permission.",
    "I hold a Master of Information Technology from Swinburne University of Technology and a Bachelor of Computer Application from Bhavnagar University. Outside work you will find me tinkering with home automation, reading more about distributed systems than is strictly healthy, and mentoring engineers making the same jump from doing to leading."
  ],

  "email": "mihir.p.sheth@gmail.com",
  "resumeUrl": "",

  "//portrait": "portraitUrl is the resting state. portraitHoverUrl cross-fades in on hover and is only downloaded on devices that have a pointer. Set portraitHoverUrl to an empty string to turn the effect off. Regenerate both with scripts/make-portrait.ps1.",
  "portraitUrl": "/img/mihir-portrait.jpg",
  "portraitHoverUrl": "/img/mihir-portrait-colour.jpg",

  "socials": [
    { "label": "LinkedIn",     "url": "https://www.linkedin.com/in/mihirpsheth/", "icon": "linkedin", "primary": true },
    { "label": "nimbus Cloud", "url": "https://www.nimbus.cloud/",                "icon": "cloud", "me": false },
    { "label": "Email",        "url": "mailto:mihir.p.sheth@gmail.com",           "icon": "mail" }
  ],

  "ticker": [
    "Azure", "AWS", "Terraform", "Ansible", "Kubernetes", "Docker",
    "ARM Templates", "PowerShell", ".NET Core", "Blazor", "Azure DevOps", "Jenkins",
    "Microsoft Intune", "M365", "SOC 2", "ISO 27001",
    "Grafana", "Datadog", "ELK", "AI in the SDLC", "Team Leadership"
  ],

  "metrics": [
    { "label": "Years in engineering",  "value": 15,  "suffix": "+",  "caption": "QA analyst in 2011 to Head of Engineering" },
    { "label": "Functions led",         "value": 4,   "suffix": "",   "caption": "Development, QA, CloudOps and security operations" },
    { "label": "Databases automated",   "value": 300, "suffix": "k+", "caption": "Manual Azure SQL operations eliminated" },
    { "label": "Release cycle time",    "value": 50,  "prefix": "-", "suffix": "%", "caption": "Through automated test frameworks" },
    { "label": "Years on one platform", "value": 8,   "suffix": "+",  "caption": "Ploytech then nimbus Cloud, QA to Head of Engineering" }
  ],

  "expertise": [
    {
      "title": "Engineering Leadership",
      "icon": "users",
      "description": "Leading software development, quality engineering and CloudOps as one function, and owning the strategy and the risk that come with it.",
      "points": ["Function design across dev, QA and ops", "Technology strategy and roadmaps", "Vendor negotiation and IT operations", "Agile delivery and technical debt"]
    },
    {
      "title": "Cloud and Platform",
      "icon": "cloud",
      "description": "Azure and AWS platforms built as code, deployed automatically and measured continuously.",
      "points": ["Infrastructure as code", "Automated cloud deployment", "Monitoring, alerting and SLA reporting", "Resilience and failover design"]
    },
    {
      "title": "Quality Engineering",
      "icon": "check-circle",
      "description": "Where I started, and still the discipline I judge an engineering organisation by.",
      "points": ["Test strategy and automation frameworks", "Regression coverage at scale", "Release confidence", "Quality embedded in delivery teams"]
    },
    {
      "title": "Security and Compliance",
      "icon": "lock",
      "description": "SOC 2 and ISO 27001 delivered as engineering work rather than as a documentation exercise.",
      "points": ["SOC 2 and ISO 27001 programs", "Risk management", "IT policy and procedure", "Audit evidence and readiness"]
    },
    {
      "title": "Identity and Endpoint",
      "icon": "shield",
      "description": "Device and identity governance established on Intune, so compliance is provable rather than assumed.",
      "points": ["Microsoft Intune and MDM", "Group Policy and Active Directory", "M365 administration", "Endpoint compliance posture"]
    },
    {
      "title": "AI in the SDLC",
      "icon": "sparkle",
      "description": "Establishing where AI earns its place in how we build software, and where it does not.",
      "points": ["Assisted development rollout", "Usage policy and guardrails", "Review and test augmentation", "Measuring real impact"]
    }
  ],

  "certifications": [
    { "name": "Microsoft Azure Fundamentals (AZ-900)", "issuer": "Microsoft", "year": "", "url": "" },
    { "name": "ISTQB Certified Tester, Foundation Level", "issuer": "ISTQB", "year": "", "url": "" },
    { "name": "Certificate III in Business", "issuer": "", "year": "", "url": "" }
  ],

  "testimonials": []
}