Product Manager - API Integration
Job Description
Prior backend development experience is a strong advantage; deep familiarity with inventory management or warehouse operations is a significant plus. What you will own: • API product strategy: Define the roadmap for IndoFast's internal and partner-facing APIs — versioning, deprecation policy, rate limiting, SLA tiers, and developer experience. • Integration design: Architect integration patterns between ERP, WMS, swap-station telemetry, CRM, and mobile apps using REST/GraphQL APIs and middleware (MuleSoft / Azure Integration Services).
• Inventory & warehouse API layer: Own the product definition for APIs that power real-time stoc visibility, inward/outward flows, bin management, serialised inventory tracking (battery packs, EV units), and reconciliation between physical and system inventory. • API governance: Establish and enforce API design standards (OpenAPI/Swagger specs, naming conventions, error codes, pagination, idempotency), conduct design reviews, and maintain a central API catalogue. • Stakeholder bridge: Translate business requirements from operations, finance, and partner teams into precise technical specifications for backend engineers.
Review PRDs with engineering and hold them to contract. • Reliability & observability: Define SLAs, work with DevOps/SRE on alerting, logging, and incident response for production API failures. • Partner & third-party integrations: Manage API onboarding for logistics partners, OEM data feeds, GSTN/IRP (e-invoicing), payment gateways, and IndianOil/SMPL upstream systems.
Must-have requirements: • 5–8 years of experience in product management, technical program management, or backend engineering, with at least 3 years in an API-facing or integration-heavy role. • Has designed or consumed REST APIs at production scale — can read and write OpenAPI specs, understand HTTP semantics (idempotency, pagination, status codes, auth flows). • Solid understanding of backend concepts: microservices, message queues (Kafka / RabbitMQ / Azure Service Bus), async patterns, database transactions, and eventual consistency.
• Prior experience as a backend developer (Java, Python, Node.js, or similar) is a strong differentiator — someone who has written production code and understands what engineering trade-offs feel like. • Working knowledge of inventory management or warehouse operations — stock movements, bin/location tracking, GRN, putaway, pick-pack-ship, cycle counting, or WMS platforms. • Experience writing detailed API specifications, integration runbooks, or technical PRDs that engineers can build from without back-and-forth.
• Comfortable with Postman, Swagger UI, or equivalent for API testing and validation. Good to have: • Experience with WMS platforms (SAP EWM, Oracle WMS, GreenfieldWMS, or custom-built systems). • Exposure to IoT / telemetry API patterns — time-series data, device registration, event streaming.
• Familiarity with GraphQL and API gateway products (Apigee, AWS API Gateway, Kong, Azure APIM). • Knowledge of EV, energy, or mobility domain — battery swap logistics, vehicle telematics, or charging infrastructure. • Experience with developer portal tooling (Stoplight, Redoc, Confluence-based API docs).
• Agile/Scrum delivery experience; comfortable running sprints with backend engineering pods.
