Technical Content Lead

Lexsi Labs is one of the leading frontier labs focusing on building aligned, interpretable and safe Superintelligence. Most of the work involves developing new methodologies for efficient alignment, interpretability, lead-strategies, and foundational tabular model research. Our mission is to make AI tools that empower researchers, engineers, and organizations to unlock AI's full potential while maintaining transparency and safety.

Our team thrives on a shared passion for cutting-edge innovation, collaboration, and a relentless drive for excellence. At Lexsi.ai, everyone contributes hands-on to our mission in a flat organizational structure that values curiosity, initiative, and exceptional performance

a Technical Content Le

re startup speed meets technical de

on.Responsibilit

• iesOwn Lexsi.ai’s technical content strategy and execution across audiences: AI engineers, data scientists, AI Researchers, SDEs, platform teams, and enterprise stakeholde
• rs.Produce high-signal technical content that engineers actually use: deep-dive blog posts, technical explainers, and benchmarks; tutorials, notebooks, guides, and reference implementations; architecture breakdowns, product narratives, and “how it works” conte
• nt.Convert internal research and product work into external-facing assets: interpretability methods, alignment approaches, evaluation methodology; ML observability, debugging workflows, auditability and governance st
• oryCreate and maintain technical and product documentation in collaboration with engineering: onboarding, SDK/API docs, integration guides, and troubleshooting playbo
• oksPartner with Product, Research, MLEs, and SDEs to: Identify adoption friction points; improve activation and “time-to-first-value” through content-driven UX clarity; ensure technical claims are precise, testable, and defensi
• bleBuild a repeatable content engine that supports user acquisition in the US and Euro
• pe:developer-first distribution (GitHub, communities, conferences); launch narratives, release notes, changelogs, and product upda
• tesSupport external visibility: co-author technical briefs/whitepapers; help prepare conference submissions, talks, demos, and workshops; publish work in open forums where appropriate (blogs, open repos, arXiv-style not

es)Qualificati

• onsStrong technical foundation in one or more of: ML / DL, MLOps, data systems, applied AI, or platform engineer
• ingDemonstrated ability to write and ship technical content that developers trust: blogs, docs, tutorials, notebooks, GitHub READMEs, research notes, or simi
• larComfortable engaging directly with engineers and researchers to extract insights and turn them into publishable asse
• ts.Hands-on familiarity with modern ML tooling and workflows (examples: PyTorch/TensorFlow, pipelines, eval stacks, model debugging, observabilit
• y).Able to communicate complex ideas clearly without diluting technical correctne
• ss.High ownership mindset: can run end-to-end from idea → draft → code/examples → review → publish → distribution → iterati

on.Nice to H

• aveExperience writing content related to interpretability, alignment, evaluation, model monitoring, or ML governan
• ce.Ability to create strong diagrams and technical visuals (system diagrams, evaluation flows, architecture map
• s).Prior open-source contributions or experience maintaining developer-facing tool
• ingExperience collaborating with growth/product on activation and funnel improvements (PLG motio
• n).Experience speaking at meetups/conferences or running worksho

ps.What Success Looks Like (First 6–12 Mont

• hs)Lexsi.ai content becomes

  a trusted refere

  nce in engineer communities (shared in Slack groups, GitHub issues, forum
• s).Clear improvement in activation metrics driven by docs/tutorials (faster time-to-first-valu
• e).A consistent, recognizable technical voice across docs, launches, and thought leadersh
• ip.Multiple “flagship” pieces of content that reliably pull qualified developers into trying the produ

ct.How to Ap

plyPlease se

• nd:2–3 examples of technical writing you’ve published (or private samples),
• andGitHub/code samples if relevant, p
• lusa short note on what kinds of technical content you love creating (and for who