Director, Technical Marketing

Databricks · San Francisco, California · Marketing · listed October 8, 2026

The shape of it

Seniority
Director
Experience asked
3–10 years
Where
Not stated
Stated pay
$223,400 – $307,100 USD
Requirements listed
7
Length
1,203 words

In the posting’s own words

As the Director of Technical Marketing at Databricks, you will lead and scale the team responsible for explaining Databricks products, and what you can do with them, at scale to technical buyers and practitioners (from data engineers, data scientists, and ML engineers to solutions architects, platform teams, security engineers, and application developers). You will own the strategy and execution of technical content in written and video form, demos, workshops, launch storytelling, and outbound evangelism that drives technical mindshare, consideration, product adoption, and ultimately pipeline. In the era of agentic marketing and AEO/GEO, your team will increasingly produce content designed to educate both humans and agents alike. You will also play an outsized role in programming the technical content for key Databricks events, such as the Data + AI Summit and Data + AI World Tour, among others. Reporting to the SVP of Product & Solutions Marketing, you will manage a team of 6+ Technical Marketing Managers (growing) and serve as the connective tissue between Product, Product Marketing, Field Engineering, and the broader technical community.

What it asks for · 7

  • 10+ years of experience in technical marketing, developer relations, solutions engineering, field engineering, or a related technical field in enterprise software / SaaS / cloud.
  • 3+ years of people management experience, with a track record of hiring, developing, and retaining high-performing technical teams.
  • Deep technical fluency in data, AI/ML, and cloud platforms, comfortable building demos and engaging credibly with data engineers, data scientists, solutions architects, and other technical practitioners across the data + AI ecosystem.
  • Demonstrated outbound evangelism skills, including a visible external presence through conference speaking, technical blogging, YouTube/video content, or social media thought leadership.
  • Experience owning technical content strategy for major product launches and flagship events (e.g., user conferences, world tours).
  • Strong cross-functional influence with a proven ability to partner with Product Management, Product Marketing, Field Engineering, and Sales to align on priorities and deliver integrated GTM.
  • Excellent written and verbal communication skills, with the ability to translate complex technical concepts into compelling narratives for multiple audiences.

Also a plus

  • Experience with data platforms, lakehouse architectures, Apache Spark, or related open-source data technologies.
  • Experience building or scaling a YouTube channel, podcast, or technical content program for practitioner audiences.
  • Familiarity with GEO / AI answer engine optimization strategies.
  • Experience with technical community building, creator programs, or influencer engagement across practitioner audiences.
  • Track record of building technical content that drives measurable pipeline and product adoption.

Tools and skills named

Data
  • Databricks10×
  • Spark2×
  • Data warehouse
Go to market
  • Outbound4×
  • Go-to-market
  • SaaS
Models & research
  • Machine learning2×
Security & compliance
  • Security2×
Product & design
  • Product management
Ways of working
  • Cross-functional

Words the posting leans on

  • technical30×
  • content18×
  • data14×
  • product14×
  • marketing9×
  • technical content9×
  • engine6×
  • experience6×
  • practitioner6×
  • solutions6×
  • building5×
  • engineers5×
  • scale5×
  • tmm5×
  • youtube5×
  • events4×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Databricks

every open role at Databricks →

How this page was made

An automated read of a public job posting, fetched October 8, 2026 and last changed by Databricks on October 8, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.