Technology · United States

Full-time

Technical Content Engineer, Cloud Native

Commvault · United States · Posted Jul 29, 2026

This posting comes from Commvault. Confirm the details on their site before applying.

Overview

Clumio is one of the top products in AWS Marketplace and carries an NPS of 88, and we got there because builders tried it and it worked. But the ceiling on a product-led motion is set by how many people can succeed without us in the room—and right now, that ceiling is our content. If you are the engineer who kept ending up writing the guide everyone linked to, or the writer who got tired of describing software you were never allowed to run—this is the seat where those are the same job.

Responsibilities

  • Write and maintain the Clumio docs—getting-started paths, service-by-service protection guides, API and SDK references, restore and recovery runbooks—treating them as a product surface, not an archive
  • Build the fastest possible path to first value: a builder should get their first S3 bucket, DynamoDB table, or RDS instance protected without opening a support ticket or booking a call
  • Author deep technical guides on the workloads that define us—S3 at scale, Apache Iceberg and S3 Tables, DynamoDB, EC2/EBS, RDS/Aurora—including the hard parts: cost, scale, recovery time, and what happens when something goes wrong
  • Own the technical narrative in AWS Marketplace listings, trial flows, and in-product onboarding copy
  • Ship and maintain working example repositories: Terraform modules, CloudFormation and CDK templates, scripts, and sample integrations that builders can fork
  • Test every workflow you document in a real AWS environment—validate the code, validate the permissions, validate the failure modes
  • Build the hands-on lab and GameDay content used at AWS events, where builders break something and recover it themselves
  • Produce short technical demos and walkthroughs—written, visual, or recorded—that show the product doing the thing rather than describing it
  • Create content that ranks in search and—increasingly—gets retrieved and cited by AI assistants: specific mechanisms, worked examples, real numbers, and concrete scenarios rather than hedged feature claims
  • Identify the questions builders are already asking about cloud data protection and answer them better than anyone else has
  • Turn customer-scale reality into public proof: petabytes, object counts, recovery times, cost deltas
  • Instrument and watch what your content does: activation rate, time to first backup, trial-to-paid conversion, docs-sourced signups, support deflection
  • Bring friction back to engineering and product—when the docs have to apologize for the product, the product is the bug
  • Partner with growth on onboarding experiments, and with field and partner teams so what you build for self-serve also arms sellers
  • Builders reach first value in a trial without human help, and the activation curve shows it

Requirements

  • Preferred: Background in data protection, storage, data engineering, or lakehouse architectures (Iceberg, Parquet, S3 Tables)
  • Preferred: Experience at a product-led company where docs were a growth channel with real targets attached
  • Preferred: AWS certification, or a personal AWS account with a billing history that tells a story
  • Preferred: Experience with docs analytics, search behavior, or optimizing content for AI retrieval

Benefits

  • Stock / equity, Training & development

Great fits start here.

Whether you're looking for your next role or your next team member, give people and possibilities a place to meet.