Senior Technical Content Designer, Platform documentation

📍 Job Overview

Job Title: Senior Technical Content Designer, Platform Documentation

Company: Autodesk

Location: Bengaluru, India

Job Type: Full-time

Category: Technical Content Design / Developer Documentation

Date Posted: 2026-04-16

Experience Level: Mid-Senior Level (Estimated 5-10 years)

Remote Status: On-site

🚀 Role Summary

• Lead the content strategy and execution for CloudOS, Autodesk's internal platform for delivering services and code to production, focusing on enhancing developer productivity and operational reliability.

• Create and maintain comprehensive, developer-centric technical documentation, including quickstarts, tutorials, reference materials, runbooks, and best-practice patterns, optimized for both human and AI consumption.

• Implement and champion "docs-as-code" systems, maintaining example repositories, starter templates, and automated publishing pipelines to facilitate easy and safe adoption of CloudOS.

• Shape the information architecture, including navigation, taxonomy, and search, to ensure developers can efficiently find critical information, thereby improving their overall experience.

📝 Enhancement Note: While the title is "Senior Technical Content Designer," the responsibilities heavily lean towards a "Developer Documentation Lead" or "Technical Writing Manager" role within a platform engineering context. The focus on strategy, roadmap, and measurable impact elevates this beyond a standard technical writer position. The inclusion of AI-driven tools suggests a forward-thinking approach to documentation.

📈 Primary Responsibilities

• Define and own the end-to-end content strategy for CloudOS developer documentation, establishing priorities, developing a roadmap, and driving measurable improvements in developer productivity.

• Author clear, practical, and task-focused developer documentation, including quickstarts, tutorials, API/CLI references, runbooks, troubleshooting guides, and reusable best-practice patterns.

• Translate complex AI platform guidance and technical concepts (e.g., ADF schemas, deployment pipelines, CD-Proxy, failover, observability, secret handling) into content patterns optimized for consumption by both developers and AI-driven tools.

• Build and maintain scalable "docs-as-code" systems by managing example repositories, starter templates, and automated pipelines to simplify and secure CloudOS adoption.

• Design interactive and task-oriented content, such as step-by-step guides and checklists, to accelerate developer success in real-world CloudOS scenarios.

• Develop and refine the information architecture, including navigation, taxonomy, and search functionality, to ensure rapid discoverability of necessary information for developers.

• Collaborate closely with engineering teams to translate intricate systems into approachable content, including code samples, diagrams, YAML/JSON examples, and API/CLI references, utilizing Git for authoring and reviewing pull requests.

• Conduct user validation through developer interviews, surveys, and task-based testing to continuously improve documentation accuracy and usability.

• Measure key performance indicators (KPIs) such as "time to first success," reduction in support tickets, and developer satisfaction, and use this data to iterate on content strategies.

• Promote and implement "docs-as-code" best practices across the CloudOS team, including CI for documentation, environment versioning, example validation, and localization readiness.

📝 Enhancement Note: The responsibilities are extensive and strategic, emphasizing a proactive and data-driven approach to developer documentation. The role requires a blend of technical acumen, content strategy, information architecture, and user advocacy. The mention of "AI-driven tools" and "AI platform guidance" indicates a need for adaptability to emerging technologies in content creation.

🎓 Skills & Qualifications

Education: While no specific degree is listed, a Bachelor's degree in Computer Science, Technical Communication, English, or a related field is often preferred for senior roles in this domain. Equivalent practical experience will be considered.

Experience:

• Significant experience (estimated 5-10 years) in designing and producing developer-facing technical content for platform or infrastructure products.

• Demonstrated experience in content design and information architecture for complex technical systems, with a proven ability to break down end-to-end workflows into clear, actionable steps.

• Hands-on experience with "docs-as-code" practices, including proficiency with Git/GitHub, Markdown or AsciiDoc, and CI-based publishing workflows.

• Working knowledge of cloud and platform engineering concepts such as containers, ECS/EKS, serverless computing, Terraform, CI/CD, GitOps, IAM, and observability.

• Proven ability to validate content with users, leveraging usability feedback and metrics for continuous improvement.

• Strong collaboration skills, with a track record of working effectively across engineering, product management, security, operations, and AI teams.

• Comfort operating independently in ambiguous environments, driving content initiatives from discovery through delivery and measurement.

