SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 72,250 - 155,250 / annual
Clumio, a leading AWS Marketplace product with an NPS of 88, is seeking a Technical Content Engineer to own the content strategy that drives product-led growth. This role bridges engineering and growth, creating the documentation, guides, and working examples that enable builders to reach first value without human intervention.
You will own Clumio's technical documentation as a product surface—not an archive. This includes getting-started paths, service-by-service protection guides, API and SDK references, and recovery runbooks. Your work directly impacts trial-to-paid conversion and activation rates.
Key responsibilities:
**Own the Content That Sells the Product**
- Write and maintain Clumio docs, treating them as a product surface with measurable impact on conversion
- Build the fastest path to first value: builders should protect their first S3 bucket, DynamoDB table, or RDS instance without opening a support ticket
- Author deep technical guides on AWS workloads at scale (S3, Apache Iceberg, DynamoDB, EC2/EBS, RDS/Aurora), including cost, scale, recovery time, and failure scenarios
- Own technical narrative in AWS Marketplace listings, trial flows, and in-product onboarding
**Build It Before You Write About It**
- Ship and maintain working example repositories: Terraform modules, CloudFormation and CDK templates, scripts, and sample integrations
- Test every workflow in a real AWS environment—validate code, permissions, and failure modes
- Build hands-on lab and GameDay content for AWS events
- Produce technical demos and walkthroughs (written, visual, recorded) showing the product in action
**Write for How Builders Actually Find Things**
- Create content optimized for search and AI assistant retrieval: specific mechanisms, worked examples, real numbers, concrete scenarios
- Identify and answer questions builders are asking about cloud data protection better than anyone else
- Turn customer-scale reality into public proof: petabytes, object counts, recovery times, cost deltas
**Close the Loop with Product and Growth**
- Instrument and measure content impact: activation rate, time to first backup, trial-to-paid conversion, docs-sourced signups, support deflection
- Bring friction back to engineering and product when documentation reveals product gaps
- Partner with growth on onboarding experiments and with field/partner teams
**First 90 Days**
- Week 1: Run the trial as a new user and document friction points
- Day 30: Ship a rebuilt getting-started path and at least one tested example repository
- Day 90: Own the content roadmap with measurable activation improvements; engineering consults you before features ship
**Requirements**
- 4+ years in a developer-facing technical role: technical writing, developer relations, solutions engineering, support engineering, or software engineering with strong writing track record
- Write code and prose; refuse to publish documentation without validating the code first
- Working fluency in AWS: S3, IAM, DynamoDB, RDS, EC2, and understanding of how cloud teams operate
- Hands-on with infrastructure as code (Terraform, CloudFormation, or CDK), APIs, SDKs, and command line
- Docs-as-code fluency: Git, Markdown/MDX, PR-based review, content living next to the product
- Teacher's instinct: anticipate reader confusion and write to prevent it
- Demonstrated technical content that shipped and moved metrics; writing samples and example repos required
**Nice to Have**
- Background in data protection, storage, data engineering, or lakehouse architectures (Iceberg, Parquet, S3 Tables)
- Experience at a product-led company where docs were a growth channel with real targets
- AWS certification or personal AWS account with billing history
- Experience with docs analytics, search behavior, or optimizing content for AI retrieval
