Hermes Wiki
Works/Profile/PersonalBrand/positioning_statement

Positioning Statement

Draft — first pass synthesized from professional_profile, needs Mihir's own refinement pass. Everything else in PersonalBrand should trace back to whatever this settles into, so it's worth getting right before building on top of it.

One-liner

Network/infra engineer who went deep on production-scale observability and automation, then built the platform and AI-engineering breadth to operate a level up — targeting Senior/Staff/Principal or Platform Engineering roles, not locked to Network long-term.

Elevator pitch (30 seconds)

I run production Network Automation, Observability, and Certification systems at RBC — tools that correlate change requests to automated pre/post-checks across thousands of devices, map live app-to-app dependencies, and let people query network state in natural language. That depth taught me how to build things that have to be right at scale, with zero tolerance for false positives. Outside that vertical I've built the broader platform toolkit that depth demands — AWS, Kubernetes/Terraform, CI/CD security tooling, agentic AI (LangChain/LangGraph/MCP) — applied as real production features, not side projects. I think of myself like a contractor: I go wherever the job is. Right now that's Fintech, Capital Markets, BigTech, Healthcare, e-commerce, or entertainment — any domain that rewards system-design maturity and platform thinking over staying in one niche.

What NOT to lead with

  • Don't lead with "Network engineer" alone — it undersells the platform/AI breadth and invites domain-locking. Network is where the depth proof lives, not the whole pitch.
  • Don't lead with tool lists — tech_stack already has extensive tool detail; the pitch is what was built with them, not the inventory.

Evidence this statement is already true, not aspirational

The breadth claim above isn't just self-description — fullstackfusions.com/blogs already has 30 published posts spanning exactly that range (RAG architecture across industries, LLM observability, harness engineering, AWS agent-native infra, MCP internals) alongside the Network-domain production work. See proof_artifacts for the full breakdown — this statement should stay grounded in what that page can actually back up.

Hermes Wiki