CAD & PLM Application Specialist Siemens NX/Teamcenter
CAD - Villeneuve, CH
The position
- Crew
- CAD
- Location
- Villeneuve, CH
- Type of contract
- Full-time
Your role
Every LYOBA part starts as an NX model and ends as flight hardware, and the Teamcenter data model that carries it between those two points now needs someone who owns it full time.
PAVE Space is building LYOBA, a heavy kick stage moving up to 4-ton payloads from LEO to high-energy orbits in under 24 hours. Getting there means hundreds of parts moving through design, review, release, procurement and build. That whole path runs through NX and Teamcenter, and you’d be the one keeping it clean and connected to the tools we build in-house.
So, why now?
We’ve defined how a part moves from concept to production, including design reviews with manufacturing readiness built in, drawing reviews, make/buy decisions and change classes. The tools now have to enforce that process instead of relying on people to remember it, and they have to talk to our in-house apps and AI agents. A BMIDE change or API you deploy this week sets how every engineer creates and releases parts next week, so your work shows up in days.
You will own
The Teamcenter data model in BMIDE: business objects, properties such as part rigor, usage and make/buy, LOVs, naming rules, and clean deployment from test to production
The NX managed-mode environment (seed parts, drawing templates, customer defaults, reference sets, load options) along with the CAD standards and onboarding that keep every engineer working the same way
Release and change: Workflow Designer processes, access rules, and change lifecycles from Initial through Class 1 and Class 2
The APIs that move part, BOM and change data between Teamcenter and our in-house procurement and build apps, in both directions
MCP servers on top of Teamcenter, so AI agents and our in-house tools can read parts, BOMs and change status and write back under the same access rules a human user has
Hands-on CAD on LYOBA hardware when the program needs another pair of hands in NX
What we are looking for
5+ years using Siemens NX and Teamcenter in a production engineering environment, as a designer and as an administrator
You’ve configured a Teamcenter data model in BMIDE yourself and deployed the templates, not only requested changes from IT
Built or reworked release and change workflows, including handlers, ACLs and revision rules
Deep knowledge of NX in managed mode and how EBOM data flows from it into procurement and manufacturing
You’ve built integrations against Teamcenter’s services (SOA, REST/Active Workspace gateway, or ITK) that write data back as well as read it
Production code in Python, Java or C#, and either an MCP server or comparable agent tool interface you’ve shipped, or code that shows us you could
Fluent English (our working language)
Nice to have: Active Workspace configuration (XRT stylesheets), NX Open automation, Dispatcher and JT/PDF translation, Teamcenter upgrades or Linux administration, Teamcenter integrations with ERP or MES, ASME Y14.5 drawing standards, aerospace or space hardware experience, Siemens Teamcenter certification.
You will fit if
You’d rather fix the data model once than answer the same CAD support question every week.
You can say no to a custom property nobody will fill in, and explain why to the engineer who asked for it.
You still model parts in NX, so you know where the integration hurts because you’ve felt it as a user.
You treat revision rules and naming conventions with the care a designer gives to tolerances.
Before letting an agent write to the PLM system, you’ve already thought through permissions, audit trail and how to roll it back.
The role is fully on-site in Villeneuve (VD), because the engineers using what you configure sit a few desks away and the fastest feedback loop is walking over. The environment is early: some of the data model will be rebuilt rather than extended, and you’ll be the first person dedicated to it, working directly with engineering, manufacturing and our software team. What makes that worth it: every part on LYOBA, from a bracket to a propellant tank, will carry the structure you set, from its first model to flight hardware. You also get to decide how AI agents work with engineering data here, at the point where that’s still being designed rather than patched.
We are building to ship, grounded on real hardware, real funding, real milestones. Apply to contribute, or pass this to the NX/Teamcenter engineer you know who has been waiting to build an environment the right way.