Senior Software Developer (Web) (Remote)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. The page already shows it, so we don't add heading for Senior Software Developer (Web). We'll start with About the role (position overview). Then Responsibilities. Then Requirements (maybe Qualifications). Then Skills? Could combine skills into Requirements. But we can have a Skills section if there are specific skills listed beyond qualifications. The qualifications already list many skills; we could put them under Requirements. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications, but we should avoid duplication. Perhaps we put Requirements as minimal qualifications, Qualifications as preferred qualifications. Or we combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine into one Qualifications section that includes both minimum and preferred. But they gave examples of headings; we can choose to include Requirements and Qualifications both if we have content. However we have both minimum and preferred qualifications; we could split: Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications. That seems reasonable.
Skills: Could be extracted from qualifications but maybe we don't need separate Skills if we already have Requirements and Qualifications. Better to omit Skills to avoid thin section.
Thus sections: About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay.
Now we need to extract content.
About the role: Position Overview paragraphs (both English and French). We need to preserve all substantive information, not duplicate. The English and French versions are same content translated. We should include only one version? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The posting includes both languages; we could include both but that would be duplicate content. However they are translations; preserving both might be considered duplicate but still substantive. The instruction says remove duplicated lines. The English and French are not duplicated lines but translated content. Might be considered duplicated meaning but not identical lines. Safer to include only one language (maybe English) as the substantive info; but we would be omitting the French version which is also substantive. However the instruction says remove duplicated lines; translation is not duplicate lines. But we might still include both to preserve all info. However that would cause a lot of repetition and near-duplicate content, which might be considered not ideal but not prohibited. The instruction: "Prefer a few substantive sections over many thin ones." Including both languages would double the content but still substantive. I'd lean to include only English version to avoid redundancy, as the French is just translation. The instruction about duplicated lines likely refers to exact repeats like "Job Requisition ID #..." etc. So we can keep English only.
Thus About the role: combine the two paragraphs from English Position Overview.
Let's extract:
"Virtual and augmented reality are transforming design and creation through new immersive and collaborative experiences that will impact how major segments like entertainment, architecture, developer, construction, and manufacturing converge. The industry is being transformed by innovations in Extended Reality (XR) and AI which are creating new ways of leveraging spatial computing to review, collaborate and create in immersive, collaborative environments. As a Senior Software Developer (Web), you will be part of the team responsible for building and delivering a collaborative XR platform within the Interactive Graphics Solution org. In this role, you will partner closely with UX Designers to build products and services that enhance our customer’s spatial understanding through our industry leading Autodesk Platform technologies. If you have a passion for creating modern, beautiful, and high-performance web frontends and share our passion for XR, join us as we redefine how we work and collaborate with each other in a new reality."
That's the overview.
Now Responsibilities: list bullet points from English responsibilities.
Responsibilities lines:
- Design, develop and maintain frontend applications (JavaScript, React, TypeScript) alongside backend services (Golang, AWS)
- Build and optimize beautifully rendered, web-based components that push performance limits across XR Headsets
- Lead large, complex projects across teams, defining scope, planning execution, and delivering milestones on time
- Collaborate with architects, UX designers, product managers, and stakeholders to translate business requirements into product features
- Help shape system design and architecture across cloud and web environments, improving scalability, performance and feel across immersive and 2D environments
- Lead technical discussions, align outcomes with business goals, and document solutions for clarity and adoption
- Stay ahead of emerging trends to anticipate and address future development needs
We'll put each as
- .
Now Requirements (minimum qualifications): list bullet points.
Minimum Qualifications lines:
- Bachelor’s or Master’s degree in Computer Science or related technical field, or equivalent practical experience
- 5+ years of hands-on experience in software design and development with emphasis on Frontend development
- Deep, hands-on experience developing complex, performance-sensitive web applications in JavaScript (ES6+) with working knowledge of React and Typescript
- Strong grasp of browser performance profiling, rendering bottlenecks, and limitations of the DOM and JavaScript engines
- Experience building applications with CPU constraints that push browser limits
- Experience with real-time communication technologies like WebSockets, Microsoft Fluid and supporting data formats (JSON, Protobuf)
- Demonstrated excellence in cross-functional collaboration, with experience working across multiple engineering teams and stakeholders
- Strong understanding of algorithms, data structures, concurrency, distributed systems, and browser event loops and rendering pipelines
- Experience with Electron
- Comfortable with AWS, specifically services like S3
- Git, Github knowledge
- Experience in an agile development environment
- Good problem-solving and communication skills
We'll list as
- .
Now Qualifications (preferred): list bullet points.
Preferred Qualifications lines:
- MS Degree in Computer Science or similar technical field
- Experience with 3D and immersive web technologies like ThreeJS or WebXR
- Proven experience with AWS cloud services and designing resilient, scalable cloud-native architecture.
- Full stack experience (Backend + Frontend) is a bonus
- Experience with Databases (SQL and noSQL)
- Experience with containerization (Docker)
- Basic game engine experience (Unreal Engine preferred)
- Basic experience with AR, VR and MR
- Proficiency with CI/CD tools and practices (e.g., Jenkins, Spinnaker) and Infrastructure as Code (e.g., Terraform)
- Experience with observability tools for monitoring, logging, and tracing in distributed systems (e.g., Dynatrace, Prometheus, Grafana, Splunk)
Also "The Ideal Candidate" traits: Result Oriented, Continuous Learner, Build Trust, Team Player. Those could be considered part of Qualifications or maybe separate section but we can include them as bullet points under Qualifications as well. They are traits, not qualifications but could be included. However we might want to keep Qualifications focused on technical. The instruction: include a section only when posting has real specific content. The Ideal Candidate section is specific content; we could include it under Qualifications or maybe a separate section like "Attributes". But we only have allowed headings list; we could put them under Qualifications as well. Or we could create a separate section "Qualifications" and include both technical and ideal candidate traits. That's fine.
Now Benefits: content: "In addition to base salaries, our compensation package may include annual cash bonuses, commissions for sales roles, stock grants, and a comprehensive benefits package." Also "Belonging We take pride in cultivating a culture of belonging where everyone can thrive." That's more culture; maybe not benefit. We'll include the benefits line.
Thus Benefits bullet list:
- Annual cash bonuses
- Commissions for sales roles
- Stock grants
- Comprehensive benefits package
Now Pay: content: "For Canada based roles, we expect a starting base salary between $107,000 and $157,300. Offers are based on the candidate’s experience and geographic location, and may exceed this range."
We'll put that as a
maybe.
Now we need to ensure we don't include any boilerplate like "Learn More About Autodesk", "Welcome to Autodesk!", "Salary transparency", "Belonging", "In-Person Onboarding and Identity Verification", etc.
We also need to exclude the French duplicate content; we already omitted.
Now produce HTML fragment:
About the role
...overview...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Benefits
...
Pay
...
Make sure no extra whitespace at start/end? It's fine.
Now check that we didn't include Schedule section.
Now ensure we preserved all substantive information: Did we miss any? The overview includes mention of "Interactive Graphics Solution org". We kept that. The responsibilities include "Lead large, complex projects across teams, defining scope, planning execution, and delivering milestones on time". Good.
We omitted the line "Help shape system design and architecture across cloud and web environments, improving scalability, performance and feel across immersive and 2D environments". Included.
We omitted "Lead technical discussions, align outcomes with business goals, and document solutions for clarity and adoption". Included.
We omitted "Stay ahead of emerging trends to anticipate and address future development needs". Included.
Minimum qualifications: we included all.
Preferred qualifications: we included all.
We omitted "The Ideal Candidate" traits; we could add them as bullet points under Qualifications. Let's add them to Qualifications list to preserve that content.
Thus Qualifications bullets will include:
- MS Degree in Computer Science or similar technical field
- Experience with 3D and immersive web technologies like ThreeJS or WebXR
- Proven experience with AWS cloud services and designing resilient, scalable cloud-native architecture.
- Full stack experience (Backend + Frontend) is a bonus
- Experience with Databases (SQL and noSQL)
- Experience with containerization (Docker)
- Basic game engine experience (Unreal Engine preferred)
- Basic experience with AR, VR and MR
- Proficiency with CI/CD tools and practices (e.g., Jenkins, Spinnaker) and Infrastructure as Code (e.g., Terraform)
- Experience with observability tools for monitoring, logging, and tracing in distributed systems (e.g., Dynatrace, Prometheus, Grafana, Splunk)
- Result Oriented: You finish the
for prose. We must not repeat job title as heading. The page already shows it, so we don't add heading for Senior Software Developer (Web). We'll start with About the role (position overview). Then Responsibilities. Then Requirements (maybe Qualifications). Then Skills? Could combine skills into Requirements. But we can have a Skills section if there are specific skills listed beyond qualifications. The qualifications already list many skills; we could put them under Requirements. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications, but we should avoid duplication. Perhaps we put Requirements as minimal qualifications, Qualifications as preferred qualifications. Or we combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine into one Qualifications section that includes both minimum and preferred. But they gave examples of headings; we can choose to include Requirements and Qualifications both if we have content. However we have both minimum and preferred qualifications; we could split: Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications. That seems reasonable. Skills: Could be extracted from qualifications but maybe we don't need separate Skills if we already have Requirements and Qualifications. Better to omit Skills to avoid thin section. Thus sections: About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay. Now we need to extract content. About the role: Position Overview paragraphs (both English and French). We need to preserve all substantive information, not duplicate. The English and French versions are same content translated. We should include only one version? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The posting includes both languages; we could include both but that would be duplicate content. However they are translations; preserving both might be considered duplicate but still substantive. The instruction says remove duplicated lines. The English and French are not duplicated lines but translated content. Might be considered duplicated meaning but not identical lines. Safer to include only one language (maybe English) as the substantive info; but we would be omitting the French version which is also substantive. However the instruction says remove duplicated lines; translation is not duplicate lines. But we might still include both to preserve all info. However that would cause a lot of repetition and near-duplicate content, which might be considered not ideal but not prohibited. The instruction: "Prefer a few substantive sections over many thin ones." Including both languages would double the content but still substantive. I'd lean to include only English version to avoid redundancy, as the French is just translation. The instruction about duplicated lines likely refers to exact repeats like "Job Requisition ID #..." etc. So we can keep English only. Thus About the role: combine the two paragraphs from English Position Overview. Let's extract: "Virtual and augmented reality are transforming design and creation through new immersive and collaborative experiences that will impact how major segments like entertainment, architecture, developer, construction, and manufacturing converge. The industry is being transformed by innovations in Extended Reality (XR) and AI which are creating new ways of leveraging spatial computing to review, collaborate and create in immersive, collaborative environments. As a Senior Software Developer (Web), you will be part of the team responsible for building and delivering a collaborative XR platform within the Interactive Graphics Solution org. In this role, you will partner closely with UX Designers to build products and services that enhance our customer’s spatial understanding through our industry leading Autodesk Platform technologies. If you have a passion for creating modern, beautiful, and high-performance web frontends and share our passion for XR, join us as we redefine how we work and collaborate with each other in a new reality." That's the overview. Now Responsibilities: list bullet points from English responsibilities. Responsibilities lines: - Design, develop and maintain frontend applications (JavaScript, React, TypeScript) alongside backend services (Golang, AWS) - Build and optimize beautifully rendered, web-based components that push performance limits across XR Headsets - Lead large, complex projects across teams, defining scope, planning execution, and delivering milestones on time - Collaborate with architects, UX designers, product managers, and stakeholders to translate business requirements into product features - Help shape system design and architecture across cloud and web environments, improving scalability, performance and feel across immersive and 2D environments - Lead technical discussions, align outcomes with business goals, and document solutions for clarity and adoption - Stay ahead of emerging trends to anticipate and address future development needs We'll put each as
maybe. Now we need to ensure we don't include any boilerplate like "Learn More About Autodesk", "Welcome to Autodesk!", "Salary transparency", "Belonging", "In-Person Onboarding and Identity Verification", etc. We also need to exclude the French duplicate content; we already omitted. Now produce HTML fragment:
About the role
...overview...
Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
Pay
...
Make sure no extra whitespace at start/end? It's fine. Now check that we didn't include Schedule section. Now ensure we preserved all substantive information: Did we miss any? The overview includes mention of "Interactive Graphics Solution org". We kept that. The responsibilities include "Lead large, complex projects across teams, defining scope, planning execution, and delivering milestones on time". Good. We omitted the line "Help shape system design and architecture across cloud and web environments, improving scalability, performance and feel across immersive and 2D environments". Included. We omitted "Lead technical discussions, align outcomes with business goals, and document solutions for clarity and adoption". Included. We omitted "Stay ahead of emerging trends to anticipate and address future development needs". Included. Minimum qualifications: we included all. Preferred qualifications: we included all. We omitted "The Ideal Candidate" traits; we could add them as bullet points under Qualifications. Let's add them to Qualifications list to preserve that content. Thus Qualifications bullets will include: - MS Degree in Computer Science or similar technical field - Experience with 3D and immersive web technologies like ThreeJS or WebXR - Proven experience with AWS cloud services and designing resilient, scalable cloud-native architecture. - Full stack experience (Backend + Frontend) is a bonus - Experience with Databases (SQL and noSQL) - Experience with containerization (Docker) - Basic game engine experience (Unreal Engine preferred) - Basic experience with AR, VR and MR - Proficiency with CI/CD tools and practices (e.g., Jenkins, Spinnaker) and Infrastructure as Code (e.g., Terraform) - Experience with observability tools for monitoring, logging, and tracing in distributed systems (e.g., Dynatrace, Prometheus, Grafana, Splunk) - Result Oriented: You finish the