# Technical Content Engineer, Cloud Native — Commvault

- Location: New Jersey
- Posted pay: $72k–$156k/yr
- Posted: Jul 29, 2026
- Status: open (checked Nov 19, 2026)
- Apply (employer's site): https://job-boards.greenhouse.io/commvault/jobs/5371666008
- Employer record: https://visajobs.io/company/commvault-systems.md

## Sponsorship history
- Tier: Employer history only
- With this exact title: 0

## Description
Recruitment Fraud Alert
We’ve learned that scammers are impersonating Commvault team members—including HR and leadership—via email or text. These bad actors may conduct fake interviews and ask for personal information, such as your social security number.
What to know:
Commvault does not conduct interviews by email or text.
We will never ask you to submit sensitive documents (including banking information, SSN, etc) before your first day.
Commvault recruiters may contact prospective candidates through LinkedIn and other professional networking platforms regarding career opportunities. If you are unsure whether a recruiting communication is legitimate, review the profile to ensure they have a badge verifying them as a Commvault employee.
If you suspect a recruiting scam, please contact us at wwrecruitingteam@commvault.com
About Commvault
Commvault (NASDAQ: CVLT) delivers continuous recovery for the AI era. We help organizations stay ready for constant disruption by returning critical data, applications, identities, and AI systems to a clean, trusted state. Our purpose-built recovery solutions span cloud-native and hybrid environments, leveraging AI to enable resilience at enterprise scale.
Clumio is bought by builders. The people who evaluate us are Staff engineers, SREs, platform leads, and directors of engineering—people who will decide whether to trust us with 50 petabytes of S3 before they ever talk to a salesperson. They arrive from a search result, an AI assistant, or a colleague’s recommendation. They open the docs. They start a trial. And within about twenty minutes, they either get their first backup running or they close the tab.
This role owns that twenty minutes—and everything that leads up to it.
You are not a documentation writer who sits downstream of engineering and turns release notes into paragraphs. You are a content engineer: you run the code, you build the example, you break the workflow, and then you write the thing that makes it obvious. Every guide you publish ships with something that actually works—a Terraform module, a CloudFormation template, a CLI walkthrough, a tested API call. If a builder can’t copy it, paste it, and have it succeed on the first try, it isn’t finished.
You will sit with the Cloud Native product organization and work shoulder-to-shoulder with engineering, product, and growth. Your work is the top of the funnel, the onboarding path, and the reason a trial converts.
Why This Role Matters
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.
What You’ll Do:
Own the Content That Sells the Product
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
Build It Before You Write About It
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
Write for How Builders Actually Find Things
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
Close the Loop with Product and Growth
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
What Success Looks Like
Builders reach first value in a trial without human help, and the activation curve shows it
Docs and guides are a measurable source of qualified signups, not a cost center
Every AWS service Clumio protects has a current, tested, copy-pasteable guide—and the example repos actually run
When an engineer asks an AI assistant how to protect S3 at scale, our content is what it draws from
Support tickets that used to be “how do I…” questions stop arriving, because the answer is already published
Your First 90 Days
Week 1: You run the trial yourself as a new user would, and write down every place you got stuck
Day 30: You have shipped a rebuilt getting-started path and at least one tested example repo
Day 90: You own the content roadmap, 

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
