Principal Backend Software Developer

Autodesk Autodesk · Enterprise · Toronto, ON +2

Autodesk is building a shared AI-assisted commerce platform where AI copilots and agents can discover, recommend, and transact Autodesk offerings. This Principal Backend Software Developer role will design and build the core APIs and orchestration layer (MCP) that connects AI systems to Autodesk’s commerce infrastructure (pricing, subscriptions, entitlements, checkout) with enterprise-grade reliability, security, and governance. The role sits at the intersection of platform engineering, distributed systems, and applied AI enablement.

What you'd actually do

  1. 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)
  2. Create standardized patterns for tool invocation (idempotency, retries, rate limits, validation), error contracts, and deterministic behaviors suitable for LLM/agent workflows
  3. Build adapters and service interfaces to existing commerce capabilities (pricing, subscriptions, entitlements, checkout), including backward compatibility and rollout strategies
  4. Own service SLOs/SLIs, observability (logs/metrics/traces), resilience patterns, and incident readiness; drive post-incident improvements
  5. Implement strong authN/authZ, tenant isolation, secrets management, auditability, policy enforcement, and safe-guardrails around agent actions (approvals, constraints, and traceability)

Skills

Required

  • 10+ years building and operating production backend/platform systems
  • Deep knowledge of distributed systems: scaling, failure modes, consistency, caching, queues/streams, concurrency, idempotency, and backpressure
  • Strong backend proficiency in one or more languages (e.g., Java/Kotlin, Node Js), plus strong API design (REST/gRPC) and data modeling
  • Experience with cloud-native systems (Kubernetes, CI/CD, IaC), and building reliable services with modern observability
  • Proven ability to lead cross-team initiatives through ambiguity, balancing platform correctness, security, and product velocity

Nice to have

  • Experience designing platforms for automation/agents (workflow orchestration, tool routing, policy engines, approvals, audit trails)
  • Commerce domain exposure: pricing catalogs, subscription lifecycle, entitlement checks, tax/payment/checkout flows
  • Multi-tenant enterprise patterns: tenant isolation, RBAC/ABAC, compliance-minded logging, data retention
  • Experience building internal platforms with adoption metrics, SDKs, and versioned contracts

What the JD emphasized

  • enterprise-grade reliability, security, and governance
  • safely discover, recommend, and transact
  • safely and consistently
  • deterministic behaviors suitable for LLM/agent workflows
  • strong authN/authZ
  • safe-guardrails around agent actions
  • integrate agents quickly and safely

Other signals

  • AI copilots and agents
  • commerce platform
  • API and orchestration layer
  • enterprise-grade reliability, security, and governance