Job Title: Agentic AI API Developer
Work Mode: Onsite - Cincinnati OH
Duration: Long Term
Role Summary:
We are seeking an Agentic AI API Developer to build and integrate enterprise-grade APIs and orchestration services that enable agentic commerce experiences and third party commerce integrations. You will work in a fast-moving pod model (2 pizza team) and deliver production-ready integration capabilities that accelerate partner POCs and real-world deployments.
Key Responsibilities
API Integration Development (Core)
- Design and implement scalable secure RESTful APIs for commerce and agentic workflows (external/partner-ready).
- Build API orchestration/composition layers that integrate multiple downstream services/APIs into cohesive business flows.
- Apply an API-first development approach and support API lifecycle practices needed for broad consumption.
- Implement and validate authentication/authorization patterns appropriate for enterprise third-party use.
Agentic Enablement & MCP
- Develop or integrate MCP server interfaces (or equivalent shim layers) that front APIs to enable agentic interactions.
- Support agentic workflow integration (tool invocation patterns orchestration flows and integration contracts).
Third Party / Partner Integrations
- Implement and operationalize 3rd-party integrations (e.g. large partner ecosystems) using robust integration patterns (avoid brittle point-to-point).
- Contribute to rapid partner POCs and transitions from POC production with quality and repeatability.
Quality Engineering for Agentic/AI-Assisted Development
- Produce production-grade code including AI-assisted development practices where applicable.
- Implement testing strategies suitable for AI/agentic variability (i.e. testing beyond purely deterministic outputs).
Collaboration & Delivery
- Work embedded with incubation/acceleration teams initially and then help evolve pod delivery as scope becomes clear.
- Operate effectively in a pod model with fast onboarding iterative staffing and rapid delivery cycles.
Required Skills & Experience
Must Have
- Strong backend engineering experience building RESTful APIs and integration services at scale.
- Proven expertise in authentication and authorization for API access.
- Hands-on experience with API orchestration/composition patterns across multiple services.
- Experience delivering production-ready software (not just prototypes).
- MCP Server experience (explicitly expected for this pod context).
- Working knowledge of agentic workflows and how agents consume tools/APIs.
Nice to Have (Highly Relevant)
- Experience integrating with major partner ecosystems and third-party commerce platforms.
- Familiarity with Googles UCP / universal commerce platform concepts and/or analogous partner protocols mentioned in the pod ask.
- Experience with AI-assisted engineering tools in enterprise environments (e.g. Copilot-style tooling referenced in discussion).
Job Title: Agentic AI API Developer Work Mode: Onsite - Cincinnati OH Duration: Long Term Role Summary: We are seeking an Agentic AI API Developer to build and integrate enterprise-grade APIs and orchestration services that enable agentic commerce experiences and third party commerce integra...
Job Title: Agentic AI API Developer
Work Mode: Onsite - Cincinnati OH
Duration: Long Term
Role Summary:
We are seeking an Agentic AI API Developer to build and integrate enterprise-grade APIs and orchestration services that enable agentic commerce experiences and third party commerce integrations. You will work in a fast-moving pod model (2 pizza team) and deliver production-ready integration capabilities that accelerate partner POCs and real-world deployments.
Key Responsibilities
API Integration Development (Core)
- Design and implement scalable secure RESTful APIs for commerce and agentic workflows (external/partner-ready).
- Build API orchestration/composition layers that integrate multiple downstream services/APIs into cohesive business flows.
- Apply an API-first development approach and support API lifecycle practices needed for broad consumption.
- Implement and validate authentication/authorization patterns appropriate for enterprise third-party use.
Agentic Enablement & MCP
- Develop or integrate MCP server interfaces (or equivalent shim layers) that front APIs to enable agentic interactions.
- Support agentic workflow integration (tool invocation patterns orchestration flows and integration contracts).
Third Party / Partner Integrations
- Implement and operationalize 3rd-party integrations (e.g. large partner ecosystems) using robust integration patterns (avoid brittle point-to-point).
- Contribute to rapid partner POCs and transitions from POC production with quality and repeatability.
Quality Engineering for Agentic/AI-Assisted Development
- Produce production-grade code including AI-assisted development practices where applicable.
- Implement testing strategies suitable for AI/agentic variability (i.e. testing beyond purely deterministic outputs).
Collaboration & Delivery
- Work embedded with incubation/acceleration teams initially and then help evolve pod delivery as scope becomes clear.
- Operate effectively in a pod model with fast onboarding iterative staffing and rapid delivery cycles.
Required Skills & Experience
Must Have
- Strong backend engineering experience building RESTful APIs and integration services at scale.
- Proven expertise in authentication and authorization for API access.
- Hands-on experience with API orchestration/composition patterns across multiple services.
- Experience delivering production-ready software (not just prototypes).
- MCP Server experience (explicitly expected for this pod context).
- Working knowledge of agentic workflows and how agents consume tools/APIs.
Nice to Have (Highly Relevant)
- Experience integrating with major partner ecosystems and third-party commerce platforms.
- Familiarity with Googles UCP / universal commerce platform concepts and/or analogous partner protocols mentioned in the pod ask.
- Experience with AI-assisted engineering tools in enterprise environments (e.g. Copilot-style tooling referenced in discussion).
View more
View less