Autodesk SF Seeks Sr Design PM ($142k-$231k+)

To pursue a design program-management role at Autodesk, search the official Autodesk careers site and verify the requisition, team, level, location, salary if published, work model, and application host. Prepare a portfolio that shows how you clarified an ambiguous design problem, aligned product, design, research, engineering, and business stakeholders, created a decision and delivery system, managed risk, and improved a user or operational outcome. The old San Francisco salary headline cannot establish a current role or compensation.

Understand the role

Design program management can coordinate portfolios, roadmaps, research operations, design systems, launches, planning, resourcing, tooling, vendor work, or cross-product initiatives. It is not merely scheduling meetings. The current description determines whether the role sits in product design, experience, design operations, research, or another organization.

Senior scope usually requires operating through influence: defining decision rights, surfacing dependencies, managing ambiguity, establishing cadences, and protecting quality. Candidates should distinguish direct ownership from facilitation and team achievements from personal contribution.

Build a decision-focused portfolio

Use two or three case studies with context, user and business problem, stakeholders, constraints, governance, plan, decision points, risks, artifacts, outcome, and learning. Show the operating mechanism: roadmap, dependency map, research plan, design-system contribution process, launch readiness, risk register, or decision log. Redact confidential information.

Quantify meaningful outcomes such as decision time, delivery predictability, research reuse, accessibility defects, adoption, rework, launch quality, designer capacity, or user success. Avoid claiming direct product impact when attribution is shared.

How to apply and verify

Navigate directly to Autodesk Careers and search design program, experience, design operations, research operations, product program, or the relevant location. Match job ID, title, date, organization, level, location, work model, compensation disclosure, and application domain. Read the candidate privacy statement and use Autodesk’s official accommodation route when needed.

Create a requirement-to-evidence matrix. Tailor the portfolio order to the role’s first three problems. Prepare interview stories on conflicting priorities, a missed dependency, difficult stakeholder, design-quality trade-off, resourcing, an unsuccessful launch, and a system you improved.

Program-management application exercise

Choose a fictional cross-product design initiative. Define goal, non-goals, users, stakeholders, decision owner, milestones, risks, dependencies, review criteria, communication, accessibility, and measurement. Explain how new evidence changes the plan. This demonstrates operating judgement without exposing proprietary work.

Evidence matrix for interviews

Build a one-page matrix with each stated requirement, the strongest project proving it, the artifact you can discuss, the outcome, and one honest limitation. Include an example of resolving conflict without authority, recovering a delayed dependency, and changing a plan after research or accessibility evidence. For every metric, record the baseline, observation period, source, and your contribution. This prevents a polished portfolio from becoming vague storytelling and gives interviewers a traceable account of how you operate.

Engagement checklist

  • Is the role active on Autodesk’s official careers site?
  • Do job ID, team, level, location, and date match?
  • Which design or research programs are in scope?
  • Does the portfolio show decisions and operating systems?
  • Are user and business outcomes measured appropriately?
  • Is individual contribution clear?
  • Are confidential details removed?
  • Are salary, work model, and eligibility official?
  • Is the recruiter/application host verified?
  • Has the current description been saved?

Safety and stale cleanup

Remove the old salary range, “seeks,” deadline, copied requirements, and San Francisco or remote assumptions. Do not publish proprietary roadmaps, research, customer data, or partner information. Date any current role example and retain evergreen evidence guidance after it closes.

FAQ

Is the former senior role still open?

The legacy article cannot prove that. Search Autodesk’s official careers portal.

Is design program management the same as product management?

No. They may collaborate, but decision ownership and responsibilities vary by organization.

What should the portfolio emphasize?

Ambiguity, cross-functional decisions, delivery systems, quality, outcomes, and learning.

Is the old salary still accurate?

Do not assume so. Use a current requisition and formal offer.

Internal links

  • Verified design and product jobs
  • Design-operations portfolio guide
  • Program-management interview hub
  • Job scam-verification checklist

Sources

WorkinVirtual community

Discuss this guide

Ask a useful question, share relevant experience, or add a practical correction. Helpful contributions publish immediately after automated safety checks.

0 public contributions
Keep it useful and safe. No applications, self-promotion, contact details, payment requests, identity documents, harassment, or external links. Job-specific questions belong in the protected “Ask the employer” channel.

Start a thoughtful discussion

Be the first member to add a question or practical insight about this topic.