Principal Software Developer, Backend Platform

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Need to parse posting. We have description: MaintainX is a leading mobile-first work execution platform... The team and the mission: You'd be joining our backend team within the Platform Engineering division... etc. We need to extract sections: - About the role: likely the paragraph describing the role: "You'd be joining our backend team within the Platform Engineering division..." etc. Also maybe "The team and the mission" part. - Responsibilities: bullet list under "What You’ll Do". That's a list of duties. - Requirements/Qualifications/Skills: The "About You" section lists qualifications. Could split into Requirements, Qualifications, Skills. But we need to avoid thin sections. Could combine into one "Requirements" or "Qualifications". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have content for About the role, Responsibilities, About You (which could be Requirements/Qualifications/Skills). Also Compensation and benefits: includes base pay range $175K - $225K, mention of benefits differing by country, link. So we can have Pay section with the range. Benefits section maybe mention benefits differ by country and link. Schedule? Not mentioned. So we omit Schedule. We need to avoid boilerplate like EEO, legal, etc. There's none. We need to preserve all substantive info, not invent. We need to use

for headings,

• for lists,

  for prose. We must not repeat job title as heading. No Job ID. We must not include placeholder text like "commensurate with experience". Not present. We need to output only HTML fragment. Let's craft:

  About the role

  ... paragraph ...

  Then Responsibilities: list items from "What You’ll Do". Let's extract each bullet: - Shape the technical direction, governance and architecture of the backend platform - Shape AI-native workflows into the platform itself, changing how the org builds services with developers and agents - Proactively identify and drive resolution of cross-cutting technical challenges before they become delivery blockers, working across multiple engineering teams - Define and evolve platform-wide standards, patterns, and abstractions adopted across teams - Influence roadmap priorities by framing trade-offs, surfacing opportunities, and driving alignment across engineering, product, and analytics - Drive adoption of changes across teams, not just their delivery - Mentor and elevate senior engineers through complex problems and architectural decisions - Navigate ambiguity and lead complex, multi-squad initiatives with minimal direction - Participate in the on-call rotation We'll put each as