Required Skills:

• Expertise in Content Strategy and Information Architecture for technical platforms.

• Proficiency in Developer Documentation (Tutorials, Quickstarts, API/CLI References, Runbooks).

• Strong command of Docs-as-Code principles and workflows.

• Hands-on experience with Git and GitHub for content management.

• Proficiency in Markdown or AsciiDoc.

• Understanding of Cloud & Platform Engineering concepts (CI/CD, Containers, IaC).

• Exceptional Developer-Focused Writing and Editing Skills.

• User Research and Usability Testing Methodologies.

• Data Analysis and Metrics-Driven Content Improvement.

• Cross-functional Collaboration and Stakeholder Management.

• Independent Work Ethic and Ambiguity Navigation.

Preferred Skills:

• Familiarity with Application Definition Files (ADF) or similar declarative infrastructure descriptions (YAML/JSON, Jsonnet).

• Basic prototyping skills for interactive documentation (e.g., Playgrounds, sandboxes).

• Experience integrating documentation with CI pipelines to validate example code.

• Background in UX Writing or Content Strategy within developer tools or platform engineering.

📝 Enhancement Note: The "Minimum Qualifications" section is quite detailed and aligns with a senior-level role. The emphasis on "docs-as-code," specific cloud technologies, and user validation points to a highly technical and user-centric approach to documentation. The preference for ADF and prototyping skills suggests a desire for advanced capabilities in creating dynamic documentation.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• A strong portfolio showcasing experience in designing and producing developer-facing technical content for platform or infrastructure products.

• Demonstrate expertise in breaking down complex, end-to-end technical workflows into clear, modular, and actionable documentation steps.

• Provide examples of content that has been validated with users, highlighting how feedback and metrics were used to drive improvements.

Process Documentation:

• Examples of creating quickstarts, tutorials, and reference material (API/CLI references, schema definitions) for complex technical systems.

• Demonstrate experience in developing runbooks, troubleshooting guides, and reusable best-practice patterns that enhance operational reliability.

• Illustrate the ability to translate AI platform guidance and complex technical concepts into consistent, production-ready content patterns optimized for AI and human consumption.

• Showcase the creation of task-focused, interactive content, such as step-by-step guides and checklists, designed to accelerate developer success.

📝 Enhancement Note: The role explicitly requires a strong portfolio, emphasizing practical examples of developer-facing content for platform products. The focus on "docs-as-code," user validation, and translating complex systems into actionable guides are key components expected in the portfolio.

💵 Compensation & Benefits

Salary Range: Based on industry benchmarks for a Senior Technical Content Designer/Developer Documentation Lead with 5-10 years of experience in a major tech hub like Bengaluru, India, the estimated annual salary range would be ₹18,00,000 to ₹30,00,000 (approximately $21,500 - $36,000 USD). This range can fluctuate based on specific skills, interview performance, and Autodesk's internal compensation bands.

Benefits:

• Annual cash bonuses, providing performance-based financial incentives.

• Commissions (primarily for sales roles, but may be applicable in some strategic GTM-adjacent roles or performance bonuses).

• Stock grants, offering equity ownership and long-term financial participation in Autodesk's success.

• Comprehensive benefits package, typically including health insurance, retirement plans, paid time off, parental leave, and professional development opportunities.

Working Hours: The standard working hours are typically 40 hours per week. While the role is on-site, there may be flexibility offered depending on team needs and individual arrangements, common in the tech industry.

📝 Enhancement Note: Salary is estimated based on the Senior level, specific technical domain (platform documentation), and location (Bengaluru, India) using typical compensation data for experienced technical professionals in India. Benefits are explicitly mentioned in the job description.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software & Technology, specializing in 3D design, engineering, and entertainment software. Autodesk is a leader in enabling digital creation and transformation across various industries.

Company Size: Large Enterprise (Autodesk has over 10,000 employees globally). This implies structured processes, significant resources, and opportunities for impact within a large organization.

Founded: 1982. With a long history, Autodesk has established a strong market presence and a deep understanding of its customer needs, evolving its platform and offerings over decades.

Team Structure:

• The role is within the CloudOS platform team, suggesting a focus on internal developer tooling and infrastructure. The team is likely composed of engineers, product managers, and other technical specialists.

