1

Fetch Delivery Jobs in Kentucky (NOW HIRING)

We are building Maven to deliver better, cheaper support, for both end users and agents. With ... It's how our agents fetch a customer's order history from Shopify, update a ticket in Zendesk, look ...

$100K - $122K/yr

... deliver the most advanced solutions of tomorrow across every market segment of chip design ... Define verification strategies for challenging behaviors such as instruction fetch, branch ...

Showing results 21-22

Fetch Delivery information

See Kentucky salary details

$11

$40

$79

How much do fetch delivery jobs pay per hour?

As of Sep 12, 2026, the average hourly pay for fetch delivery in Kentucky is $40.26, according to ZipRecruiter salary data. Most workers in this role earn between $17.74 and $52.60 per hour, depending on experience, location, and employer.

What is a Fetch Delivery driver?

Fetch Delivery drivers are independent contractors who deliver packages to residents of apartment communities. Fetch Delivery partners with property managers to handle all package deliveries, ensuring secure and convenient drop-offs. Drivers pick up packages from Fetch warehouses and deliver them directly to residents’ doors on a flexible schedule. It's a gig-style job that allows drivers to choose their hours and earn money based on the number of deliveries they complete.

What are the key skills and qualifications needed to thrive as a Fetch Delivery driver?

To thrive as a Fetch Delivery driver, you need a valid driver's license, a clean driving record, and strong time-management skills. Familiarity with GPS navigation apps, delivery management systems, and sometimes a reliable personal vehicle are typically required. Excellent customer service, communication, and problem-solving abilities help drivers stand out in this role. These skills ensure timely, accurate deliveries and positive interactions with customers, which are crucial for operational efficiency and customer satisfaction.

What are some common challenges Fetch Delivery drivers face during their shifts, and how can they effectively manage them?

Fetch Delivery drivers often encounter challenges such as navigating apartment complexes, managing multiple deliveries within tight timeframes, and communicating with residents who may not be available for direct handoff. To succeed, drivers should familiarize themselves with property layouts, use the Fetch app to track delivery instructions, and proactively communicate with the support team for any access issues. Staying organized and planning routes efficiently can also help drivers maintain timely deliveries and ensure a positive experience for residents.

What is the difference between Fetch Delivery vs Courier Driver?

AspectFetch DeliveryCourier Driver
CredentialsValid driver’s license, delivery app trainingValid driver’s license, courier certification (if required)
Work EnvironmentUrban and suburban areas, delivery vehiclesUrban, suburban, and sometimes rural areas, delivery vehicles or bikes
Industry UsageFood, retail, e-commerce deliveriesParcel, document, and food deliveries

Fetch Delivery and Courier Driver roles both involve transportation and delivery tasks, often requiring similar licenses and working in comparable environments. The main difference lies in the companies and services they represent; Fetch Delivery typically refers to specific food or retail delivery platforms, while courier drivers may work for various courier companies or independently. Both roles are essential in the logistics industry and often overlap in skills and work settings.

How to become a Fetch Delivery driver?

To become a Fetch Delivery driver, applicants typically need to meet age requirements, have a valid driver's license, and pass a background check. Prior experience with delivery or navigation skills can be beneficial, and drivers usually use a smartphone app to receive and complete delivery orders. Availability during flexible hours is often preferred.

Is Fetch Delivery a good job?

Fetch Delivery is a gig-based delivery job where workers use their own vehicles to deliver food or packages. It offers flexible hours and the opportunity to earn based on completed deliveries, but income can vary depending on demand and location. Workers typically need a valid driver’s license, insurance, and a reliable vehicle.

What are popular job titles related to Fetch Delivery jobs in Kentucky?

For Fetch Delivery jobs in Kentucky, the most frequently searched job titles are:

What job categories do people searching Fetch Delivery jobs in Kentucky look for?

The top searched job categories for Fetch Delivery jobs in Kentucky are:

Infographic showing various Fetch Delivery job openings in Kentucky as of August 2026, with employment types broken down into 1% As Needed, 63% Full Time, 26% Part Time, 7% Temporary, and 3% Contract. Highlights an 91% Physical, 2% Hybrid, and 7% Remote job distribution, with an average salary of $83,745 per year, or $40.3 per hour.

Group Product Manager, Integrations

On-site

Other

Posted 11 days ago


Key responsibilities

  • Define and prioritize the roadmap for Maven's integration portfolio, including which systems to support and at what depth.

  • Own the development and scaling of the underlying integration platform, including tooling, frameworks, and patterns to enable faster deployment and customer extensibility.

  • Engage with enterprise customers to understand their system stacks and translate those requirements into integration features and actions.


Job description

Maven AGI is an enterprise AI platform on a mission to unleash business artificial general intelligence (AGI), starting with customer service. Founded in July 2023 by executives from HubSpot, Google and Stripe, Maven builds conversational AI agents capable of delivering accurate, autonomous support that delights customers at scale.

