Skip to content
Together AI

Technical Marketing Engineer

San Francisco; San FranciscoUnited States
Marketing
POSTED 15 SEPTVERIFIED 1H AGO
Apply Ask
Role
57 days opentrue age
Past the 49d median close
Posted 15 Sept · n=12
Pay
$175k–$285kno pay posted
$161k$285k
Market p25–p75
$161k–$240k
Together AI p25–p75
$175k–$285kn=5
SF Bay Area · n=2154 · 365d to 12 Nov
CompanyTogether AI →
80open roles
Opened · 30d
+4
Closed · 30d
−3
10d of snapshots · 30d window
Market
37,808open · Software engineering
Opened · 7d
+3,71910% of open
All software engineering
75,513open
All tracked boards · live 12 Nov · n=37,808

About The Role

Most of what makes Together AI so valuable for customers is invisible from the outside. Optimizing kernels, scheduling, quantization, speculative decoding, and more create an industry-leading platform for inference and post-training at scale. As a technical marketing engineer, you are the conduit between the engineering and research work and the developers who should know about it. You go deep with product, engineering, research, and CX to learn the platform at the level of nuanced technical detail, then decide which details matter to an AI builder and build content that makes them care.

This is a creator role. You are a technical storyteller. You'll produce social-native posts, technical blogs, performance benchmarks, demo and explainer videos, and thought leadership, all aimed at one outcome: building Together’s credibility with developers. You'll also own our technical communities on X, YouTube, Discord, Linkedin and the engagement metrics for developer content company-wide, including amplifying the work of engineers and researchers who publish under their own names.

Responsibilities

External

  • Partner with product, engineering, DevRel, research, and CX to learn new capabilities in technical depth, then extract the most meaningful aspects for a developer audience.
  • Create the content strategy based on deep understanding of our company’s differentiation and marries that with an understanding of the content that would resonate.
  • Build technical content across formats: blogs, videos, benchmark reports, podcasts, and short-form posts that drive engagement with developers and preference for Together.
  • Monitor real-time news and announcements related to AI infrastructure and lead timely responses working with product and engineering
  • Replies to social media comments, bringing expert understanding of the technology
  • Own Together's presence in technical communities, primarily X, Discord, LinkedIn, and Youtube. Track engagement metrics, what lands, what doesn't, and adjust.
  • Drive amplification of engineering and research work across social channels.
  • Be the heartbeat of the Together AI technical community - understanding the developers and researchers who follow us and enabling them to be successful
  • Experiment and test new ideas to see what resonates with the community
  • While the role involved mainly online engagement (80%), there is an aspect of translating their deep understanding to deliver highly engaging in-person meet ups and events (20%) in collaboration with Events/ DevRel teams

Internal

  • Be the bridge between research and engineering with the field team
  • Deploy models, benchmark new capabilities (e.g. the compiler, speculative decoding) across models and workloads, and turn results into practical field guidance: when to use it, when not to, and what to expect.
  • Enable SAs and FDEs on every launch. Create technical briefs and run sessions covering how it works, where it sits in the inference serving stack, how to deploy it for customers
  • Go to implementation depth for FDEs: which workload and model shapes a capability fits, how to configure it, and how to implement it.
  • Build the technical foundations curriculum for field onboarding
  • Create field-ready technical assets: reference architectures, benchmark summaries, POC guidance, competitive technical comparisons, and FAQs for deep customer conversations.
  • Close the loop. Bring what SAs and FDEs learn from POCs and deployments, and customer questions from sales calls (with PMM), back into internal and external content.

Requirements

  • 3+ years of product, technical or developer marketing
  • Either hands-on GPU/AI infrastructure experience or a portfolio of in-depth technical content for engineers (links required).
  • Experience creating content for infrastructure or technical systems, not user-facing SaaS applications. You've explained how something works under the hood.
  • Loves building social community presence, posting, engaging, monitoring with technical audiences, with experience managing channels
  • Technical depth sufficient to hold a real conversation with engineers about architecture, performance, and tradeoffs, and to write about it accurately (partnering with SMEs).
Source · Together AIFirst seen 2 Nov2 editsOriginal ↗