• . Then Requirements/Qualifications/Skills: Could combine into one section "Requirements". But we have multiple headings allowed. Perhaps we can have "Requirements" and "Qualifications" and "Skills". But we need to avoid thin sections. The About You paragraph includes many items; we could split into Requirements (experience, expertise) and Skills (languages). However we can just have one "Requirements" section with all points as list. That satisfies. But the instruction says we can use those headings; we can choose to include only those with real content. So we can include "Requirements" and maybe skip Qualifications and Skills if we put all in Requirements. That's okay. Thus:

  Requirements

  • Strong AI-native mindset — you've brought AI-assisted workflows into a platform or org, not just your own workflow.
  • Deep expertise in distributed systems, demonstrated with experience making architectural decisions with long-term, cross-org, multi-year consequences
  • Deep exposure across several of the platform's key domains: cloud (AWS), IaC infrastructure (Terraform/Atmos), CI/CD, GraphQL federation, Event driven systems, APIs, and developer experience
  • Expert in Node.js, TypeScript, or similar languages, with a track record of setting standards others adopt.
  • Track record of cross-team impact: changing how multiple teams build, decide, or deliver
  • Demonstrated ability to frame ambiguous technical problems and drive them to resolution with minimal guidance
  • Experience navigating organizational complexity, aligning stakeholders and using data to demonstrate impact
  • Strong technical judgment balanced with pragmatism: knows when to advocate for the right solution and when to move forward
  • Expert-level English, spoken and written — you'll lead platform engineering managers across multiple teams and present technical priorities to executive stakeholders.
  Then Benefits: we have paragraph: "Compensation and benefits. Base pay is one part of the package. Depending on the role, compensation may also include commission, an annual bonus and equity. Benefits differ by country. For roles in the United States, Autodesk’s benefits are described at benefits.autodesk.com. For roles in Canada and other countries, the plan differs on health coverage, retirement and leave, and your recruiter will walk you through it." We need Benefits section: maybe list benefits? Not detailed. But we have info: benefits differ by country, link for US, etc. That's substantive. We'll put as

  . Pay: we have "Compensation Range: $175K - $225K". Also earlier: "Base pay is one part of the package. Depending on the role, compensation may also include commission, an annual bonus and equity." So Pay section can include base pay range and mention of possible commission/bonus/equity. We'll make Pay section with

  containing that. We should not duplicate content. Ensure we don't repeat same sentences. Let's craft About the role paragraph: combine the introductory paragraphs about MaintainX, Autodesk, mission, team. Need to preserve all substantive info but not repeat. We'll summarize? We must not invent or summarize away detail. We need to preserve ALL substantive information; do NOT invent or summarize away detail. That means we should keep the details, not omit them. However we can rephrase? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the information, not omit. But we can rephrase? It might be considered summarizing if we condense. Safer to keep the original sentences, maybe split into paragraphs. We need to avoid boilerplate like navigation etc. The posting includes a lot of descriptive text about MaintainX, Autodesk, mission. We'll keep that as prose. Let's extract the initial block: "MaintainX is a leading mobile-first work execution platform for industrial and frontline teams. More than 13,000 customers, including Duracell, McDonald's, Shell, DHL and Volvo, use MaintainX to cut unplanned downtime and run better operations, across 13.9 million managed assets and 79.5 million completed work orders. In August 2026 MaintainX became part of Autodesk, joining Autodesk Operations Solutions, the organization unifying Autodesk's operations platform alongside Tandem, FlexSim and Fusion Operations. Autodesk's strategy is to converge design, make and operate into one continuous lifecycle: design an asset, build it, run it, then feed what you learn running it back into the next design. Autodesk had design and make. Operate is the phase that tells you what actually happened, and it is ours. We're growing fast and hiring the Engineering talent to match. The team and the mission You'd be joining our backend team within the Platform Engineering division. We're building an AI-native platform for our internal developers, over 150 of them, guided by a single question: does this shorten the time from idea to value, for the teams building on our platform and for the customers they ultimately serve? The smooth path is the safe, fast path, because the platform makes it the default. We build the route that maximizes AI acceleration. You'll set the technical direction for how backend services get built, shipped, and operated across the engineering org — not just for one team." We can keep that as About the role paragraph(s). Might be long but okay. Now Responsibilities list as above. Then Requirements list as above. Then Benefits paragraph: "Compensation and benefits. Base pay is one part of the package. Depending on the role, compensation may also include commission, an annual bonus and equity. Benefits differ by country. For roles in the United States, Autodesk’s benefits are described at benefits.autodesk.com. For roles in Canada and other countries, the plan differs on health coverage, retirement and leave, and your recruiter will walk you through it." But note that part about base pay etc also belongs to Pay. We might split: Pay section: "Base pay is one part of the package. Depending on the role, compensation may also include commission, an annual bonus and equity. Compensation Range: $175K - $225K." Benefits section: "Benefits differ by country. For roles in the United States, Autodesk’s benefits are described at benefits.autodesk.com. For roles in Canada and other countries, the plan differs on health coverage, retirement and leave, and your recruiter will walk you through it." We need to avoid duplication. So we separate. Thus:

  Pay

  Base pay is one part of the package. Depending on the role, compensation may also include commission, an annual bonus and equity. Compensation Range: $175K - $225K.

  Benefits

  Benefits differ by country. For roles in the United States, Autodesk’s benefits are described at benefits.autodesk.com. For roles in Canada and other countries, the plan differs on health coverage, retirement and leave, and your recruiter will walk you through it.

  Now we need to ensure we didn't include any boilerplate like "Belonging. We take pride in a culture where everyone can thrive. More at autodesk.com/company/global-belonging. More on where this is going: Autodesk CEO Andrew Anagnost on building the future of connected operations, and AOS SVP Stephen Hooper on welcoming MaintainX to Autodesk." That is also substantive? It's about belonging and links. Might be considered boilerplate? It's not EEO/legal but could be considered extra. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The belonging paragraph is not explicitly listed but could be considered extra fluff. However it's substantive about culture. Might be okay to keep? The instruction says "Prefer a few substantive sections over many thin ones." This belonging paragraph is thin; we could omit it as it's not essential to role. Safer to omit. Also the sentence "Our mission is to keep the physical world running. Factories, fleets, hospitals and campuses stay up because the people who maintain them have tools worth using. That is what we build." That's also substantive about mission; we could include in About the role maybe. It appears after compensation? Actually appears after "Compensation and benefits." It's a mission statement. Could be included in About the role. We'll incorporate into About the role paragraph. Thus About the role paragraph will include that mission sentence. Let's craft final HTML. We need to ensure no extra whitespace issues. Let's produce:

  About the role

  MaintainX is a leading mobile-first work execution platform for industrial and frontline teams. More than 13,000 customers, including Duracell, McDonald's, Shell, DHL and Volvo, use MaintainX to cut unplanned downtime and run better operations, across 13.9 million managed assets and 79.5 million completed work orders. In August 2026 MaintainX became part of Autodesk, joining