Senior Contract Software Engineer - PLM/CAD Integrations

At Dalus, we're building AI-powered software to reimagine how complex hardware systems are designed — think rockets, satellites, EVs, aircraft, nuclear plants.

Right now, companies building these systems are held back by legacy tools that were never built for today’s fast-paced engineering teams. We’re changing that. Our platform makes hardware development faster, safer, and more scalable, even with smaller teams. We believe that designing atoms should feel more like working with bits — and that the next industrial renaissance needs better software.

Dalus is building a hardware system design platform to make hardware as fast to build as software. We're hiring a senior contract software engineer to build integrations between Dalus and enterprise engineering tools — starting with PLM (Windchill, Teamcenter, 3DEXPERIENCE, Aras) and extending to CAD (NX, Creo, SolidWorks, Onshape, Fusion) and requirements tools (Jama, Polarion, DOORS, via OSLC where possible).

This is a hands-on integration-engineering role. You'll write the API clients, the sync logic, and handle auth, revisions, and partial failures against locked-down enterprise systems. Engineering discipline comes first; PLM/CAD domain knowledge second.

This is a fully remote contract role

What you'll do

• Build and own production integrations between Dalus and PLM/CAD/requirements tools
• Write API clients and sync logic; handle enterprise auth, revisions, effectivity, and partial failures
• Build against mocks first when sandboxes aren't available in customer environments

Must have

• 4+ years shipping production backend services in a team codebase with CI, code review, and tests
• Strong in TypeScript and/or Python; comfortable wrapping Java or C# vendor SDKs at the edge
• At least one real integration built against a PLM or CAD API — you wrote the client, the sync logic, and handled auth, revisions, and partial failures (not just configuration or workflows)
• Understands engineering data: parts vs revisions, EBOM/MBOM, effectivity, change objects, CAD structure vs product structure
• Experience working in locked-down enterprise environments (VPN-only access, customer IT ticket cycles, no sandbox) and a method for building against mocks first

Strong signals

• Worked at a hardware-tooling or PLM-adjacent company or on a vendor's own integration/platform team rather than a services practice
• Familiar with OSLC, OData, SOAP, SAML/Kerberos enterprise auth
• Public code on GitHub or open-source contributions in this space
• Any exposure to SysML, MBSE, or the SysML v2 API

Screen-outs

• "PLM consultants" whose experience is configuration, workflow setup, or migration projects with no custom code
• Engineers who can only work in Java or C# end to end
• Agency profiles with no individual engineer named