Remote UX work for AI and developer platforms requires more than polished screens. Designers must understand technical users, incomplete mental models, system feedback, failure and recovery, permissions, data handling, accessibility and collaboration with engineering. Autodesk’s current official UX Designer, Platform Data posting illustrates a Canada role connected to AEC data APIs, services and interfaces, but every requisition controls its named locations and remote conditions. Treat the old $94K–$137.5K range and “lead AI developer experiences” vacancy as expired. Build evidence around research-to-decision traceability, interaction states, accessible prototypes and measurable usability rather than an employer-specific salary page.
Evidence that demonstrates fit or progress
Create a sanitized developer workflow case using a public API or invented platform. State user, job, research method, constraints, current journey and success measure. Prototype authentication, permissions, empty/loading/error/partial-success states, undo or confirmation for destructive actions, keyboard flow, focus order, labels, contrast and help. If AI is involved, show uncertainty, source or evidence access, correction, human approval and incident reporting. Test five representative tasks with consent, record errors and revisions and distinguish observation from inference. Never expose participant identity, proprietary research, unreleased product, tokens, customer data or confidential model behavior.
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
Review ten official Canada postings and capture permitted provinces, named offices, remote/hybrid label, time-zone overlap, travel, research scope, portfolio requirement, accessibility responsibility, AI/developer domain and compensation currency. Tailor the portfolio landing page to the role with problem, contribution, evidence, tradeoffs, outcome and what changed after testing. Ask who the users are, how designers access them, how accessibility is tested, how AI failures are disclosed and which residence rules apply. Apply only through the employer portal and never provide government ID or banking data before verified onboarding.
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 old vacancy’s active status, salary, “remote Canada” generalization and active JobPosting schema. Do not claim WCAG conformance from automated checks alone or imply that a visual redesign proves usability. AI features, employer locations and compensation change; date examples and verify each requisition. Do not fabricate research participants or metrics. Use Article/FAQ schema after editorial review and include a portfolio privacy checklist. Canadian employment, accessibility and privacy questions require relevant qualified guidance.
- 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
What distinguishes AI-product UX?
Uncertainty, evidence, correction, permissions, failure recovery and human approval must be designed explicitly.
Is automated accessibility testing enough?
No. Standards-based checks and human evaluation, including disabled users where possible, are needed.
Does Canada remote mean every province?
No. Verify permitted provinces, offices and time-zone rules on the exact requisition.
What portfolio data is unsafe?
Participant identity, proprietary research, customer data, tokens, unreleased designs and confidential metrics.
Official and primary sources
- Autodesk UX Designer Platform Data Canada — official or primary evidence for scope, status, safeguards or application.
- Autodesk Tech Careers — official or primary evidence for scope, status, safeguards or application.
- W3C WAI Tutorials — official or primary evidence for scope, status, safeguards or application.
- W3C Understanding Conformance — 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.