Software architects for AEC data platforms design systems that keep building, infrastructure and operational data usable across products and time. Autodesk’s current official Software Architect roles describe APIs, schemas, event streams, batch and streaming systems, backward compatibility, reliability, security, performance, observability and cross-team alignment. Some postings are EMEA offsite or include a specific Canadian remote location, proving that remote eligibility is requisition-specific. The candidate’s central artifact should be a decision trail showing how requirements, domain semantics, failure modes and migration constraints shaped an architecture. The old “competitive package” vacancy is not a current offer.
Evidence that demonstrates fit or progress
Design an authorized or invented AEC asset-data service. Include domain glossary, entities and relationships, API contract, event schema, versioning and migration, tenant isolation, identity, encryption, data retention, lineage, privacy, failure modes, observability, SLOs, cost and disaster recovery. Write two architecture decision records and a compatibility test demonstrating how an old client survives schema evolution. Add a threat model and runbook. Use synthetic data; do not copy building models, customer projects, credentials, vulnerabilities or employer architecture. Explain assumptions and what would require domain, security, legal or operations review.
Build a requirement-to-evidence matrix with requirement, proof, result and gap columns. Copy a current requirement or operating need into the first column. Add one truthful example and a verifiable result. Label missing proof as a gap instead of hiding it with keywords. Legal status, health, safety, schedule, location, privacy, accessibility or security mismatches require a decision.
Write two short cases containing context, constraint, personal action, quality or safety check and result. Reduce each to one résumé, plan or portfolio bullet. Keep confidential clients, systems, employees, health information and security details out. A credible sanitized example is stronger than detail that should not be public.
How to apply or use the guidance
Create a matrix of ten official architecture roles recording employer, product domain, approved location, offsite/hybrid rule, architecture scope, cloud, data and security expectations, individual-contributor versus management level and compensation basis. Match each repeated requirement to an artifact section. In interviews, ask who owns production, how decisions gain adoption, how schemas evolve, what SLOs matter, how security reviews work and which meetings require location overlap. Apply through official portals, save the requisition and verify salary currency and residence before investing in a tailored application.
Verification checklist
- Open the official employer, government or primary source.
- Confirm current status, document or requisition ID and the date checked.
- Record legal, location, eligibility, deadline, privacy and work-model constraints.
- Compare mandatory criteria with evidence that can be substantiated.
- Identify one decisive gap before spending more time or money.
- Save the source, decision, accountable owner and fallback.
- Stop when payment, secrets, unsafe access or unofficial transfer of sensitive information is demanded.
Practical exercise and decision aid
Create a next-48-hours card with one verification, one evidence improvement and one communication action. At the end, mark completed, learned and changed. This creates a return reason and keeps the page useful when a legacy vacancy, product claim or simplistic promise is removed.
Use a stop/continue table. Continue when the official source is current, core requirements fit and the next cost is reasonable. Pause when legal status, health, location, accessibility, safety, security, privacy or money is unclear. Stop when an accountable party is hidden, payment is demanded for a job, or normal verification is bypassed.
Safety and stale-content cleanup
Remove the historical vacancy’s active status, package claim and universal remote implication. Do not present a diagram as proof of operability or a certification as architecture authority. Cloud products, job locations and compensation change. Avoid exposing client AEC data or security weaknesses. Remove active JobPosting schema. Use dated official examples, Article/FAQ schema and a maintenance log. Security, privacy, construction-data and cross-border issues need qualified review in the actual organization.
- Replace urgency and guaranteed outcomes with dated verification.
- Do not infer remote work from a digital role or site brand.
- Keep employer, government, manager, worker and tool roles distinct.
- Put official or primary sources ahead of copied pages.
- Do not collect identity, bank, health, immigration or security data.
- Recheck canonical, robots, schema, outbound links and dates in QA.
- Keep unpublished if the intent cannot be served honestly.
Frequently asked questions
Can AEC software architects work remotely?
Some roles are offsite or remote in named regions; the exact requisition controls eligibility.
What is the strongest portfolio artifact?
A decision-backed system design with schemas, migration, security, SLOs, failure recovery and tradeoffs.
Can customer building data be shown?
Not without authorization; synthetic or public licensed data is safer.
Does certification prove architecture skill?
No. Employers need evidence of decisions, adoption, operability and measurable outcomes.
Official and primary sources
- Autodesk Software Architect AEC Data — official or primary evidence for scope, status, safeguards or application.
- Autodesk Software Architect AEC Platform Data — official or primary evidence for scope, status, safeguards or application.
- Autodesk Tech Careers — official or primary evidence for scope, status, safeguards or application.
- NIST Cybersecurity Framework — official or primary evidence for scope, status, safeguards or application.
- FTC Job Scams — official or primary evidence for scope, status, safeguards or application.
Research checked 2026-08-09. Organization and guidance pages establish context; only an accountable live source establishes a current vacancy, rule, price or individual recommendation. Evidence is applied within its limits and does not guarantee outcomes.