• This Senior Content Designer will likely report to a manager or lead responsible for developer experience or platform engineering tooling.

Methodology:

• Data Analysis & Insights: The role emphasizes measuring impact through metrics like "time to first success," reduced support tickets, and developer satisfaction to drive content improvements.

• Workflow Planning & Optimization: A core function is to design and optimize developer workflows through clear, actionable documentation, quickstarts, and tutorials.

• Automation & Efficiency: Implementing "docs-as-code" systems, automated pipelines, and leveraging AI-assisted authoring tools are key to driving efficiency and scalability.

Company Website: https://www.autodesk.com/

📝 Enhancement Note: Autodesk's established presence in the software industry and its focus on enabling innovation provide a strong backdrop. The CloudOS platform team context suggests a role deeply embedded within internal engineering operations, focused on supporting other developers. The emphasis on data-driven improvements and automation aligns with modern GTM and operations best practices.

📈 Career & Growth Analysis

Operations Career Level: This is a Senior individual contributor role, focusing on specialized technical communication and content strategy within a platform engineering context. It requires significant autonomy and strategic input.

Reporting Structure: The role reports into the CloudOS platform team, likely under a manager or lead overseeing developer experience or platform tooling. Collaboration will be extensive across multiple engineering and product teams.

Operations Impact: The primary impact is on developer productivity, adoption speed, and operational reliability of the CloudOS platform. By providing high-quality, accessible documentation, this role directly contributes to faster onboarding, reduced friction for internal developers, and more efficient use of Autodesk's core platform services. This indirectly impacts the speed and quality of product development across the company.

Growth Opportunities:

• Technical Specialization: Deepen expertise in platform engineering documentation, cloud technologies, and AI-assisted authoring tools, potentially leading to Principal or Staff Content Designer roles.

• Team Leadership: Transition into a team lead or management position for developer documentation or technical content within the platform or a broader engineering organization.

• Cross-functional Expertise: Expand knowledge into product management, UX design, or developer relations by leveraging close collaboration with these teams.

• Industry Influence: Contribute to industry best practices for platform documentation and "docs-as-code" through internal advocacy and potential external contributions (e.g., blog posts, conference talks).

📝 Enhancement Note: This role offers substantial growth potential within a large technology company, moving from a senior individual contributor to leadership or highly specialized technical expert roles. The focus on internal platforms means growth is often tied to the evolution of the company's core technology stack.

🌐 Work Environment

Office Type: The role is specified as "On-site" in Bengaluru, India. This suggests a traditional office environment where collaboration and team interaction are physically present.

Office Location(s): Bengaluru, India (specifically the Sunriver office mentioned in the raw data). This is a major technology hub in India, offering access to a skilled talent pool and a vibrant tech ecosystem.

Workspace Context:

• The environment is expected to be collaborative, requiring close interaction with engineering, product, and AI teams.

• Access to standard office technology and potentially specialized documentation tools, including AI-assisted authoring platforms, will be provided.

• Opportunities for direct engagement with developers using CloudOS will be frequent, fostering a deep understanding of their needs and pain points.

Work Schedule: While the standard is 40 hours per week, the on-site nature implies adherence to office hours, though flexibility might be available for specific tasks or team needs, typical in tech environments. The focus on developer productivity might necessitate responsiveness during core development hours.

📝 Enhancement Note: The on-site requirement in a major tech hub like Bengaluru suggests a dynamic and collaborative office setting, typical of large software companies fostering in-person innovation and team cohesion.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter or hiring manager will likely review applications and portfolios, focusing on alignment with core requirements for technical content strategy and "docs-as-code."

• Technical Interview(s): Expect in-depth discussions about your experience with platform documentation, information architecture, and your approach to creating developer-centric content. This may involve technical Q&A related to cloud concepts.

• Portfolio Review & Presentation: A dedicated session to walk through your portfolio. Be prepared to discuss specific projects, your role, the challenges faced, the solutions implemented (especially regarding content strategy, information architecture, and "docs-as-code"), and the measured impact.

• Cross-functional Interviews: Meetings with engineers, product managers, and potentially other stakeholders to assess collaboration skills, ability to translate complex technical information, and cultural fit.

• Hiring Manager/Final Interview: A discussion to assess overall fit, strategic thinking, and alignment with Autodesk's culture and the specific team's goals.

