1

Senior Solidworks Api Jobs (NOW HIRING)

Generative AI CAD Engineer

Emeryville, CA · On-site +1

$210K - $260K/yr

This posting is not associated with a specific level, but it spans Junior, Senior, and Staff levels ... with Onshape API, SolidWorks API, Fusion API, CadQuery, Build123d, FreeCAD, or similar)

... API compliance regulations, codes, and standards, preferred but not required * Familiarity with manufacturing processes, preferred but not required * CAD Software, AutoCAD, SolidWorks 2016 or newer ...

R&D Mechanical Engineer, Senior

Spring, TX · On-site

$95K - $126K/yr

Experience in SolidWorks (or equivalent CAD software) and Microsoft Office, used for 3D modeling ... Experience with industry standards such as API (American Petroleum Institute), ISO (International ...

next page

Showing results 1-20

Senior Solidworks Api information

See salary details

$59.5K

$126.6K

$183.5K

How much do senior solidworks api jobs pay per year?

As of Aug 28, 2026, the average yearly pay for senior solidworks api in the United States is $126,557.00, according to ZipRecruiter salary data. Most workers in this role earn between $104,500.00 and $143,500.00 per year, depending on experience, location, and employer.

What is the difference between Senior Solidworks Api vs Solidworks Mechanical Designer?

AspectSenior Solidworks ApiSolidworks Mechanical Designer
Required SkillsAdvanced API scripting, programming, automationMechanical design, CAD modeling, drafting
Work EnvironmentSoftware development, engineering teamsDesign departments, product development
CertificationsSolidworks certifications, programming coursesSolidworks certifications, mechanical engineering degrees
Industry UsageAutomation, custom tool developmentProduct design, prototyping

The main difference is that a Senior Solidworks Api specializes in scripting and automating tasks within Solidworks using APIs, while a Solidworks Mechanical Designer focuses on creating and modifying 3D models and drawings. The API role requires programming skills and automation expertise, whereas the designer role emphasizes mechanical design skills and CAD proficiency.

More about Senior Solidworks Api jobs

What cities are hiring for Senior Solidworks Api jobs?

Cities with the most Senior Solidworks Api job openings:

What are the most commonly searched types of Solidworks Api jobs?

The most popular types of Solidworks Api jobs are:

What states have the most Senior Solidworks Api jobs?

States with the most job openings for Senior Solidworks Api jobs include:

Infographic showing various Senior Solidworks Api job openings in the United States as of August 2026, with employment types broken down into 89% Full Time, 3% Part Time, and 8% Contract. Highlights an 75% Physical, 6% Hybrid, and 19% Remote job distribution, with an average salary of $126,557 per year, or $60.8 per hour.

Senior Software Engineer, CAD Interoperability

Zoo

Los Angeles, CA • On-site, Remote

Full-time

Re-posted 13 days ago


Job description

About The Role

We're looking for a Senior Software Engineer, CAD Interoperability, who can help build the systems that convert native and proprietary CAD formats into Zoo's KCL, our new programming language for 3D design. You'll work at the intersection of CAD data extraction, geometry processing, and code generation, turning models from third-party CAD systems into structured KCL representations. This role is for someone who enjoys digging into complex CAD systems, working with CAD SDKs and APIs, and building robust import pipelines that preserve model structure and design intent as much as possible.

What You'll Do
  • Design, implement, and maintain import pipelines that convert native and proprietary CAD formats into Zoo's KCL.
  • Build systems for extracting feature information from CAD files and applications, including sketches, dimensions, constraints, parameters, feature trees, assemblies, metadata, PMI, and related design intent.
  • Develop extractors using native CAD application APIs and toolkits where interoperability SDKs are insufficient.
  • Translate extracted CAD structure, geometry, parameters, and feature information into KCL that faithfully represents the original model.
  • Build validation, testing, and comparison tools to measure conversion quality across geometry, topology, feature information, assemblies, and generated KCL output.
  • Handle edge cases across proprietary formats, CAD versions, modeling kernels, malformed files, incomplete metadata, and inconsistent vendor API behavior.
  • Collaborate with the file format, modeling, and product teams to improve Zoo's CAD import experience and expand support for real-world customer files.
What You'll Need
  • B.S. in Computer Science, Mechanical Engineering, or a related field, or equivalent experience.
  • Strong professional experience in software engineering, ideally involving CAD, geometry, file formats, code generation, or data extraction systems.
  • Experience working with complex technical data formats, application APIs, SDKs, or translation pipelines.
  • Proficiency in a systems programming language such as Rust or C++, with comfort working across language boundaries and vendor SDKs.
  • Experience building automated tests, validation tools, and debugging workflows for complex technical systems.
  • Ability to work autonomously, investigate unfamiliar systems, and make pragmatic technical decisions in a fast-moving environment.
Nice to Have
  • Strong understanding of CAD model structure, including parts, assemblies, sketches, constraints, dimensions, features, parameters, B-rep geometry, and tessellated representations.
  • Experience with CAD interoperability SDKs such as HOOPS Exchange, CoreTechnologie 3D_Kernel_IO, Open Design Alliance, CAD Exchanger, Datakit, or similar tools.
  • Experience with native CAD APIs such as SOLIDWORKS API, Creo TOOLKIT, NX Open, CATIA CAA/API, Inventor API, or similar.
  • Experience with STEP, IGES, Parasolid, ACIS, JT, glTF, STL, or other CAD and 3D exchange formats.
  • Experience generating structured source code from model data, especially for DSLs or domain-specific modeling languages.
  • Familiarity with KCL or other programmatic CAD workflows.