Autodesk
PrincipalBackendSoftwareDeveloper
Neural analysis suggests this role is
optimal for Senior candidates.
“Principal Backend Software Developer at Autodesk. Skills: Commerce platform, AI enablement, Distributed systems. Design runtime and APIs. Create standardized patterns”
What You'll Achieve.
AI copilots reliably complete tasks; Integrations become simpler and faster; Platform reliability improves measurably
Industry & Context.
Root cause analysis
What They're Looking For.
Must Have
10+ years backend/platform systems, Deep knowledge of distributed systems, Backend proficiency in Java/Kotlin/Node.js, API design (REST/gRPC), Data modeling, Cloud-native systems (Kubernetes, CI/CD, IaC), Building reliable services with modern observability, Lead cross-team initiatives
Nice to Have
Designing platforms for automation/agents, Commerce domain exposure, Multi-tenant enterprise patterns, Building internal platforms
What You'll Do.
Design runtime and APIs
Create standardized patterns
Build adapters and service interfaces
Own service SLOs/SLIs
Implement authN/authZ
Drive architecture decisions
Lead design reviews/RFCs
How You'll Work.
Team & Collaboration
Cross-team initiatives; Across teams
Full Job Description
**Job Requisition ID #** 26WD96355 _L 'affichage de poste en français suivra / The French job posting follows._ **26WD96355, Principal Backend Software Developer** **Position Overview** Autodesk is building a shared AI-assisted commerce platform that enables AI copilots and agents to safely discover, recommend, and transact Autodesk offerings. As a Principal Developer you will design and build the core APIs and orchestration layer (MCP) that connects AI systems to Autodesk’s commerce infrastructure—pricing, subscriptions, entitlements, and checkout—with enterprise-grade reliability, security, and governance. This role sits at the intersection of platform engineering, distributed systems, and applied AI enablement. **Responsibilities** * Design and implement the runtime and APIs that allow copilots/agents to invoke commerce capabilities safely and consistently (e.g., product discovery → pricing → eligibility/entitlements → checkout) * Create standardized patterns for tool invocation (idempotency, retries, rate limits, validation), error contracts, and deterministic behaviors suitable for LLM/agent workflows * Build adapters and service interfaces to existing commerce capabilities (pricing, subscriptions, entitlements, checkout), including backward compatibility and rollout strategies * Own service SLOs/SLIs, observability (logs/metrics/traces), resilience patterns, and incident readiness; drive post-incident improvements * Implement strong authN/authZ, tenant isolation, secrets management, auditability, policy enforcement, and safe-guardrails around agent actions (approvals, constraints, and traceability) * Provide SDKs, documentation, reference implementations, and golden paths so product teams can integrate agents quickly and safely * Drive architecture decisions across teams, lead design reviews/RFCs, mentor developers, and influence roadmaps across the commerce + AI ecosystem **Minimum Qualifications** * 10+ years building and operating production backend/platfor
Applying for this Principal Backend Software Developer role?
Most applicants get filtered before a human reads their resume. See if yours makes the cut.
How to Apply on Workday
- Workday has a multi-step form — save your progress after every section.
- "Apply With LinkedIn" can fail or lose data; manual entry is more reliable.
- Watch for the "Submit for Review" final step — hitting "Save" alone does not submit.
- Job requisition numbers are useful when following up with HR by email.
ANONYMOUS · UNFILTERED
What do employees actually say about Autodesk?
Real rants from real employees. Read before you apply.