Technical Content Engineer, Cloud Native

Commvault is hiring a Technical Content Engineer to support Clumio’s cloud-native product. The role builds and tests technical content, examples, and onboarding experiences that help cloud builders adopt the product and reach first value independently.

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

Requirements:

• 4+ years in a developer-facing technical role—technical writing, developer relations, solutions engineering, support engineering, or software engineering with a strong writing track record
• You write code and you write prose, and you refuse to publish the second without validating the first
• Working fluency in AWS: S3, IAM, DynamoDB, RDS, EC2, and the mental model of how a cloud team actually operates
• Hands-on with infrastructure as code (Terraform, CloudFormation, or CDK), APIs, SDKs, and the command line
• Docs-as-code fluency: Git, Markdown/MDX, PR-based review, and content that lives next to the product
• The instinct of a teacher—you know where a reader will get confused before they do, and you write to that
• Demonstrated technical content that shipped and moved something: writing samples and example repos required
• 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 attached
• AWS certification, or a personal AWS account with a billing history that tells a story
• Experience with docs analytics, search behavior, or optimizing content for AI retrieval