Job Requisition ID #
25WD93562
Position Overview
Autodesk Construction is looking for a Software Architect to help shape the technical direction of Payment Solutions, a business‐critical product area that helps owners, general contractors, and subcontractors manage progress payments with greater transparency, accuracy, and efficiency.
Construction Payments Context
Construction payments are complex. They involve multi‐party collaboration, financial controls, compliance requirements, contract structures, approval workflows, integrations, and enterprise‐scale platform architecture across the construction ecosystem. Our platform helps customers navigate that complexity and gives project stakeholders better visibility into payment progress, risk, and outcomes.
Strategic Individual Contributor
This is a strategic, hands‐on individual contributor role. You will work across engineering, product, and design teams to define architecture, guide modernization, and influence how teams build scalable, reliable, secure, and maintainable systems. You will not be managing people, but you will be expected to lead through technical direction, architectural judgment, mentoring, and close partnership with engineering teams.
Platform Modernization
We are actively modernizing a successful platform. That means reducing legacy complexity, defining clearer domain boundaries, improving developer experience, and evolving our architecture toward more modular, resilient, and extensible systems. Depending on the problem, that may include modular monolith patterns, service decomposition, microservices, micro‐frontends, event‐driven architecture, or other pragmatic architectural approaches.
Technology Stack
Our current technology stack includes React and Angular on the frontend, with JavaScript, TypeScript, Node.js, .NET, and related backend technologies. Our services are deployed in AWS. As Payment Solutions continues to evolve into a broader platform, we need an architect who can simplify complexity, create durable technical direction, and help teams make high‐quality decisions that balance long‐term architecture with incremental delivery.
Success Looks Like
* In your first 3 months, you will understand the Payment Solutions domain, current architecture, key modernization goals, and major technical constraints. You will build relationships across engineering and product teams, identify high‐impact architectural opportunities, and begin contributing to design reviews and technical direction.
* In your first 6 months, you will help define and drive architecture initiatives that reduce legacy complexity, improve domain boundaries, and create clearer patterns for frontend and backend development. You will establish practical architecture guidance that teams can use, and you will be actively influencing implementation across multiple product areas.
* In your first 12 months, you will have helped move the platform toward a more modular, observable, reliable, and maintainable architecture. Teams will be able to deliver payment‐related capabilities with greater confidence, clearer ownership, and less friction from legacy systems.
Responsibilities
* Define and evolve the architecture for Autodesk Construction's Payment Solutions platform, with a focus on scalability, reliability, maintainability, and product velocity.
* Partner with engineering, product, and design leaders to translate business and domain complexity into clear technical strategy.
* Guide modernization efforts, including decomposition of legacy systems, clearer domain boundaries, reusable platform capabilities, and safer migration paths.
* Establish architecture patterns, technical standards, and decision‐making practices that teams can adopt consistently.
* Lead design reviews and architectural discussions across teams, helping engineers evaluate trade‐offs and make pragmatic decisions.
* Influence implementation quality through technical guidance, code reviews, mentoring, and close partnership with engineering teams.
* Improve system observability, performance, reliability, and security across critical payment workflows.
* Break down medium‐ and long‐term technical initiatives into incremental milestones that teams can execute safely.
Minimum Qualifications
* 8+ years of professional software engineering experience, including experience designing and delivering complex production systems.
* Strong understanding of client‐server architectures, distributed systems, APIs, data modeling, and service boundaries.
* Experience designing systems that span multiple teams, services, applications, or product areas.
* Ability to work as a hands‐on technical leader in an individual contributor capacity.
* Strong judgment in balancing long‐term architecture direction with incremental delivery.
* Experience with modern frontend, backend, and cloud technologies, such as React, Angular, TypeScript, JavaScript/Node.js, .NET, AWS, or similar stacks.
* Excellent written and verbal communication skills, with the ability to explain technical decisions, trade‐offs, and architecture direction to technical and non‐technical audiences.
* Experience mentoring engineers and raising the technical quality of teams.
* Empathy, curiosity, and respect for teammates, customers, and cross‐functional partners.
Preferred Qualifications
* Experience with payments, construction technology, ERP systems, financial workflows, compliance‐heavy systems, or other complex business domains.
* Experience applying Domain‐Driven Design concepts in large‐scale systems.
* Experience modernizing legacy systems, including decomposing monoliths into modular monoliths, services, microservices, or micro‐frontends.
* Experience defining architecture decision records, reference architectures, reusable components, or engineering standards.
* Experience with cloud architecture, observability, reliability practices, SLOs, performance tuning, or secure system design.
* Experience improving developer experience through better tooling, patterns, documentation, or technical enablement.
* Interest in sharing knowledge through technical talks, design reviews, mentoring, or engineering community engagement.
#J-18808-Ljbffr