Procurement is the single largest cost lever in manufacturing: over 50% of a physical product's cost originates with suppliers. Yet the teams managing billions in spend still run on spreadsheets, fragmented tools, and tribal knowledge.
Delvo is building Cognitive Procurement: an AI-native intelligence layer that gives strategic procurement teams the decision power they've never had. Our agents analyze suppliers, benchmark prices against real-time cost indices, and generate tailored negotiation strategies, turning weeks of manual analysis into minutes of actionable insight.
We're founded by a McKinsey venture builder who shipped production AI systems as interim CTO, a procurement excellence lead from PwC who ran 500+ supplier negotiations for industrial manufacturers, and one of the very few people in the world who combines deep procurement domain knowledge with the technical skills to build. We combine deep technical skill with the domain expertise to build something procurement teams actually trust and use.
If you want to shape how procurement works at scale, Delvo is where you can do the most important engineering work of your career.
We're looking for a Forward Deployed Engineer: a full-stack engineer who sits with our customers, understands their data inside out, and builds the features that make our AI deliver real value on it.
Enterprise procurement runs on data that lives in dozens of systems: SAP, Oracle, custom ERPs, supplier portals, commodity databases, and more spreadsheets than anyone wants to admit. None of it is clean. None of it is standardized. And our product is only as good as its ability to reason over it.
You'll be embedded in our customer engagements from day one. You'll sit in workshops with procurement teams and their IT departments, map their data landscape, figure out where the valuable signals live, and build the pipelines, analytics, and product features that make our AI agents actually work on their data. One week you're writing a data normalization pipeline for a customer's SAP export. The next you're shipping a Next.js feature that surfaces the insights to their category managers. When a procurement team sees a savings opportunity that changes a negotiation, your work made that possible, from data layer to UI.
This role is equal parts engineering and customer problem-solving. You need to be as comfortable whiteboarding a data architecture with a customer's IT lead as you are building the frontend that presents the result. If you're energized by going to a customer, figuring things out together, and coming back with something that works end-to-end, we'd love to talk.
Be at the customer, not behind a desk. You'll join customer workshops, talk to IT teams, walk through ERP configurations, and understand how procurement data actually flows through a large manufacturer. Most engineers never see this. You'll see it every week, and it'll make everything you build sharper.
Turn messy data into procurement intelligence. Enterprise data is fragmented, inconsistent, and spread across dozens of systems. Your job is to find the signal in the noise: normalize supplier master data, connect spend records to commodity indices, build analytics that surface savings opportunities no one could see before. This is where the real value of Cognitive Procurement gets created.
Build analytics that drive real decisions. The output of your work isn't a chart in a dashboard nobody checks. It's a cost benchmark that changes a negotiation. A supplier risk score that redirects a sourcing strategy. A spend analysis that reveals millions in consolidation potential. You'll see procurement teams act on what you built.
Ship features across the full stack. You won't just work on data pipelines. You'll build the product features that present insights to users: Next.js interfaces, interactive visualizations, agent-driven workflows. The line from customer data to user-facing feature runs through you.
Solve a different puzzle every time. Every customer's data landscape is different. There's no universal connector or standard schema. Getting to reliable outcomes takes fast prototyping, creative problem-solving, and the persistence to keep improving until it works. You'll build patterns that scale across customers, not one-off scripts.
Shape the product from the field. You're not just an implementation engineer. The patterns you discover across customer deployments, what data matters, what's always broken, what analytics procurement teams actually use, directly inform our product roadmap. You sit at the intersection of customer reality and product development.
We care about what you can do, not how many years you've been doing it. What matters is craft, velocity, and the ability to figure things out in front of a customer.
You should:
Be a strong full-stack engineer who's equally comfortable with data and product work. You can write a Python data pipeline in the morning and ship a Next.js feature in the afternoon. You don't see "data work" and "product work" as separate disciplines.
Be fluent in TypeScript and Python. You'll build product features in Next.js/React, write data pipelines, and work with messy datasets. SQL is second nature.
Be comfortable in front of customers. You'll sit in workshops with procurement teams and IT departments, whiteboard data architectures, ask the right questions about their systems, and come back with a plan. You don't need to be a salesperson, but you need to be someone a customer trusts technically.
Be comfortable with ambiguity and mess. Enterprise data is never clean. ERP exports have inconsistent encodings, missing fields, and undocumented schemas. You're the person who figures it out, builds a robust pipeline anyway, and documents what you learned for the next time.
Have sharp analytical instincts. You can look at a procurement dataset and spot patterns: where the spend concentration is, which categories have price anomalies, where consolidation potential hides. You think about data as a source of insight, not just as rows to move between systems.
Be genuinely interested in enterprise systems and procurement. ERP data, supplier master records, commodity indices, spend classification. If this sounds tedious to you, this isn't the role. If it sounds like a puzzle worth solving, you'll thrive.
Bonus: any hands-on experience with SAP, Oracle, or other ERP systems. Even basic exposure accelerates everything.
Bonus: experience with LLMs, embeddings, or retrieval pipelines. Understanding how AI consumes data helps you build better data infrastructure.
We value strong fundamentals and fast iteration over checkbox experience with specific tools. That said, here's what's most relevant to this role:
Data & Analytics: Python, SQL, PostgreSQL (Supabase). You'll build pipelines that ingest and normalize enterprise data, and analytical models that turn it into procurement intelligence.
Integrations: REST and SOAP APIs, file-based ingestion (CSV, XML, EDI), ERP connectors. Every customer is different, and you'll build for that reality.
Stack context: TypeScript/Next.js (frontend on Vercel), Python, Supabase/PostgreSQL. You'll work closest to the data and backend layers, but shipping features in NextJS will be part of your day-to-day.
Tooling: Git, GitHub Actions, Sentry, Vercel Analytics. We ship daily.
We're a small, fast team with large-enterprise customers and the intensity that comes with it. We work from CIC Berlin in Kreuzberg: direct collaboration, no unnecessary process.
Everyone on the team talks to customers. Everyone ships to production. The founders are technical and hands-on: Jonas (CTO) writes code daily, Darius (CPO) designs and builds product, Erik (CEO) runs customer relationships. There's no layer between you and the work that matters.
We're building a generational company in Cognitive Procurement. That means high standards, fast pace, and real ownership.
💰 Competitive salary with meaningful equity (VSOP).
🏖️ 30 days vacation.
🖥️ Equipment budget for your ideal setup.
Search for a command to run...