Technical Lead Manager

Nexla is the leading Integration platform, built with AI, for AI. Nexla takes a metadata driven approach to converge diverse integrations across Data, Documents, Agents, Applications, and APIs into a single design pattern. We accelerate the development of solutions for GenAI, Analytics, and Inter-company data. Nexla makes data users and developers up to 10x more productive by delivering a true blend of no-code, low-code, and pro-code interfaces.

Leading companies including DoorDash, LinkedIn, Johnson & Johnson, and LiveRamp trust Nexla for mission-critical data. Named in the 2022, 2023, and 2024 Gartner Magic Quadrant™ for Data Integration Tools and top-rated by customers on Gartner Peer Insights, headquartered in San Mateo, California.

At Nexla, our culture is built around our core values: Have Empathy, Be Curious, Be Intellectually Honest, Achieve Excellence, and Remember to Relax. We put our customers at the heart of everything we do, foster a data-driven mindset, take ownership of our work, and believe in the power of teamwork to achieve ambitious goals.

Nexla, briefly

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, briefly

Nexla’s connector layer is what talks to everything else: over a thousand SaaS applications, databases, streams, files, and APIs, bidirectionally, each with its own schema quirks, auth scheme, rate limits, and retry semantics. You would be the most senior engineer on it, and the person four to six engineers report to, working alongside our backend, API, and UI teams. The split is roughly 80% hands-on design and code, 20% growing the team. If you are looking to step off the keyboard, this is the wrong job.

• The architecture of the connector layer. You make the calls on how we abstract a thousand systems and handle formats like JSON, Parquet, and Avro at high throughput, and you write the hard parts yourself.

• The connector roadmap. You decide what ships, what gets deprecated, and in what order, working directly with product, customer success, and support on what customers actually need.

• Reliability of what your team ships, on-call included. Fewer failures reaching customers, and better tooling so the team sees problems before customers do.

• The four to six engineers around you. Hiring, growth, and raising the technical bar, mostly through design review and pairing. Formal management runs to about a day a week.

Ninety days in: you have shipped something non-trivial to production, named the two worst parts of the current design with a proposal attached, and the team has started routing hard design questions to you before they route them upward.

A real problem you’d hit here

We have thousands of connectors, with thousands of customer pipelines running on them. Each one has to scale in two directions at once: the volume of data moving through it, and its reliability under that volume. This is not a problem you solve and close. The connector surface keeps growing, so holding both properties is a