Director of Engineering, Data Platform

Pendo

Where
Raleigh, NC
Pay
$235K a year

Posted 23 days ago· Checked live at Pendo 52 minutes ago

Stale: open 23 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Pendo asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Pendo's own hiring page 52 minutes ago.
What is the job?
Pendo's Data Platform is the backbone of everything we do. Our systems process more than 50 billion events per day, peaking at over 1 million events per second, and manage dozens of petabytes of data across several production environments. The platform powers real-time data ingestion, batch processing, and analytics at scale — and the instrumentation standards that keep our entire codebase observable.
What does it pay?
$235K a year, as the posting states.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

Pendo's Data Platform is the backbone of everything we do. Our systems process more than 50 billion events per day, peaking at over 1 million events per second, and manage dozens of petabytes of data across several production environments. The platform powers real-time data ingestion, batch processing, and analytics at scale — and the instrumentation standards that keep our entire codebase observable.

What this looks like day-to-day

  • Lead multiple engineering teams responsible for our real-time data ingestion pipeline, analytics batch job pipelines, and analytics query engine — setting technical direction and roadmap while balancing near-term delivery with long-term scalability, reliability, and cost efficiency.
  • Drive architectural decisions across storage, compute, and data modeling; know when to adopt, build, or retire technologies and make those calls with conviction and clear rationale.
  • Own instrumentation standards across the core codebase — structured logging, OpenTelemetry metrics and tracing — ensuring teams across the organization can adopt them with minimal friction and that the resulting telemetry is useful, consistent, and cost-conscious.
  • Own the cost profile of the data platform at petabyte scale: forecast infrastructure spend for new product initiatives, improve cost attribution by customer, product, feature, and team, and diagnose and resolve cost overruns quickly.
  • Partner with SRE on shared on-call responsibilities, incident response, postmortems, and reliability roadmaps; define and track SLOs for ingestion latency, query performance, and data correctness.
  • Serve as a technical authority in customer conversations on platform performance, data integrity, and reliability — translating customer needs and escalations into clear engineering priorities.
  • Hire, coach, and develop engineering managers and senior engineers; build a team culture grounded in high standards, clear communication, and continuous improvement.

Who you are

Beyond the qualifications, we hire through a specific lens. These aren't buzzwords; they're the things we'll actually look for in how you talk about your work.

You're a builder, not a maintainer.

You're most energized when there isn't a clear path yet, and you get to define it. You don't wait for direction; you identify gaps, shape solutions, and drive them forward. At Pendo, great engineering directors don't just manage delivery — they operate as technical owners, setting architectural direction, making cost and reliability tradeoffs visible before they become crises, and building teams that can operate at the same level of ambition.

You're AI-curious — genuinely.

You're not using AI tools occasionally. You're rewiring how you work around them — and you bring that same orientation to your teams. You evaluate emerging tools with sound judgment, separate meaningful shifts from hype, and guide the adoption of AI-assisted and agentic coding practices across the organization in a way that raises the bar rather than creates new risk.

Nice-to-haves

  • Experience with high-cardinality, high-volume event or telemetry data.
  • Background in multi-tenant SaaS platforms.
  • Familiarity with FinOps practices and cloud billing data, including cost allocation approaches such as tagging, labeling, and usage-based attribution.
  • Contributions to open-source projects in the data or observability ecosystem.