Senior Technical Writer; US- Remote

About Aembit

Aembit is a well-funded cybersecurity startup founded in late 2021. The company’s founders have a strong track record, having started several companies that were successfully acquired. We are focused on a new area in the hot identity space.

Aembit is a workload identity and access management platform that secures how applications, services, and AI agents authenticate to the resources they need. Think "Okta for workloads and AI agents." We help enterprises manage non-human identities across clouds, SaaS, and on‑premise environments without the pain of static credentials, secrets sprawl, or fragmented tooling.

As AI agents and agentic systems become a bigger part of enterprise infrastructure, Aembit is at the forefront of securing how those agents securely access sensitive data and systems autonomously. We're a growing team solving hard problems at the intersection of identity, security, and modern software architecture.

We're looking for a Senior Technical Writer to join our documentation team. You'll work alongside our Staff Technical Writer to own and evolve Aembit's public documentation: user guides, API references, tutorials, conceptual content, and troubleshooting guides.

This is a hands‑on role where you dig into the product, talk to engineers and customers, and figure out how to explain complex identity and security concepts to technical audiences. You'll configure Aembit the same way our customers do, working in real cloud environments to understand their experience firsthand. You'll work in a docs‑as‑code environment with modern tooling, but your primary focus is creating excellent documentation.

Our team uses AI tools and custom workflows to augment how we create documentation. We're always iterating and improving on our AI tooling and processes. AI‑generated writing is a starting point that goes through thorough human review and editing before anything gets published.

Be prepared to discuss your respect or disdain for the Oxford comma, docs frameworks, AI, IDEs, operating systems, and other things you geek out on!

The following responsibilities represent what the role looks like once you're up to speed. No one is expected to know or do everything on day one. We'll work together to ramp you up and figure out how to best leverage your strengths.

• Own the development and maintenance of Aembit's public documentation, including user guides, API references, tutorials, conceptual content, and troubleshooting guides. Write for Dev Ops engineers, security teams, and platform engineers while keeping content current as the product evolves.
• Champion the Reader
  
  Experience:
  
  Approach documentation from the customer's perspective rather than just the product's perspective. Test workflows and procedures yourself before or while documenting them. Identify gaps, pain points, and opportunities to improve how users find and use information.
• Work in a Docs‑as‑Code Environment:
  Collaborate using Git‑based workflows with branches, pull requests, and code reviews. Write in Markdown and MDX for our Astro Starlight documentation site. Create diagrams as code and apply pre‑built and custom components throughout the docs.
• Partner Across the Company:
  Work with engineering, product, and customer success to identify documentation needs and priorities. Collaborate with subject matter experts to extract accurate technical information. Gather and incorporate feedback from users and internal stakeholders in a remote, async environment.
• Contribute to AI‑Assisted Workflows:
  Use AI tools as part of your daily workflow for research, drafting, and editing. Provide feedback to help iterate and improve our documentation processes and tooling.

To set clear expectations, you won't be responsible for any of the following:

• Marketing copy:
  Our team doesn't write marketing content. We do, however, work closely with the marketing team to ensure alignment of each team's content.
• Support knowledge base:
  We work closely with support to ensure our troubleshooting docs complement (not duplicate) the support KB, but we don't own support documentation.
• Internal engineering docs:
  We focus on…