REQ.ROUTE 00 // SYSTEM_OPERATOR

Abhinav Kumar

“Everyone points a camera at the agent. I build what the agent stands on.”

Product Manager specializing in AI Integration & Agentic Orchestration. Architecting resilient context protocols, semantic runtime buses, and high-throughput evaluation systems for enterprise platforms.

◎ Focus: Agentic Orchestration ▣ Platform: IBM webMethods ▲ Alum: IIM Ahmedabad

/ABOUT // OPERATING_PRINCIPLE

System resilience precedes model intelligence. If the infrastructure sways, the agent fails.

I view artificial intelligence not as a standalone user interface feature, but as a complex distributed system challenge. Modern enterprise AI initiatives rarely fail because a language model lacks reasoning capability — they fail because orchestration, deterministic schema verification, context propagation, and runtime governance are missing.

Across a decade spanning hands-on software development, enterprise integration architecture, full-time strategic management at IIM Ahmedabad, and product leadership at IBM webMethods, I have specialized in turning raw engineering capability into reliable enterprise platforms.

Current role

Product Manager @ IBM

Core domain

Hybrid Integration & AI

Previous architecture

Arrow / Infineon Tech Lead

Strategy foundation

MBA, IIM Ahmedabad

/FOCUS // ATTENTION_MAP

Where I spend my attention

  1. req.route 01

    Agentic AI, held up by real infrastructure

    The agent gets the headline. I care about the governed APIs and data pathways underneath it — the part that decides whether the agent can be trusted with production work.

  2. req.route 02

    Enterprise integration & iPaaS

    Hybrid integration across on-prem and cloud, B2B and MFT, and the unglamorous plumbing that keeps large organizations running without anyone noticing it’s there.

  3. req.route 03

    API management & governance

    Designing for the moment an API stops being an internal convenience and becomes a contract — versioned, secured, observable, and safe to build a business on.

  4. req.route 04

    Digital government & data exchange

    Public-sector integration platforms — the quiet infrastructure that lets national systems share verified data across agencies without duplicating it everywhere.

  5. req.route 05

    Enterprise architecture

    Systems thinking applied to messy organizations — legacy estates, acquired subsidiaries, and the politics of who owns which data.

  6. req.route 06

    Product management for platforms

    Roadmapping for a product whose users are other builders — where the real deliverable is leverage, not a feature.

/WORK // CURRENTLY

The work

IBM · Bengaluru

Present

Product Manager, AI Integration

Working on IBM webMethods Hybrid Integration and API Connect — the layer that lets enterprises connect systems, govern APIs, and extend that same discipline to AI agents. Focused on turning “the AI agent worked in the demo” into “the AI agent is trusted with production traffic.”

  • webMethods
  • API Connect
  • Hybrid Integration
  • Agentic AI

IIM Ahmedabad

MBA

Business on top of systems instinct

Business fundamentals layered on an engineering instinct for how systems actually behave — the combination that ended up defining how I approach platform product work.

/WRITING // FIELD_NOTES

Ideas I keep coming back to

Notes on integration, platforms, and what “AI-ready” actually requires of an enterprise underneath the surface.

  • #AgenticAI · #Integration

    The agent gets the credit. The integration fabric does the work.

    Most of the systems now enabling “AI achievements” — governed data exchanges, secure APIs, shared service fabrics — were built years before this model cycle. The agent is the visible layer on infrastructure that already had to earn enterprise trust the hard way.

  • #iPaaS · #EnterpriseArchitecture

    Operational efficiency is a feature, not a footnote

    Cleaner interfaces, saner runtime key management, automatic cleanup of stale instances — the unglamorous releases usually determine whether a platform team wants to keep using your product.

  • #APIManagement · #DigitalGovernment

    What public-sector integration gets right

    Systems built for cross-agency data exchange are forced to solve governance, consent, and interoperability before they’re allowed to scale. Enterprises building AI agents are running into the same requirements — later, and under more pressure.

/CONTACT // OPEN_CHANNEL

Open to conversations on integration, platforms, and where enterprise AI is actually headed.

Best reached on LinkedIn — that’s where most of these conversations start anyway.

LinkedIn /in/linkabhinav ↗