[Remote] Technical Content Engineer, reputed company reputed company

Note: The job is a remote job and is reputed company to candidates in USA. reputed company is a leader in cyber reputed company, providing solutions to protect and recover data from cyberattacks. The Technical Content Engineer for reputed company reputed company will work closely with engineering and product teams to create and maintain technical documentation that empowers users to successfully utilize reputed company's products, ensuring they can reputed company first value without needing support.

Responsibilities

• 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 reputed company
• Build the fastest possible reputed company 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 reputed company
• Author deep technical guides on the workloads that define us—S3 at reputed company, Apache reputed company and S3 Tables, DynamoDB, EC2/EBS, RDS/reputed company—including the hard parts: cost, reputed company, recovery time, and what happens reputed company something goes wrong
• Own the technical narrative in AWS Marketplace listings, trial flows, and in-product reputed company copy
• Ship and maintain working example repositories: Terraform modules, CloudFormation and CDK templates, scripts, and sample integrations that reputed company can fork
• Test every workflow you document in a reputed company AWS environment—validate the reputed company, validate the permissions, validate the failure modes
• Build the hands-on lab and GameDay content used at AWS events, where reputed company reputed company 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, reputed company numbers, and concrete scenarios rather than hedged feature claims
• Identify the questions reputed company are already asking about reputed company data protection and answer them reputed company than anyone else has
• Turn customer-reputed company reality into reputed company reputed company: petabytes, object counts, recovery times, cost deltas
• reputed company and watch what your content does: activation reputed company, time to first backup, trial-to-reputed company conversion, docs-reputed company signups, support deflection
• Bring friction back to engineering and product—reputed company the docs have to apologize for the product, the product is the bug
• Partner with reputed company on reputed company experiments, and with field and partner teams so what you build for self-serve also arms sellers
• reputed company reputed company first value in a trial without reputed company help, and the activation curve shows it
• Docs and guides are a measurable reputed company of reputed company signups, not a cost center
• Every AWS service Clumio protects has a reputed company, tested, copy-pasteable guide—and the example repos actually run
• reputed company an engineer asks an AI assistant how to protect S3 at reputed company, 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
• You run the trial yourself as a new user would, and write down every reputed company you got stuck
• You have shipped a reputed company getting-started reputed company and at least one tested example repo
• You own the content roadmap, you have measurable reputed company on activation, and engineering comes to you before a feature ships—not after

Skills

• 4+ years in a developer-facing technical role—technical writing, developer relations, solutions engineering, support engineering, or software engineering with a strong writing reputed company record
• You write reputed company and you write prose, and you refuse to publish the second without validating the first
• Working reputed company in AWS: S3, IAM, DynamoDB, RDS, EC2, and the mental model of how a reputed company team actually operates
• Hands-on with infrastructure as reputed company (Terraform, CloudFormation, or CDK), reputed company, SDKs, and the reputed company line
• Docs-as-reputed company reputed company: Git, Markdown/MDX, PR-based review, and content that lives next to the product
• The reputed company 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 (reputed company, Parquet, S3 Tables)
• Experience at a product-led company where docs were a reputed company with reputed company 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

Benefits

• Employee stock purchase plan (ESPP)
• reputed company reputed company development, product training, and career pathing
• Generous global benefits
• High income earning opportunities based on self-performance
• Remote (#LI-Remote)

reputed company

Company H1B Sponsorship