Portfolio Review Tips:

• Showcase Platform Expertise: Prioritize examples of documentation for platforms, infrastructure, or complex APIs/CLIs.

• Highlight "Docs-as-Code": Include examples demonstrating your workflow with Git, Markdown/AsciiDoc, and CI processes. Explain your contribution to these systems.

• Demonstrate User-Centricity: Present case studies where you used user research, feedback, or metrics to improve documentation. Quantify impact where possible (e.g., "reduced onboarding time by X%," "decreased support tickets related to Y by Z%").

• Structure for Clarity: Organize your portfolio logically. For each project, clearly state the objective, your role, the technologies involved, the content created, and the outcomes.

• AI Integration (If Applicable): If you have experience using AI tools in content creation or optimization, be ready to discuss your approach and learnings.

Challenge Preparation:

• Content Strategy Scenario: You might be presented with a hypothetical platform feature and asked to outline a content strategy, including target audience, key topics, and delivery formats.

• Information Architecture Exercise: You could be asked to propose a sitemap or navigation structure for a new documentation portal.

• Technical Content Snippet: You may be asked to write a short example (e.g., a quickstart step, an API parameter description) for a given technical scenario.

• "Docs-as-Code" Workflow Question: Be prepared to discuss how you would integrate documentation into a CI/CD pipeline or manage contributions from multiple engineers.

📝 Enhancement Note: The interview process is expected to be rigorous, focusing heavily on practical experience, strategic thinking, and the ability to demonstrate impact through a well-curated portfolio. The emphasis on "docs-as-code" and user validation is critical.

🛠 Tools & Technology Stack

Primary Tools:

• Version Control: Git, GitHub (essential for "docs-as-code").

• Markup Languages: Markdown, AsciiDoc (fundamental for writing technical documentation in a code-like environment).

• Documentation Generators/Static Site Generators: Tools like Sphinx, MkDocs, Hugo, or similar frameworks are likely used for publishing.

• CI/CD Tools: Jenkins, GitLab CI, GitHub Actions (for automated documentation builds and deployments).

• AI-Assisted Authoring Tools: Autodesk-approved platforms (specifics to be learned on the job), indicating a modern approach to content creation efficiency.

Analytics & Reporting:

• Web analytics tools (e.g., Google Analytics, custom internal dashboards) to track documentation usage, user engagement, and success metrics.

• Tools for collecting user feedback (e.g., surveys, in-doc feedback widgets).

CRM & Automation: Not directly applicable to this role, as it's focused on internal platform documentation rather than external customer management. However, understanding how internal platform adoption is tracked might involve aspects of internal tooling.

Other Relevant Technologies:

• Cloud Platforms: Understanding of AWS (ECS/EKS), Azure, or GCP concepts.

• Infrastructure as Code (IaC): Terraform, CloudFormation, or similar.

• Containerization: Docker, Kubernetes.

• Observability Tools: Datadog, Prometheus, Grafana, Splunk.

• API Specification Formats: OpenAPI (Swagger).

• Data Formats: YAML, JSON, potentially Jsonnet.

📝 Enhancement Note: Proficiency in "docs-as-code" tooling is paramount. The role requires comfort with Git, markup languages, CI/CD, and a foundational understanding of cloud infrastructure technologies. The mention of AI-assisted authoring tools is a key differentiator.

👥 Team Culture & Values

Operations Values:

• Developer-Centricity: A strong focus on empowering internal developers with the information and tools they need to succeed.

• Collaboration: Working closely with engineering, product, and other teams to ensure documentation is accurate, comprehensive, and meets user needs.

• Data-Driven Improvement: Using metrics and user feedback to continuously refine content strategy and execution.

• Innovation & Efficiency: Embracing new technologies and methodologies ("docs-as-code," AI tools) to improve processes and outcomes.

• Quality & Reliability: Ensuring that platform documentation is trustworthy, up-to-date, and contributes to the operational reliability of CloudOS.

Collaboration Style:

• Proactive Partnership: Actively engaging with subject matter experts (SMEs) early and often to gather information and ensure accuracy.

• Cross-functional Integration: Seamlessly working within a matrixed environment, understanding the goals and constraints of different teams (engineering, product, security, AI).

