A resume that says Windchill is compatible with at least four different careers. We establish which one you are looking at before anybody reaches your shortlist.
PTC Windchill is the enterprise PLM backbone for manufacturers who cannot afford to lose a revision. It holds the part structure, governs the change process, manages CAD data from Creo and other authoring tools, and feeds manufacturing and service through ERP integration.
Birch Hill recruits Windchill specialists for PTC, its value-added resellers, system integrators and the manufacturers running Windchill in production. We screen on what someone actually did inside the platform, because a resume that lists Windchill is compatible with at least four distinct careers.
These are the areas we probe in a technical screen. The depth we look for depends on the role, but a candidate who cannot discuss the relevant ones specifically does not reach your shortlist.
Part-centric versus CAD-centric data models, EBOM to MBOM transformation, where the manufacturing view diverges from engineering, and why that decision is expensive to revisit.
Problem Reports, Change Requests, Change Notices and Change Tasks, and how an organisation\'s real approval process maps onto them without creating a process nobody follows.
Lifecycle templates, workflow templates, team templates and Object Initialization Rules. OIR design in particular separates people who configured Windchill from people who watched it being configured.
Creo integration through Workgroup Manager, family tables, dependency handling, and the behaviour of CAD documents against part structures.
Java customisation, Info*Engine tasks, listeners and validators, custom UI, and Windchill REST Services. The critical judgment is which extensions survive an upgrade and which create permanent technical debt.
ERP integration to SAP or Oracle through ESI or middleware, plus version upgrade experience. Having carried a customised environment through an upgrade is one of the clearest signals of real depth.
This is the distinction that decides whether your search succeeds. Below each role is the question we ask to establish whether a candidate genuinely holds it.
Owns the end-to-end design: data model, lifecycle strategy, integration approach and the decisions that are expensive to reverse later. What to evaluate: ask them to describe a design decision they got wrong and what it cost to unwind. An architect who has never had to live with their own decision is a designer, not an architect.
Translates engineering process into platform configuration: workflows, lifecycles, OIRs, access control. What to evaluate: ask how they handled a change process the business described one way and practised another. The answer separates configuration skill from process judgment.
Designs and builds customisation and integration in Java and Info*Engine. What to evaluate: ask what they refused to customise and why. Strong Windchill developers are defined as much by what they kept out of the platform as by what they built into it.
Runs the environment: users, permissions, performance, patches and upgrades. What to evaluate: ask whether they have taken a customised environment through a major version upgrade. That single experience is worth more than years of routine administration.
The most common Windchill requisition we see wants architecture judgment, configuration skill, Java customisation and administration in one hire, at one compensation level. That person exists and is rare enough that you are competing with PTC and every partner simultaneously.
Five years of Windchill can mean five years of designing enterprise deployments or five years of resetting passwords. Both are written the same way. Without a technical screen that probes OIRs, change objects and upgrade history, you cannot tell which you are interviewing.
Experienced Windchill consultants are employed by PTC or its partner network and are usually mid-engagement. They are reachable, but by direct approach from someone who can discuss their work credibly, not by a job alert.
Plenty of people have implemented Windchill. Far fewer have carried a heavily customised environment across a major version boundary. If your environment is customised, that experience should be a hard requirement, and it narrows the field sharply.
Every Windchill candidate is placed into architecture, configuration, development or administration before they reach you, with evidence. You see a shortlist for the job you are actually filling.
We track which resellers and integrators are growing, which are losing people, and who is doing the Windchill work in your region. That map is where the search starts.
If the scope, compensation or location will not attract the person you described, you hear it during the intake call rather than after a quarter of silence.
Candidates get honest market context and are never submitted anywhere without consent. That is why specialists who are not looking still return our calls.
A functional consultant configures the platform to match a business process: workflows, lifecycles, Object Initialization Rules, access control. A technical consultant writes code against it in Java and Info*Engine to do things configuration cannot. Both describe themselves as Windchill consultants. Hiring one when you needed the other is the most common and most expensive Windchill hiring error.
If you are designing a deployment, setting the data model, or deciding how Windchill will connect to ERP, you need an architect. If the design exists and the work is configuring it to match how your engineers actually work, a functional consultant is the right hire and usually the better value. Many organisations advertise for an architect and describe a consultant's job.
If your environment is customised, treat it as a hard requirement. Upgrading a stock Windchill installation is routine. Upgrading one carrying years of Java customisation is a different exercise, and someone who has done it will design extensions differently from someone who has not. It is the single most useful filter we apply.
The PLM concepts transfer. The platform does not, at least not quickly. Change object models, configuration tooling and customisation approaches differ enough that a strong Teamcenter consultant needs a genuine ramp on Windchill. Worth considering for a multi-year programme where process judgment matters most. Not worth it if you need productivity in month one.
All three. The distinction matters because the jobs differ: partner-side consultants work across many clients at pace, manufacturer-side specialists go deep into one environment over years. Strong performers in one setting often struggle in the other, and matching that correctly is a large part of what we do.
At minimum: how they approached Object Initialization Rules, how they structured the change process using Problem Reports and Change Notices, what they customised and what they deliberately did not, and whether they have taken a customised environment through an upgrade. Those four questions separate real depth from exposure faster than anything else we have found.
Every search is run directly by Tim Lohse. No hand-offs, no junior sourcers, no resume dumps. If the role is scoped in a way that will not attract the Windchill talent you need, we will say so before you spend three months finding out.
Replacing someone, or exploring a role you have not announced. Handled discreetly from first call.
Start a Confidential SearchAn open role you need filled with someone who contributes from day one.
Hire Digital Thread TalentA search that has stalled, or one other firms have returned nothing usable on.
Discuss a Hard-to-Fill RoleMarket intelligence, compensation reality and scoping. No obligation.
Schedule a Consultation