About Pinecone
Pinecone is the leading vector database for building accurate and performant AI applications at scale in production. Pinecone's mission is to make AI knowledgeable. More than 9000 customers across various industries have shipped AI applications faster and more confidently with Pinecone's developer-friendly technology. Pinecone is based in New York and raised $138M in funding from Andreessen Horowitz, ICONIQ, Menlo Ventures, and Wing Venture Capital.
Pinecone is looking for a full-stack engineer to bring a new level of visibility, control, and trust to our product experiences. From cost metrics and spend alerts to interactive usage dashboards, we’re looking for a product-focused engineer who will deliver transparent and accurate insights to our customers.
As a member of the Experience Platform team, you’ll have direct ownership over the billing, management, and authentication interfaces that we need our customers to understand and trust. You understand the responsibility and care this type of work requires, while also moving quickly to match Pinecone’s rapid growth. You’ll do this by working closely with product, design, and other engineering teams to identify user and system needs and build the right thing, at the right abstraction level, at the right time.
Shape our product experience. Influence the rollout of products, propose and build new features, and advocate for experiences that will build confidence with our customers.
Ship end-to-end experiences across API, SDK, and web. You'll own the full surface, from the HTTP layer to the UI, and you'll make calls across all of it.
Own integrations with billing systems and vendor APIs, designing for resiliency against outages, schema drift, and inconsistent data.
Create observable, auditable systems with monitoring, alerting, and verification mechanisms that give leadership and customers confidence in the numbers.
Bring AI-assisted development practices to the team — use the best tools available and help establish patterns that let a small team move at a pace that shouldn't be possible.
Partner with finance, product, and design to translate business requirements into scalable technical solutions, and push back when the abstraction level isn't right.
Engineers at Pinecone operate with high autonomy. You'll be an active partner in setting strategy on APIs, interfaces, observability, and our product experience — not just executing on a roadmap. We care more about how you think and how you work than whether your resume checks every box. In exchange, we’ll make sure you’re set up for success with mentorship and technical guidance.
You should have:
At least 2 years of software engineering experience
A bias toward automation and leverage — you reach for systems and tooling before you reach for elbow grease
Hands-on experience shipping with AI coding tools (Claude Code, Cursor, Copilot, or similar) as a genuine part of your workflow
Proven ability to design and deliver APIs for a rapidly scaling product surface
Proficiency building web interfaces with React or similar
Experience with at least one major cloud provider (AWS, GCP, Azure)
Strong intuition for what makes APIs easy for both humans and agents to use correctly
Bonus points for:
Experience at a SaaS company with usage-based or consumption pricing models
Experience building billing-specific features, such as usage dashboards or cost reporting
Strong familiarity with a compiled language like Rust, Go, or Java
Experience integrating with third-party financial APIs and building defensively against inconsistent or delayed data
Experience with queueing and streaming technologies such as Kafka, Kinesis, or Pub/Sub
Perks & Benefits:
Comprehensive health coverage including medical, dental, vision, and mental health resources
401(k) Plan
Equity award
Flexible time off
Paid parental leave
WFH Equipment Stipend
All qualified applicants will receive considerations for employment without regard to race, color, religion, sex, age, disability, marital status, familial status, sexual orientation, pregnancy, gender identity, gender expression, national origin, ancestry, citizenship status, veteran status, and any other legally protected status under federal, state, or local anti-discrimination laws.
Pinecone provides a fully-managed vector database that allows businesses to store and search through data embeddings for AI applications. The product works by converting data into mathematical vectors, enabling fast similarity searches that provide relevant context to Generative-AI models like chatbots. Unlike many competitors, Pinecone handles all infrastructure maintenance, service monitoring, and algorithm troubleshooting, allowing developers to scale their usage without managing the underlying systems. The company's goal is to make it easy for organizations of all sizes to build and scale applications that can accurately interpret and retrieve information from large datasets.
Company Size
51-200
Company Stage
Series B
Total Funding
$138M
Headquarters
New York City, New York
Founded
2019
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
BYOC: Pinecone vector database managed service expands to AWS, Azure & GCP. Chris Mellor STORAGE EDITOR Blocks & Files editor Published thu 24 Sep 2026 // 12:12 UTC Vector database-as-a-Service supplier Pinecone has released its proprietary cloud lock by adding support for the AWS, Azure and Google clouds, and is aiming to head fully into the on-prem world. A vector database stores the mathematically transformed tokens generated by a user's natural language input to a large language model (LLM). Pinecone provides a managed vector database service to store, access and use these vectors. Its bring-your-own-cloud (BYOC) strategy has a customer's vector data - the data plane - living in their public cloud area but still managed through the Pinecone control plane for operations such as resource lifecycle, authentication, and service health. This control plane does not store or process customer content or request payloads. The public cloud data plane stores, processes, and serves customer data and knowledge. AI agents and applications connect directly to this for read and write operations. The only data shared with Pinecone are anonymized operational metrics and traces for monitoring and support. With BYOC, the data plane runs inside the customer's selected cloud account and region, including those beyond where Pinecone's standard service is available. Vectors, documents, metadata, and request payloads remain within the customer-controlled boundary. Customers retain access to Pinecone's support and engineering teams for troubleshooting, incident response, and ongoing operational guidance. Pinecone does not require SSH, VPN, inbound network access, or a standing cross-account IAM role to manage the service. Upgrades, scaling actions, and maintenance work are retrieved using an outbound call from the Pinecone control plane and executed locally. This allows Pinecone to manage the database without a persistent access path into the customer environment. BYOC works alongside SSO, RBAC, SCIM + SAML, audit logging, encryption, and private-networking controls available with Pinecone's Enterprise plan so customers can have complete confidence in ensuring their proprietary knowledge is secure. Customer admin teams use the same Pinecone APIs, SDKs, and control plane workflows across the BYOC and standard deployments. This means each workload can use the deployment model that fits its data governance and access requirements without creating a separate development path. Toyota Motor North America (TMNA) was one of Pinecone's first BYOC customers to deploy it in production. TMNA used Pinecone to this way with its decades of proprietary manufacturing knowledge kept secure inside Toyota's environment and not exposed to Pinecone's own managed service. Kordel France, Head of AI Engineering at Toyota Motor North America, said: "Decades of manufacturing know-how live in our documentation, and that institutional knowledge is one of the most valuable assets we have. It also happens to be complex - highly structured engineering data sitting alongside unstructured process documents, across a lot of formats and a lot of different access patterns. Pinecone BYOC runs inside our own environment, so that knowledge never leaves our boundary and is served only to models we've already vetted." Pinecone wants to go further, and work in a customer's on-premises environment. Its developing a fully self-managed option for air-gapped and highly restricted networks where both the control plane and data plane will run inside the customer environment. Bootnote. Pinecone is following its competitors' examples. Zilliz Cloud documents regions on all three providers and offers both SaaS and BYOC (Bring Your Own Cloud) on AWS, Google Cloud, and Microsoft Azure. Feature availability can vary by region and plan (for example on-demand compute is not equally available everywhere). Weaviate can be self-hosted, with deployment on Kubernetes on AWS (EKS), Azure (AKS), or GCP (GKE). The managed Weaviate Shared Cloud is available on GCP and AWS (AWS Shared Cloud went GA in US East and Europe Frankfurt). Dedicated/enterprise deployments are described as covering AWS, GCP, and Azure. There is also an Azure Marketplace listing for running Weaviate in a customer Azure tenant. Qdrant supports AWS, Azure, and GCP or your own Hybrid Cloud infrastructure.
Pinecone BYOC: trusted AI knowledge in the customer cloud. Sep 23, 2026 Today, Pinecone is announcing the general availability of Pinecone Bring Your Own Cloud (BYOC) on AWS, Google Cloud, and Azure, bringing Pinecone's trusted AI knowledge platform to where enterprise data needs to live. AI becomes transformative when it works with a company's proprietary knowledge. Customer context, policies, and operational history allows its agents to make decisions and carry out work using expertise the business has built over years. Organizations have spent years controlling where sensitive knowledge lives and who can reach it. Providing access to it typically meant managing knowledge infrastructure ranging from inference, document parsing, and vector databases. Platform teams shouldered the burden of tuning and maintaining the system, including keeping retrieval quality and performance stable across a diverse set of AI workloads. With BYOC, customer data and the knowledge derived from it remain in the customer's account, while Pinecone manages the platform operations. This means teams can bring sensitive AI workloads to production without taking on the complexity of operating knowledge infrastructure themselves. The APIs and interfaces remain the same as the managed service, providing organizations with the flexibility to select the right deployment model for each workload based on its security, connectivity, and operational requirements. Keeping proprietary knowledge inside the customer cloud. Pinecone's platform architecture separates the systems that manage the service from those that store and process customer data. * Control Plane: Handles management operations such as resource lifecycle, authentication, and service health. It does not store or process customer content or request payloads. * Data Plane: Stores, processes, and serves customer data and knowledge. AI agents and applications connect directly to this for read and write operations. The only data shared with Pinecone are anonymized operational metrics and traces for monitoring and support. With BYOC, the data plane runs inside the customer's selected cloud account and region, including those beyond where Pinecone's standard service is available. Vectors, documents, metadata, and request payloads remain within the customer-controlled boundary. Zero-access BYOC model. Pinecone does not require SSH, VPN, inbound network access, or a standing cross-account IAM role to manage the service. Upgrades, scaling actions, and maintenance work are retrieved using an outbound call from the Pinecone control plane and executed locally. This pull-based mechanism allows Pinecone to manage the database without a persistent access path into the customer environment. Additionally, BYOC works alongside SSO, RBAC, SCIM + SAML, audit logging, encryption, and private-networking controls available with Pinecone's Enterprise plan so customers can have complete confidence in ensuring their proprietary knowledge is secure. Keep the managed Pinecone experience. In addition to Pinecone handling upgrades, scaling, maintenance, and service health monitoring, customers retain access to Pinecone's support and engineering teams for troubleshooting, incident response, and ongoing operational guidance. Teams use the same Pinecone APIs, SDKs, and control plane workflows across the BYOC and standard deployments. This means each workload can use the deployment model that fits its data governance and access requirements without creating a separate development path. Toyota brings manufacturing knowledge to AI within its environment. Toyota Motor North America (TMNA) was one of Pinecone's first BYOC customers. TMNA used Pinecone to ground AI applications with decades of proprietary manufacturing knowledge while keeping that knowledge secure inside Toyota's environment. "Decades of engineering expertise and R&D knowledge live across our technical documentation, specifications, test data, and research. R&D GPT, backed by Pinecone's vector database, helps bring that institutional knowledge together, giving our engineers a faster and more intuitive way to discover, connect, and apply the information they need while maintaining the security, governance, and access controls our enterprise requires. It helps our teams spend less time searching for knowledge and more time applying it to accelerate innovation." - Ravi Chandu Ummadisetti, Head of Agentic AI & Product Research, Toyota Motor North America "A vast amount of our manufacturing know-how lives in our documentation, and that institutional knowledge is one of the most valuable assets we have. It also happens to be complex - highly structured engineering data sitting alongside unstructured process documents, across a lot of formats and a lot of different access patterns. Pinecone BYOC runs inside our own environment, so that knowledge never leaves our boundary and is served only to models we've already vetted. It handles that complexity at the scale our operations demand, with the enterprise security and governance controls our teams require. A critical requirement for how our team can use AI with confidence." - Kordel France, Head of AI Engineering, Toyota Motor North America Bringing trusted AI knowledge to more environments. Its mission is to make AI knowledgeable, everywhere. BYOC extends Pinecone's trusted AI knowledge platform to customer-controlled cloud environments today, and its work continues beyond BYOC. Pinecone is developing a fully self-managed option for air-gapped and highly restricted networks where both the control plane and data plane will run inside the customer environment. Reach out if you're interested in shaping the security and deployment requirements of a self-managed Pinecone offering. Get started. Talk with your Pinecone account team to review your requirements and plan your BYOC deployment, or contact Pinecone to get connected with Pinecone.
Zilliz launches Milvus vector lakebase. Chris Mellor STORAGE EDITOR Blocks & Files editor Published thu 16 Jul 2026 // 18:17 UTC Zilliz has announced its v3.0 update to Milvus, its open-source vector database adding lake-native data access and a more expressive retrieval engine to developers building production AI applications. Lake-native means the data's primary home is open formats on cloud object storage (a data lake) - not loaded into a separate database. Zilliz has been talking about its Vector Lakebase technology since June, public preview start time, when CEO and founder Charles Xie said it was "one data foundation where the same vectors can serve a production query, anchor a discovery session, and power a multi-petabyte training-data pipeline - without copies, migration, or a parallel stack." Unified lake-native storage, Zilliz says, means one storage layer, on object storage, that serves both low-latency online search and large-scale analytics over the same files. James Luan, Zilliz Co-founder and CTO, said: "Milvus 3.0 brings production retrieval closer to where data already lives and gives developers a more expressive engine for modern AI applications. That same foundation powers Zilliz Vector Lakebase, where we extend it with the elasticity, operational simplicity, and enterprise capabilities required to manage AI data at scale." Vector databases store vector embeddings, the mathematically calculated numeric representations of various dimensions of a word or image. Vector databases provide vector search facilities to find similar vectors. Items with similar values on the same dimensions have vectors that are closer to the stores ones than dissimilar items. Zilliz says Milvus is the most popular open-source vector database world-wide, with more than 10,000 organizations using it for RAG, search, recommendations, and AI agents in production. It has also accumulated more than 100 million Docker pulls. Zilliz says production AI systems commonly maintain one copy of data for real-time retrieval and another for offline processing. Moving data between the two introduces additional storage overhead, lengthy exports, synchronization pipelines, and operational complexity. Milvus 3.0 enables organizations to build and serve production-grade indexes over vector data that remains in object storage and open data formats. It also moves more query and retrieval operations into the engine, expanding Milvus beyond traditional nearest-neighbor search to support richer ranking, aggregation, sparse search, and multi-vector retrieval. V3.0 features; * External Collections define Milvus collections over data stored in Lance, Iceberg, Parquet, or Vortex. Milvus builds vector, full-text, JSON, and scalar indexes over the data and exposes them through the same APIs as native collections - without copying the source data into Milvus. Incremental synchronization keeps indexes current as the underlying dataset changes. * Loon, the new manifest-based storage engine in Milvus 3.0, is designed to substantially reduce the read amplification associated with low-latency point access on object storage. It uses Vortex, an open and Arrow-compatible columnar format, as its default storage format. * Snapshots create point-in-time, read-only views of live collections at minimal incremental storage cost. Offline jobs such as evaluation, deduplication, and backfill validation can run against a stable dataset while production writes continue. * A new Spark connector exposes Milvus as a Spark DataSource V2, allowing Spark, Databricks, and EMR pipelines to read from and write to Milvus as part of standard batch workflows. Milvus 3.0 also introduces vector-native batch operators for tasks including deduplication and clustering. Top-K vector search means finding the K most conceptually similar items to a query item, using mathematical distance rather than exact keyword matching. "K" is a number such as 5, 10 or 20. Top-K searches don't scale well as they measure distances between vectors across an entire dataset. The more vectors and dimensions in the dataset the longer the search takes. Luan said: "Production applications rarely stop at returning the nearest vectors. They need to sort, group, build facets, and retrieve across multiple representations of the same entity. Milvus 3.0 moves more of that work into the engine while redesigning storage for efficient, low-latency access on object storage." Milvus 3.0 expands search retrieval beyond traditional top-K vector search to include; * Server-side sorting and aggregation, together with faceted search, allow applications to combine semantic relevance with attributes such as freshness, rating, price, category, tenant, and content source. Operations that previously required over-fetching data and processing it in application code can now execute directly within the Milvus engine. * StructList introduces native multi-vector retrieval for documents, images, and other entities represented by more than one vector. A document can retain vectors for multiple chunks, an image can retain vectors for multiple visual patches, and a product can retain several multimodal representations under a single entity and metadata record. StructList also supports late-interaction retrieval models such as ColBERT and ColPali. * Milvus 3.0 strengthens sparse and hybrid retrieval with an optimized sparse index that is approximately 3 times smaller while achieving comparable recall in internal testing. * Enhancements also include SINDI for learned-sparse vectors, server-side MinHash generation, nullable vector fields, custom dictionaries for full-text search, and broader support for Faiss-compatible indexes. This release develops the shared technical foundation behind both open-source Milvus and Zilliz Cloud. Developers can deploy Milvus independently, while Zilliz Cloud builds on the Milvus core to deliver a fully-managed Vector Lakebase spanning real-time serving, interactive discovery, batch analytics, and AI data operations. Zilliz has given competitors Pinecone, Qdrant and Weaviate something to think about. All four are looking to lower search times. Qdrant introduced faster indexing, 3-way clusters for instant failover, and audit logging for compliance. In April. Pinecone announced precompiled vector sets and a composable retriever in May to speed AI agent searches. They appear to be assuming that, by providing better vector-based search facilities, they can prosper while competing with multi-model databases such as Regatta, SingleStore, SurrealDB and others. The vector-only suppliers do partner upstream with analytic lakehouse suppliers such as Snowflake and Databricks, but partnering with other database suppliers might be difficult because of database core architecture and storage engine difficulties. It will be interesting to see if one or more of the vector-only database suppliers starts adding/developing support for other database model types, such as structured, graph, document and time-series data. Availability. Milvus 3.0 is available under the Apache 2.0 license and remains a graduated LF AI & Data project. It can be deployed on Kubernetes or Docker, including in air-gapped environments, and supports S3-compatible object storage, Google Cloud Storage, and Azure Blob Storage. The release is available initially through the Python, Go, and Node.js SDKs, with Java support planned shortly after release. Developers can read the release notes, follow the quickstart, and access the source code on GitHub. They can also join the Milvus community or speak with project maintainers through Milvus Office Hours. For organizations that prefer a managed platform, Zilliz Cloud incorporates Milvus 3.0 as its core indexing and retrieval engine and extends it into a fully managed Vector Lakebase. Zilliz Cloud adds elastic compute, interactive discovery, batch analytics, shared indexing, enterprise security and governance, and automated operations across a single copy of AI data. Bootnote. External Collection builds real vector, full-text, JSON, and scalar indexes over lake-resident data and Loon removes the read amplification that made object storage impractical for low-latency point lookups. External Collection does not copy data. It is read-only and zero-copy: Milvus maps fields from your existing Lance, Iceberg, Parquet, or Vortex data and builds indexes over it in place. The files stay in your lake under your governance; incremental sync picks up changes.
Database vendors are positioning themselves as a solution to escalating AI costs as major providers shift towards usage-based billing. Companies like Pinecone and Tiger Data claim they can reduce expenses by minimising calls to AI models and managing workloads from developer agents. Pinecone has launched Nexus, a knowledge engine that structures and contextualises business data in advance, preventing agents from repeatedly rediscovering information and burning through tokens. Tiger Data's Ghost platform offers instant PostgreSQL databases with usage-based pricing, charging by compute-hours rather than database count. According to IDC research, 79% of organisations are investing significantly in agentic AI. However, analysts note that established database vendors like Snowflake, Oracle and Microsoft are absorbing similar capabilities, creating uncertainty over whether specialists or platforms will dominate this emerging market.
Pinecone has announced an integration between Pinecone Nexus and Microsoft OneLake at Microsoft Build, enabling AI agents to access enterprise data more efficiently. The integration eliminates manual data imports by connecting directly to OneLake, where organisations using Microsoft Fabric have unified their documents, tables and Power BI models. Nexus builds task-specific "artifacts" from data in advance, rather than requiring agents to retrieve and assemble information at runtime. Agents query these artifacts using KnowQL, a purpose-built query language. Early results show a 95% reduction in frontier LLM token usage, 30x faster task execution and completion rates above 90%. The system maintains role-based access controls and provides cited responses traceable to source data. Early access to Pinecone Nexus with OneLake integration is now available.