Senior Front Suspension Design Engineer

About the role

This role advances vehicle programs by defining front suspension systems and interfaces. The position supports concept development through production for aerospace, medical, automotive, and commercial clients.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Component and system engineering requirements guide vehicle programs.

Engineering designs and concepts address customer and supplier expectations.

Packaging, tolerance, and feasibility studies evaluate layout and integration.

CATIA 3Dx, 3D Experience, or V5 produce models, drawings, and releases.

Design, manufacturing, quality, and launch issues resolve to enable smooth product introduction.

Internal cross-functional teams, suppliers, and customers align interfaces and deliverables.

Engineering changes and documentation maintain traceability and compliance.

Concept-to-production vehicle development and problem-solving apply to lifecycle challenges.

Requirements

A bachelor's degree is required for this position.

5 or more years of automotive or commercial vehicle engineering experience within the relevant domain is required.

2 or more years of CAD experience with CATIA 3Dx, 3D Experience, or V5 is required.

Knowledge of torque steer, durability, ground clearance, and serviceability impacts is required.

GD&T and tolerance analysis capability is required.

DFMA principles are applied during design and packaging activities.

Experience comparing carryover, modified, and new design solutions is required.

Problem-solving and root cause analysis methods address technical issues.

Effective communication and teamwork skills are necessary to work with cross-functional stakeholders.

Practical notes

Employment eligibility and background checks apply to all qualified candidates.

Drug screening is required as a condition of hire per federal contractor obligations.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Roles in this field typically involve interpreting engineering requirements and translating them into system architectures.

Design work often focuses on front suspension geometry, packaging, and interface management.

Common analysis methods include tolerance stack-up, durability, and feasibility assessments.

Proficiency with CAD tools and GD&T is essential for developing release-ready documentation.

Collaboration across functions, suppliers, and customers is standard in product development environments.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.