Software Architect

Autodesk Autodesk · Enterprise · Melbourne, Australia +10 · Remote

Autodesk Construction is seeking a Software Architect to define the technical direction for their Payment Solutions platform. This role involves guiding modernization efforts, decomposing legacy systems, and influencing the design of scalable, reliable, and maintainable systems. The architect will partner with engineering, product, and design teams to translate business needs into technical strategy and establish architectural patterns and standards. The role requires strong experience in client-server architectures, distributed systems, and modern cloud technologies, with a focus on improving system observability, performance, and security.

What you'd actually do

  1. Define and evolve the architecture for Autodesk Construction's Payment Solutions platform, with a focus on scalability, reliability, maintainability, and product velocity
  2. Partner with engineering, product, and design leaders to translate business and domain complexity into clear technical strategy
  3. Guide modernization efforts, including decomposition of legacy systems, clearer domain boundaries, reusable platform capabilities, and safer migration paths
  4. Establish architecture patterns, technical standards, and decision-making practices that teams can adopt consistently
  5. Lead design reviews and architectural discussions across teams, helping engineers evaluate trade-offs and make pragmatic decisions

Skills

Required

  • 8+ years of professional software engineering experience
  • designing and delivering complex production systems
  • client-server architectures
  • distributed systems
  • APIs
  • data modeling
  • service boundaries
  • designing systems that span multiple teams, services, applications, or product areas
  • hands-on technical leader in an individual contributor capacity
  • balancing long-term architecture direction with incremental delivery
  • modern frontend, backend, and cloud technologies
  • React
  • Angular
  • TypeScript
  • JavaScript/Node.js
  • .NET
  • AWS
  • excellent written and verbal communication skills
  • mentoring engineers
  • raising the technical quality of teams

Nice to have

  • payments
  • construction technology
  • ERP systems
  • financial workflows
  • compliance-heavy systems
  • Domain-Driven Design concepts in large-scale systems
  • decomposing monoliths into modular monoliths, services, microservices, or micro-frontends
  • defining architecture decision records, reference architectures, reusable components, or engineering standards
  • cloud architecture
  • observability
  • reliability practices
  • SLOs
  • performance tuning
  • secure system design
  • improving developer experience through better tooling, patterns, documentation, or technical en

What the JD emphasized

  • modernizing a successful platform
  • reducing legacy complexity
  • defining clearer domain boundaries
  • improving developer experience
  • evolving our architecture toward more modular, resilient, and extensible systems
  • complex production systems
  • complex business domains
  • modernizing legacy systems