Our platform unifies fragmented systems, integrates knowledge and personalization sources, and enables intelligent actions - all without costly system changes. We’re laying the foundation for a future where our technology handles complex tasks, allowing people to focus on what they do best: creative problem-solving, relationship building, and delivering exceptional customer experiences.

We’ve started by reimagining the enterprise customer experience with a support use case. We believe that today’s support experience is broken: slow and painful for customers, and expensive and human capital intensive for companies.

We are building Maven to deliver better, cheaper support, for both end users and agents. With recent advancements in Generative AI, it is now possible to deliver delightful customer experiences at a fraction of today’s cost.

Team:

Maven has assembled a world-class team from Google, Meta, Amazon, and Stripe, and is supported by executives & Advisors from OpenAI, Google, HubSpot, and Stripe.

The Role

Maven's agents are only as good as the systems they can reach. Every enterprise customer runs on a different stack of CRMs, ticketing systems, knowledge bases, commerce platforms, identity providers, and internal tools. Our agents have to read from all of them, take action inside them, and do it reliably.

The Integrations layer is what makes that possible. It's how our agents fetch a customer's order history from Shopify, update a ticket in Zendesk, look up an account in Salesforce, pull a knowledge article from Confluence, and trigger a refund inside a homegrown billing system.

We're hiring a Group PM to own this layer end-to-end. You'll define what Maven integrates with, how deep those integrations go, and how we scale the platform so that adding the next integrations doesn't require building each one by hand. You'll own the roadmap, the P&L, and the direct relationships with the enterprise customers whose stacks we live inside.

What you'll own:
  • Roadmap and prioritization for Maven's integration portfolio. Which systems we support, at what depth, and in what order.

  • The underlying integration platform. Tooling, frameworks, and patterns that let Maven ship new integrations faster over time and let customers extend the platform themselves.

  • Depth versus breadth tradeoffs. A read-only Salesforce connector is not the same product as a full read/write integration with custom object support, and you'll own how we make those calls.

  • Enterprise customer engagement. You'll be in the room when customers describe their stack, and you'll translate that into integration requirements engineering can build against.

  • Actions and tool use. Maven's agents don't just retrieve information, they take actions inside customer systems. You'll own how those actions are defined, tested, and made safe at enterprise scale.

  • Partner ecosystem strategy. Which platforms warrant a formal partnership, which stay in our own build queue, and how we approach marketplace listings on Salesforce AppExchange, Zendesk Marketplace, and similar channels.

  • Cross-functional partnership with GTM to convert integration depth into enterprise wins, and with customer success to turn integration issues into product improvements rather than support tickets.

Who you are:
  • 8+ years of product management experience, with meaningful time on integrations, APIs, developer platforms, or iPaaS products.

  • You’ve built and shipped integration products before. You understand the difference between a connector, an integration platform, and an actions framework, and you can explain the difference,

  • Direct experience with the systems Maven agents touch: CRMs (Salesforce, HubSpot), ticketing (Zendesk, ServiceNow, Freshdesk), knowledge bases (Confluence, Notion, Guru), commerce (Shopify, Stripe), and identity (Okta, Auth0). You don't need all of them, but you've worked inside several.

  • Fluent in the technical building blocks: REST and GraphQL APIs, webhooks, OAuth, rate limits, event streams, and the failure modes that come with each.

  • You’ve operated in both startup and scaled environments and know when to build in-house versus when to buy or partner.

  • You extract requirements from messy customer conversations and turn them into PRDs. Non-negotiable.

  • You're a problem solver, not a project manager. You’ve been the person deciding what to build and why.

  • Real enthusiasm for AI, LLMs, and autonomous agents, and a clear point of view on how integrations change when the caller is an agent instead of a human developer.

  • Strong communication across audiences. Technical enough to hold your own with engineering, but clear enough to translate for enterprise stakeholders and GTM.

Location:

Hybrid in Boston, San Francisco, or New York.

Compensation:

Base salary of $190,000 to $230,000, plus bonus, comprehensive benefits, and equity in a well-funded, high-growth AI company.

Why Maven:
  • You own a P&L, not a backlog. Your product line has customers, revenue, and a roadmap you define.

  • Integrations at Maven is not a services function or a \"nice to have.\" It's the difference between an agent that can talk about a customer's problem and an agent that can actually solve it.

  • Maven has the strongest product on the market for complex enterprise AI use cases. Our conversion rate from first conversation to close speaks for itself.

  • A growing roster of enterprise brands is betting on Maven for their AI agent strategy.

  • This isn't a proof of concept! We're deploying AI agents into production for enterprise customers today.

Join us in changing the face of enterprise customer support!

#J-18808-Ljbffr