Software Architect - remote job

Autodesk is hiring a Software Architect. The role sits in IT and programming and is fully remote. The company hires candidates based in Europe.

The employer did not publish a figure; that is settled at interview. The advert sets no condition on working hours.

This vacancy passed an automated check: the list excludes any advert requiring a foreign work permit, visa sponsorship, a particular citizenship, or residence in a specific country.

Job Requisition ID # 26WD94957

Position Overview

Autodesk builds 3D design, engineering, and entertainment software used by creative people solving real problems. Fortune, Forbes, Glassdoor and others rank it a top employer. The company works to keep its workplace diverse and inclusive, so innovation and creativity can grow.

The Architecture, Engineering, and Construction (AEC) Data organization wants a seasoned Software Architect. You will join the AEC Data team and set the cloud-native service and distributed-systems architecture behind the AEC Data Model (AECDM) and its surrounding services.

Data is the subject matter, but the work itself is cloud and services architecture across many teams: APIs, service contracts, integrations, distributed-systems design, and the connected data model holding it together. It is not a data-warehouse or analytics-specialist position.

AEC Data is assembling the base data infrastructure for Autodesk's connected construction vision: platforms, services, and unified data models covering the whole built-asset lifecycle, from design and construction into operation and maintenance. That lets AEC data keep flowing (3D models, 2D drawings, issue tracking, cost, sensor streams, and more) between Autodesk products and third-party integrations. You will help form the next wave of capability for the Autodesk Forma Industry Cloud, working alongside software architects, domain experts, and product teams from Revit, Civil 3D, AutoCAD, Autodesk Construction Cloud, and Autodesk Forma.

The position is a senior individual-contributor spot on an established architecture track. You report to the AEC Data team's Distinguished Architect, who is also the Lead Software Architect. Your main job is influencing how several teams design and build, via standards, reference architectures, ADRs, and design-review governance, rather than owning one service yourself. Where you focus can shift toward your strengths and what the organization needs.

Responsibilities

* API Design & Evolution: Shape and grow the API surfaces across AEC Data services, covering resource modeling, addressing, versioning and backward-compatible evolution, query APIs, and folding overlapping surfaces into one coherent contract.

* System Architecture: Set and develop cross-team, cloud-native architecture over the AEC Data services; design distributed systems, including service contracts and event-driven flows.

* Schema Design & Evolution: Build, document, and grow data schemas for AEC domain entities (buildings, infrastructure, spaces, systems, components, relationships), covering semantic models, property sets, classification systems, and relationship hierarchies. You own versioning, backward and forward compatibility, deprecation, and migration, plus the schema registry, validation rules, and quality checks.

* Standards & Governance: Set standards, reference architectures, and reusable components; write architecture proposals and decision records (ADRs) that a cross-org architecture council reviews, and run design reviews spanning teams.

* Prototyping & Feasibility: Weigh alternative architectural directions with modeling and prototyping, taking risk out of big decisions before wide rollout.

* Mentorship & Technical Leadership: Coach engineers and other architects on both new and established technologies and on architectural practice; deepen technical skill across teams.

* Reliability & Performance: Keep systems reliable, secure, and fast; set SLOs and push observability (metrics, tracing, logging).

* Communication: Explain architecture through clear views and diagrams (e.g. C4) and narratives fit for executives; write thorough documentation and onboarding material.

Minimum Qualifications

* Bachelor's degree in Computer Science, or comparable experience.

* 10+ years building cloud-native, distributed systems, with 5+ years of that at cross-team architect altitude (Software Architect, Principal Engineer, Staff+, or similar). The title is flexible; what counts most is the scope of your impact.

* Deep command of cloud services (AWS preferred), API and service design, and distributed-systems patterns (microservices, event-driven, resilience).

* Firm footing in data modeling and schema design, covering schema definition languages (e.g. JSON Schema), versioning, and backward/forward-compatibility and evolution strategies, applied both to standalone data schemas and to API contracts. Specialist data-warehouse or analytics architecture is not needed.

* Strong knowledge of software design and architecture patterns.

* Proven skill at influencing without authority and pulling teams outside your own reporting line into alignment.

* Strong leadership and mentoring, with a record of guiding and growing diverse, cross-functional teams.

* Mastery at putting complex ideas across concisely and persuasively, with excellent verbal, written, and presentation skills for varied stakeholders.

* Able to work with a global team.

Preferred Qualifications

Treat the preferred list as a menu, not a checklist: depth in a few core areas counts for more than a light touch on all of them. The emerging AI/ML items below help but can be learned on the job; they are not prerequisites.

Core:

* Cloud Services: AWS and its core services (EC2, ECS, Lambda, API Gateway, S3, DynamoDB, RDS).

* Distributed Systems: Domain-driven service decomposition, data consistency patterns (CQRS, event sourcing, sagas), and multi-tenant/multi-region design.

* API & Service Design: REST API design and evolution; GraphQL, federation included.

* Database Architecture: Relational and NoSQL (e.g. DynamoDB, PostgreSQL).

* Observability/SRE: OpenTelemetry, distributed tracing, metrics/SLOs for data services.

Bonus:

* Semantic Technologies: Knowledge graphs, RDF/OWL, or property graphs, which bear directly on the connected/semantic AECDM.

* BIM Expertise: Building Information Modeling concepts, Revit families, or comparable parametric modeling systems.

* AI Systems: RAG, agents/MCP, agentic orchestration (LangGraph, Semantic Kernel), LLM observability, and data governance / AI safety (PII, prompt-injection, content filtering).

* Domain-Specific AI for AEC: BIM/IFC extraction, CAD or point-cloud processing.

* Event-Driven Architectures: Kafka or Kinesis; schema registries (Confluent, AWS Glue); exactly-once processing.

* AEC Domain Knowledge: Time spent in the Architecture, Engineering, and Construction industry; familiarity with industry standards (IFC, COBie, gbXML, CityGML, LandXML, UniFormat, OmniClass). Domain onboarding is provided.

About the Team

The AEC Data team is building the AEC Data Model (AECDM) so AECO (Architecture, Engineering, Construction, Operations) outcomes improve through data that is more useful, connected, and reachable. Its remit covers data services and APIs, product and design-tool integrations, and lifecycle/asset data across several teams, so information moves smoothly between Autodesk products and third-party integrations and AEC professionals can decide better with better data.

Why Join Us

* Set the direction of AEC data platforms and standards at a company that leads its industry.

* Design systems and schemas that millions of architects, engineers, and construction professionals use worldwide.

* Work with world-class software architects and engineers from across Autodesk's AEC portfolio.

* Add to open standards and interoperability efforts that lift the whole industry.

* Join a team that prizes technical excellence, innovation, and continuous learning.

Learn More

About Autodesk…