Finding a Sales Job in Engineering Software: A Candidate’s Guide

Roles and customers: know what you would sell

This guide covers selling engineering software—not providing engineering designs. Autodesk describes its CAD software as supporting two-dimensional drafting and three-dimensional design or modeling. That description applies to its products, not every engineering tool. See the Autodesk CAD overview.

When evaluating openings, distinguish CAD workflows from simulation capabilities. Ask whether the product supports drawing, modeling, analysis, collaboration, or another task. Do not assume it proves design safety or exchanges every file without loss.

• SDR: Investigate prospecting expectations, account qualification, and handoffs to account executives.
• Account executive: Clarify ownership of discovery, demonstrations, evaluations, commercial negotiation, and closing.
• Account management: Determine whether the job emphasizes renewals, adoption, expansion, or all three.

Ask who uses, evaluates, approves, and purchases the software. Potential stakeholders to investigate include engineers, CAD managers, engineering leaders, IT, procurement, and finance. Establish how technical validation and purchasing approval affect the sales cycle.

Where and how to search

Search for specific combinations: “CAD software account executive,” “engineering software SDR,” “simulation software sales,” “CAE account manager,” and “technical software sales.” Add your actual location or “remote United States,” then verify eligible states, travel expectations, and working hours.

Browse Salesfolks sales jobs alongside your targeted search. Read descriptions for product and customer fit rather than relying on job titles.

• Identify whether the employer sells its own software, resells another vendor’s products, or bundles implementation services.
• Check which customer workflows the role serves: for example, mechanical design, drafting, or simulation evaluation.
• Ask whether accounts are assigned by geography, customer segment, industry, or named-account list.
• Confirm whether demonstrations require travel and who supplies technical expertise.

Build a shortlist around workflows you can explain or learn credibly—not simply familiar product names.

Evidence to prepare

Use a resume that separates your contribution from team results. Report only outcomes you can substantiate, with relevant context such as territory, deal ownership, and measurement period. If you lack engineering software experience, show transferable discovery, multi-stakeholder selling, or technical learning without claiming engineering credentials.

A hypothetical sales-work exercise

Prepare a one-page evaluation plan for a hypothetical engineering team considering a drawing or model workflow. Use synthetic material, not a former employer’s confidential files.

1. Discovery: Ask what the team creates, which tools it uses, and where revisions or handoffs cause difficulty.
2. Representative task: Propose opening a sample drawing or model, making an agreed change, and exchanging the specified file format.
3. Validation: Ask the customer to define acceptance criteria, such as required dimensions, annotations, geometry, or revision information surviving the workflow.
4. Support and next step: Identify when an application specialist must assist, record unresolved limitations, and agree who evaluates the results.

Limit your conclusions to the agreed drawing or modeling task; do not present this exercise as evidence of simulation capability or design safety. Present your plan as a discovery artifact, not proof of product performance.

Evaluate compensation beyond the headline

Request the written compensation plan before accepting. Separate guaranteed base pay from variable compensation and ask what must happen for commission to become payable.

• Quota: What revenue or activity counts, and how are renewals, services, and shared deals credited?
• Attainment: What proportion of comparable, fully ramped representatives reached quota in the most recent completed period? What were their territories and tenure?
• Ramp: When does full quota begin, and what training or temporary guarantees apply?
• Draw: Is it recoverable or nonrecoverable? Ask for a written explanation and worked payout example.
• Adjustments: How do cancellations, payment delays, caps, accelerators, and account reassignment affect earnings?

For salary research, use the BLS occupational wage tables. Select the occupation that best matches actual duties, then check geography and data year. A broad national occupation is not a local salary quote or a software-sales commission benchmark.

Interview questions and due diligence

Ask for concrete examples rather than accepting labels such as “technical sale” or “strong pipeline.” Request anonymized information when customer confidentiality matters.

• For an SDR role: “What makes a meeting qualified, who accepts it, and how are rejected handoffs reviewed?”
• For an AE role: “Walk me through an evaluation that stalled. Which buyer, technical requirement, or purchasing step blocked progress?”
• For account management: “How are renewal risk, adoption work, and expansion credit divided across teams?”
• For any role: “Who is the user, technical evaluator, budget owner, and final approver?”
• Pipeline and territory: “What would I inherit, how was it qualified, and which accounts are excluded?”
• Manager support: “How often do you coach discovery and review deals? When can I involve an application specialist?”

Also ask what happens when a requested file exchange or simulation requirement cannot be supported. Look for a clear process for testing limitations and communicating them honestly.

Warning signs and common search mistakes

• Vague technical promises: If an interviewer implies universal interoperability, ask how formats, versions, and acceptance criteria are validated.
• Unclear earnings: Replace enthusiasm about top earners with questions about comparable representatives, written crediting rules, and ramp.
• Undefined technical support: Ask who builds demonstrations and handles specialist questions; do not assume you must answer everything yourself.
• Overstating your expertise: Instead of presenting yourself as an engineer, demonstrate disciplined discovery and appropriate escalation.
• Generic applications: Tailor your opening paragraph to the product workflow and customer segment, not a copied list of software terms.
• Excessive unpaid work: Propose a bounded, synthetic exercise rather than supplying a live prospect list or confidential customer analysis.

Compare offers with a usable checklist

Mark each item as confirmed, unclear, or unacceptable. Resolve important unknowns in writing rather than hiding them inside a total score.

Hypothetical comparison: Offer A advertises higher target earnings but leaves account allocation unresolved. Offer B has a written territory and scheduled specialist support. Neither automatically wins: ask A to clarify allocation, then compare realistic earning conditions and your ability to perform the work.

A one-week candidate action plan

1. Monday: Choose your preferred role and two engineering workflows to investigate.
2. Tuesday: Build a focused employer shortlist and verify location and travel requirements.
3. Wednesday: Tailor your resume and label every performance claim with its context.
4. Thursday: Complete the hypothetical evaluation exercise and rehearse a short explanation.
5. Friday: Submit targeted applications and record your questions for each employer.
6. Saturday: Practice role-specific interview answers and compensation questions.
7. Sunday: Review responses, identify knowledge gaps, and schedule appropriate follow-ups.

Candidate FAQs

Do I need an engineering degree?

Check each opening’s requirements. Ask which technical tasks you must perform independently and which belong to specialists. Describe your qualifications accurately.

Can I move from another B2B sales industry?

Show how you learn unfamiliar workflows, qualify competing priorities, and coordinate evaluations. Pair transferable experience with a relevant, clearly hypothetical work sample.

Should I memorize product features before interviewing?

Learn enough to ask informed questions, but prioritize buyer problems, evaluation steps, and product boundaries. Never claim an unverified capability to sound knowledgeable.

Sources and relevant next steps

Use the linked Autodesk overview for its stated CAD scope, not as an endorsement or evidence about other vendors. Research occupation tasks through O*NET OnLine; compare those tasks with the actual job description. Recheck BLS geography, occupation, and year when researching wages.

Verify changing product capabilities, compensation terms, travel requirements, and territory rules directly with each employer. To continue your search, create a Salesfolks account and prepare a focused application package: an honest resume, a workflow-specific work sample, and your unanswered interview questions.

Employer perspective: Hiring Salespeople for Engineering, CAD and Simulation Software.