Principal Software Engineer

Autodesk Autodesk · Enterprise · Atlanta, GA +1

Autodesk is seeking a Principal Software Engineer to provide technical leadership for their next-generation Content Platform. This role involves designing and operating distributed backend systems, workflow orchestration, and high-throughput content delivery on AWS, with a focus on Python and schema-driven data pipelines. While the role primarily focuses on platform engineering, there is exposure to AI/ML-driven content workflows.

What you'd actually do

  1. Set the technical direction for the Content Platform's core subsystems and drive architectural alignment across the multi-repo workspace
  2. Translate ambiguous product and partner requirements into concrete platform capabilities, schema extensions, and workflow patterns, and document the tradeoffs for engineering and product leadership
  3. Design and review complex changes to the workflow framework (BaseWorkflow, APIWorkflow, annotation-driven fan-out, registries) and the single-table DynamoDB model, ensuring correctness under concurrency, versioning, and locale semantics
  4. Lead cross-team initiatives that span ingestion, workflow orchestration, delivery, and content modeling; identify and resolve systemic issues in reliability, performance, and developer productivity
  5. Establish and evolve engineering standards for the platform and coach engineers across teams to adopt them Partner with senior leaders, architects, DevOps, Support, and product organizations to advise on platform strategy, capacity planning, and incident response

Skills

Required

  • Bachelor's degree in Computer Science or a related field, or equivalent practical experience
  • 8+ years of professional software development experience, including significant time at a senior or staff level designing and operating distributed backend systems in production
  • Deep proficiency in Python, including experience designing libraries and frameworks consumed by other engineering teams
  • Hands-on experience designing and operating workflow orchestration systems (Temporal, Cadence, Airflow, Step Functions, or equivalent) at production scale
  • Strong expertise with AWS, including Lambda, DynamoDB (single-table design and GSIs), S3, and event-driven integrations
  • Expertise in REST API design and implementation with frameworks such as FastAPI, including schema validation, versioning, and backwards compatibility
  • Demonstrated ability to design data models and schemas and to drive system behavior from declarative configuration
  • Track record of leading architecture and design across multiple teams or repositories, and of influencing technical direction through written design docs and stakeholder communication

Nice to have

  • Experience building headless CMS, content delivery, or large-scale content ingestion platforms, including integration with third-party CMSs such as Contentful
  • Familiarity with immutable versioning, locale-per-item modeling, and hot-path delivery optimization on DynamoDB or similar NoSQL stores
  • Experience with plugin/connector frameworks and source-agnostic ingestion patterns (acquire → extract → transform → deliver)
  • Background in developer experience and platform tooling: uv, internal package registries, monorepo or multi-repo developer workflows
  • Experience operating regulated or multi-region environments (e.g., FedRAMP sync, cross-region replication, compliance-driven data handling)
  • Exposure to AI/ML-driven content workflows, including embeddings, search relevance, or content enrichment pipelines

What the JD emphasized

  • workflow orchestration systems (Temporal, Cadence, Airflow, Step Functions, or equivalent) at production scale
  • AWS, including Lambda, DynamoDB (single-table design and GSIs), S3, and event-driven integrations
  • REST API design and implementation with frameworks such as FastAPI, including schema validation, versioning, and backwards compatibility
  • Track record of leading architecture and design across multiple teams or repositories, and of influencing technical direction through written design docs and stakeholder communication