• Feedback-Driven: Open to constructive criticism and actively seeking feedback on documentation from developers and peers.

• Knowledge Sharing: Contributing to a culture of shared learning, potentially through internal wikis, presentations, or mentoring junior team members.

📝 Enhancement Note: The culture likely emphasizes technical excellence, data-informed decision-making, and a strong sense of ownership. Collaboration is key, especially with engineering teams building the platform.

⚡ Challenges & Growth Opportunities

Challenges:

• Translating Complexity: Effectively simplifying and clarifying highly technical and abstract platform concepts (ADF, deployment pipelines, observability) for a developer audience.

• Rapidly Evolving Platform: Keeping documentation current with the fast pace of development and changes within the CloudOS platform.

• Balancing AI and Human Authorship: Responsibly integrating AI-assisted authoring tools while maintaining quality, accuracy, and a consistent voice.

• Measuring Impact: Defining and accurately measuring the impact of documentation on developer productivity and platform adoption in a way that is meaningful and actionable.

• Ambiguity: Navigating situations where requirements or technical details may not be fully defined, requiring proactive information gathering and strategic decision-making.

Learning & Development Opportunities:

• Deep Dive into CloudOS: Gaining in-depth knowledge of Autodesk's core platform technologies, architecture, and internal development processes.

• AI Authoring Tools: Becoming proficient in cutting-edge AI tools for content generation, editing, and optimization.

• Developer Experience (DX) Best Practices: Expanding expertise in optimizing the overall experience for internal developers.

• Information Architecture for Platforms: Developing advanced skills in structuring and organizing complex technical information.

• Cross-functional Skill Development: Learning about product management, engineering workflows, and AI development through close collaboration.

📝 Enhancement Note: The role offers significant opportunities to tackle complex technical challenges and grow in specialized areas of platform documentation and developer experience, particularly with the integration of AI.

💡 Interview Preparation

Strategy Questions:

• "How would you develop a content strategy for a new, complex platform feature like CloudOS's failover mechanism?" (Focus on audience, goals, content types, and measurement).

• "Describe your process for collaborating with engineers to document a new API or CLI command. How do you ensure accuracy and completeness?" (Highlight Git workflow, review process, and SME management).

Company & Culture Questions:

• "What attracts you to Autodesk and this specific role within the CloudOS platform team?" (Research Autodesk's mission, products, and values; connect to your skills/interests).

• "How do you approach working in a large, complex organization with many stakeholders?" (Emphasize collaboration, communication, and navigating ambiguity).

Portfolio Presentation Strategy:

• Tell a Story: For each portfolio piece, guide the interviewer through the problem, your solution (content created/strategy implemented), and the positive outcome/impact.

• Quantify Success: Whenever possible, use data and metrics to demonstrate the effectiveness of your work (e.g., "This tutorial reduced support requests by 15%").

• Explain Your Process: Clearly articulate your "docs-as-code" workflow, user research methods, and how you collaborated with engineers.

• Address AI Use: If you have relevant experience, be ready to discuss how you've leveraged AI tools responsibly in your content creation process.

📝 Enhancement Note: Preparation should focus on demonstrating strategic thinking, practical application of "docs-as-code" principles, strong collaboration skills, and a data-driven approach to content development, all tailored to a platform engineering context.

📌 Application Steps

To apply for this Senior Technical Content Designer position:

• Submit your application through the Autodesk careers portal link provided.

• Curate Your Portfolio: Select 2-3 of your strongest projects that best showcase your experience with platform documentation, "docs-as-code" workflows, and translating complex technical concepts for developers. Ensure each project clearly outlines the problem, your solution, and the measurable impact.

• Tailor Your Resume: Highlight keywords and responsibilities from the job description, such as "content strategy," "information architecture," "developer documentation," "docs-as-code," "Git," "Markdown/AsciiDoc," and specific cloud technologies. Emphasize achievements with quantifiable results.

• Prepare for the Portfolio Review: Practice walking through your selected portfolio pieces, focusing on your process, collaboration, and the outcomes. Be ready to discuss your approach to AI-assisted authoring tools and user validation.

• Research Autodesk & CloudOS: Understand Autodesk's products, mission, and culture. Gain a basic understanding of what internal platforms and developer tools entail to better tailor your responses and demonstrate genuine interest.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.