Aembit
Senior Technical Writer (US-Based Remote)
Aembit, Silver Spring, Maryland, United States, 20900
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. About the Role
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! What You'll Do
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 DevOps 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. What You Won't Do
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 external, customer‑facing documentation. We may occasionally help review internal docs intended for customer discussions, but we don't author them. What We're Looking For
We focus on what you can do and how you demonstrate it. The following required skills are essential. Preferred skills represent areas that would strengthen your candidacy, where any combination is valuable. Required
Proven experience writing technical documentation for developer tools, APIs, SDKs, infrastructure, containerization, or security products Hands‑on experience with Git‑based workflows (branches, pull requests, code reviews), Markdown, and static site generators Ability to read and understand front‑end code (HTML, JavaScript, JSX) within documentation markup and apply pre‑built or custom components Ability to read and understand at least one of the following: Go, TypeScript, Rust, C#, Python, or Java Hands‑on experience with at least one major cloud provider (AWS, Google Cloud, or Azure) Experience creating diagrams using diagrams‑as‑code tools such as Mermaid or D2 Ability to take, edit, and annotate screenshots of software UIs for documentation Ability to organize complex information logically for findability and usability Ability to learn complex technical concepts and explain them clearly to technical and non‑technical audiences Hands‑on experience with AI tooling such as Claude Code, Cursor, Windsurf, or similar Strong focus on user experience, usability, and accessibility in documentation Solid editing and revision skills with attention to clarity and accuracy Experience creating simple automation or scripts for recurring tasks Ability to work independently and own projects from research through publication Comfort with remote, asynchronous collaboration across a distributed team Genuine enthusiasm for technical writing, technology, and continuous learning Preferred
Experience with one or more of the following: security, identity, DevOps, or cloud infrastructure products Experience with documentation linting tools such as Vale or similar Experience with Jira or similar project management tools Familiarity with one or more documentation frameworks such as Diátaxis, 7‑Action Doc Model, or similar Understanding of one or more of the following: OAuth, SAML, OIDC, SPIFFE, Kubernetes, or cloud IAM Familiarity with IaC frameworks such as Terraform, CloudFormation, or similar Experience working with one or more of the following: Docusaurus, Astro, Hugo, or Eleventy Experience maintaining or creating custom writing style guides Experience with Docker, Kubernetes, or similar technologies Comfortable using Bash, Zsh, PowerShell, or similar CLIs Nice‑to‑Haves
Experience creating video documentation or screencasts Published technical blog posts or articles outside of work Involvement in documentation communities such as Write the Docs or Good Docs Project Experience using docs analytics to measure and improve content effectiveness Experience with localization or internationalization of documentation What We Offer
Aembit offers the following benefits: A remote working environment with flexible working hours to accommodate work‑life balance Competitive salary and benefits, including health, dental, and vision insurance Generous Employee Stock Options Program Flexible vacation and time off A small team with some of the best software engineers in the industry Your contributions will be highly visible, impactful, and appreciated Aembit has been featured on Fast Company’s Seventh‑Annual List of the 100 Best Workplaces for Innovators When You Apply
Submit your application with the following: Your resume. A brief note on why this role interests you. Two to three writing samples that represent work you're most proud of and excited to talk about. Take the following into consideration:
Only provide writing samples that can be shared publicly. Do not submit confidential or internal writing samples from current or previous employers that you don't have permission to share. Show off your understanding or expertise in a highly‑technical subject. If possible, submit writing samples of things you're genuinely excited or enthusiastic about. If you can't submit writing samples that are publicly available and aren't confidential or internal, be bold and creative with your samples and be prepared to dive in deep when discussing them.
#J-18808-Ljbffr
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. About the Role
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! What You'll Do
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 DevOps 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. What You Won't Do
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 external, customer‑facing documentation. We may occasionally help review internal docs intended for customer discussions, but we don't author them. What We're Looking For
We focus on what you can do and how you demonstrate it. The following required skills are essential. Preferred skills represent areas that would strengthen your candidacy, where any combination is valuable. Required
Proven experience writing technical documentation for developer tools, APIs, SDKs, infrastructure, containerization, or security products Hands‑on experience with Git‑based workflows (branches, pull requests, code reviews), Markdown, and static site generators Ability to read and understand front‑end code (HTML, JavaScript, JSX) within documentation markup and apply pre‑built or custom components Ability to read and understand at least one of the following: Go, TypeScript, Rust, C#, Python, or Java Hands‑on experience with at least one major cloud provider (AWS, Google Cloud, or Azure) Experience creating diagrams using diagrams‑as‑code tools such as Mermaid or D2 Ability to take, edit, and annotate screenshots of software UIs for documentation Ability to organize complex information logically for findability and usability Ability to learn complex technical concepts and explain them clearly to technical and non‑technical audiences Hands‑on experience with AI tooling such as Claude Code, Cursor, Windsurf, or similar Strong focus on user experience, usability, and accessibility in documentation Solid editing and revision skills with attention to clarity and accuracy Experience creating simple automation or scripts for recurring tasks Ability to work independently and own projects from research through publication Comfort with remote, asynchronous collaboration across a distributed team Genuine enthusiasm for technical writing, technology, and continuous learning Preferred
Experience with one or more of the following: security, identity, DevOps, or cloud infrastructure products Experience with documentation linting tools such as Vale or similar Experience with Jira or similar project management tools Familiarity with one or more documentation frameworks such as Diátaxis, 7‑Action Doc Model, or similar Understanding of one or more of the following: OAuth, SAML, OIDC, SPIFFE, Kubernetes, or cloud IAM Familiarity with IaC frameworks such as Terraform, CloudFormation, or similar Experience working with one or more of the following: Docusaurus, Astro, Hugo, or Eleventy Experience maintaining or creating custom writing style guides Experience with Docker, Kubernetes, or similar technologies Comfortable using Bash, Zsh, PowerShell, or similar CLIs Nice‑to‑Haves
Experience creating video documentation or screencasts Published technical blog posts or articles outside of work Involvement in documentation communities such as Write the Docs or Good Docs Project Experience using docs analytics to measure and improve content effectiveness Experience with localization or internationalization of documentation What We Offer
Aembit offers the following benefits: A remote working environment with flexible working hours to accommodate work‑life balance Competitive salary and benefits, including health, dental, and vision insurance Generous Employee Stock Options Program Flexible vacation and time off A small team with some of the best software engineers in the industry Your contributions will be highly visible, impactful, and appreciated Aembit has been featured on Fast Company’s Seventh‑Annual List of the 100 Best Workplaces for Innovators When You Apply
Submit your application with the following: Your resume. A brief note on why this role interests you. Two to three writing samples that represent work you're most proud of and excited to talk about. Take the following into consideration:
Only provide writing samples that can be shared publicly. Do not submit confidential or internal writing samples from current or previous employers that you don't have permission to share. Show off your understanding or expertise in a highly‑technical subject. If possible, submit writing samples of things you're genuinely excited or enthusiastic about. If you can't submit writing samples that are publicly available and aren't confidential or internal, be bold and creative with your samples and be prepared to dive in deep when discussing them.
#J-18808-Ljbffr