← Back to Propaganda

Careers / Open role

Developer Experience Lead

Make technical products easier to build with—for humans and the agents working alongside them.

Employment type

Contractor Full Time

Location

Remote, with overlap w/ Eastern Time (ET)

Reports to

Gayatri, Partner, Product & Engineering

About Propaganda

Propaganda is a creative and technical studio based in New York City. We think of the internet as our playground. We embed with teams, learn their products fast, and ship work that people can actually use.

We've worked on developer documentation and launch support for Whop, and on Flynet's developer portal and onboarding for Blackbird. You will move between clients and learn new products quickly, so curiosity and good judgment matter as much as knowing any one stack.

The role

This role is for someone who can make technical products easier to build with. At Propaganda, that can mean restructuring an API reference, debugging a quickstart, building a demo, shaping a launch, or helping run a builder program. To put it bluntly, the work could change weekly, if not daily.

It also increasingly means writing for two audiences. Plenty of integrations are now built by an agent with a human supervising, which puts new weight on machine-readable specs, well-described tools, and errors that say what to do next. You should either think this way already or be visibly excited to.

It is a senior IC role with a lot of range. You will own the feedback cycle and speak with developers rather than work from secondhand feedback. You'll have direct access to work with the team that owns the fix and help ship it.

What you'll do

  • Own developer documentation end to end: quickstarts, API references, conceptual guides, tutorials, migration guides, and changelogs.
  • Write and maintain runnable code samples, SDK snippets, and starter repositories across the languages our clients' developers use. If the example does not run, it does not ship.
  • Establish the docs system, including information architecture, style standards, review workflow, release gates, and a docs-as-code pipeline.
  • Own docs discoverability end to end: information architecture, on-site search, technical SEO, and redirect strategy during restructures.
  • Make documentation legible to the AI coding assistants developers now use as a first stop—clean markdown sources, semantic heading structure, self-contained code blocks, and machine-readable entry points.
  • Work with engineering and product to ship documentation alongside releases.
  • Audit the onboarding path from signup and credentials to a working call and real product value. Use product data, developer feedback, and regular dogfooding to find where people get stuck.
  • Turn friction into a prioritized set of docs and product fixes. Advocate for better API design, error messages, authentication flows, and SDK ergonomics when documentation cannot solve the underlying problem.
  • Build demo apps, sandboxes, and reference implementations that developers can learn from and client teams can reuse.
  • Partner with product marketing on technical launches and integration announcements. Support sales and solutions teams with POCs, technical collateral, and direct answers to common objections.

What we're looking for

  • You have owned documentation or developer experience for an API, SDK, platform, infrastructure product, or another technical product.
  • You are technical enough to build and debug integrations, review example code, create small demo apps, and contribute to docs tooling.
  • You write clear technical prose and know when the right answer is a code sample, diagram, reference page, or short explanation.
  • You understand developer onboarding, including authentication, credentials, SDKs, CLIs, webhooks, error handling, and versioning.
  • You can combine product data with qualitative feedback and explain what should change next.
  • You work well with engineers and product managers, ask precise questions, and push back without creating theater.
  • You can learn unfamiliar products quickly, move between client contexts, and leave behind systems other people can maintain.
  • You can show examples of work such as docs systems, quickstarts, SDK samples, starter repositories, demo apps, or onboarding improvements.

Nice to have

  • Experience with multi-language SDKs, OpenAPI, docs-as-code tooling, CI, or automated sample testing.
  • Experience in solutions engineering, technical product marketing, or developer education.
  • Experience with developer infrastructure, AI, fintech, or crypto.