Sr. Developer Advocate, Open Source — Omnigent

Databricks · San Francisco, California · Product · listed August 14, 2026

The shape of it

Seniority
Senior
Experience asked
5+ years
Where
Not stated
Stated pay
$149,200 – $205,150 USD
Requirements listed
11
Length
1,227 words

In the posting’s own words

Are you a Developer Advocate who thrives in the spotlight, loves presenting and hosting events, and is genuinely hands-on with agentic developer tooling — the kind of person who has already wired up three coding agents and has opinions about what breaks?

What it asks for · 11

  • 5+ years of combined experience as a developer advocate and in a hands-on technical role — software engineer, ML engineer, or solutions architect.
  • Professional experience actually building software, and current hands-on experience with agentic developer tooling and coding agents.
  • Strong Python and TypeScript skills, and comfort at the command line and in other people's codebases.
  • Demonstrated experience contributing to open source projects and working in the open — issues, pull requests, reviews, and release processes.
  • Subject matter knowledge of agent architecture, orchestration, sandboxing, and the practical problems of running agents safely and affordably.
  • Experience growing a contributor community, not just a user base.
  • Active participation and recognized leadership in open source community forums, chats, and meetups — measured by what the community builds with your help, not by follower count.
  • A public portfolio of technical work: repositories, tutorials, talks, or sustained community contributions.
  • Exceptional communication skills, with a talent for articulating complex concepts through writing, teaching, video, and public speaking.
  • Deep empathy for developer needs, with the ability to craft engaging experiences across tutorials, sample projects, and community platforms.
  • Adept at collaborating with cross-functional stakeholders to align community initiatives with product objectives.

What the job covers

  • Own medium-to-large advocacy projects end-to-end for Omnigent, from scoping through delivery.
  • Grow the Omnigent contributor community: lower the barrier to a first contribution, review and triage in the open, and help new maintainers take on real responsibility.
  • Drive external adoption by showing developers how to integrate Omnigent into their existing agent stacks and their own products — including stacks that have nothing to do with Databricks.
  • Create practical templates, sample repositories, and reference implementations that developers can clone, fork, and ship.
  • Create high-quality educational content — videos, tutorials, courseware, and blog posts — covering harness composition, contextual policies, sandboxing, and cost controls, and reuse each core asset across formats.
  • Drive awareness and adoption of Omnigent through speaking engagements at industry events, conferences, and meetups.
  • Act as a trusted advisor between the community and our engineering team, and influence roadmap discussions with what you learn.
  • Support developers where they already are — GitHub issues, Discord, Slack, Stack Overflow, and Reddit — and keep a real pulse on what's blocking them.
  • Mentor and unblock less-experienced advocates in content, demos, and public speaking.

Tools and skills named

Data
  • Databricks5×
  • Spark2×
Languages
  • Python
  • TypeScript
Models & research
  • Machine learning2×
Ways of working
  • Cross-functional
  • Slack
Go to market
  • Solutions architecture
Product & design
  • Roadmap

Words the posting leans on

  • developer17×
  • community12×
  • omnigent9×
  • agents8×
  • data7×
  • projects7×
  • advocate6×
  • experience6×
  • open source6×
  • create5×
  • building4×
  • contributor4×
  • practitioners4×
  • program4×
  • stacks4×
  • adoption3×

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 August 25, 2026 and last changed by Databricks on August 18, 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.