Product Manager, Bay Area
Nexla · San Mateo, California, United States ·
- Work mode
- Remote
- Category
- Product
- Experience
- 4+ years
- Visa sponsorship
- Yes
- Company size
- 51-200
- Salary
- USD 150,000 – 180,000 / year
Nexla · San Mateo, California, United States ·
Nexla is the data layer for enterprise AI. We give AI apps and agents the connectivity, context, and governance to work across more than 1,000 enterprise systems in real time, and we process over a trillion records a month doing it. DoorDash, LinkedIn, Johnson & Johnson, Instacart, and LiveRamp run mission-critical data on us. Honorable Mention in the Gartner Magic Quadrant™ for Data Integration Tools, and top-rated by customers on Gartner Peer Insights four years running. Founded 2016, remote-first, headquartered in San Mateo.
Our values are short and we actually use them: Have Empathy. Be Curious. Be Intellectually Honest. Achieve Excellence. Remember to Relax.
Role
The future of enterprise software is increasingly AI-native, conversational, agent-driven, and deeply integrated into enterprise systems. We are looking for a technical, customer-first product leader with a strong operational mindset and a founder-like mentality for ownership, urgency, and problem solving. This is not a traditional PRD-driven product management role.
At Nexla, product innovation is deeply collaborative and tightly connected to engineering, customer workflows, and rapid iteration cycles. Product thinking comes from across the organization: engineering leaders, tech leads, Solutions Engineers, FDEs, customer teams, and leadership. The role of Product Management at Nexla is to operate as the connective layer between leadership’s product vision and execution across teams.
You will help translate strategic product direction into coordinated execution by:
This role is ideal for someone who thrives in ambiguity, enjoys technical products, communicates exceptionally well, and understands how modern AI-native product organizations operate.
Key Responsibilities
You will work closely with the CEO, engineering leadership, EMs, tech leads, Solutions Engineers, FDEs, design, GTM, marketing, DevRel, and customer teams to improve product execution and organizational alignment.
Your responsibilities include:
Qualifications
Compensation
Compensation for this role will be determined by overall skills, experience, and location. The salary range for a US based Product Manager will be $150,000 - $180,000 USD. The package will also include benefits such as Medical, Dental, and Vision, 401k, and flexible PTO.
A few large companies - DoorDash, SentinelOne, Johnson & Johnson, LinkedIn, Amex, Integrity Marketing, among them use Nexla for data integration. Connectors, runtime, transformations, scheduling, the parts of the stack where data has to move between systems reliably.
The reason this is an interesting moment to join is what the agent shift is doing to the category. Data integration used to mean "land this data in that warehouse so a human can look at it." That product is mature. What it's becoming is closer to "an agent asks a business question, and the platform figures out which data and what code and which APIs add up to a real answer." That's a much bigger problem, and most of the architecture for it hasn't been built yet by anyone.
A concrete example. A revenue team wants to ask "which enterprise customers are showing renewal risk" and get a real answer through whatever agent or app they work in. Today there is no clean way to answer that question, it requires CRM, usage, support, and billing data joined in org-specific ways, and the calling agent can't just invoke a tool that returns the right answer unless someone first establishes whether the underlying data is even capable of producing one.
That is the system we are building. A probe agent investigates the data plane whether the right fields are populated, whether freshness is adequate, whether the joins exist, whether credentials cover the required scope and returns a grounded feasibility answer. Where there are gaps, Express.dev composes the pipelines to close them. The capability is then exposed as an MCP server: "renewal risk" as a curated product, with the business logic correct and the query semantics described well enough that the calling agent uses it as intended. The MCP Gateway governs which agents can call which capabilities, with the policies, audit, and observability an enterprise control plane requires.
The bet is that ten years of connector work, an enterprise customer base, and a runtime that already moves real volume are the right foundation to define this layer from.