Aras rewards people who think in data models, and its functional and technical split does not map from other PLM platforms. Scoping that correctly is most of what makes an Aras search work.
Aras Innovator is a model-based PLM platform with a low-code architecture and a subscription model that includes upgrades of customisations. That combination has made it the platform of choice for organisations that want to shape PLM around their process rather than reshape their process around the platform, particularly in defence, aerospace and complex industrial manufacturing.
The talent pool is correspondingly younger and smaller than the established platforms. Birch Hill recruits Aras specialists for Aras itself, its partner network, system integrators and manufacturers running Innovator in production.
Aras rewards people who think in data models. The screening questions below reflect that.
In Aras, almost everything is an ItemType, including the things that define other things. Candidates who grasp this build cleanly. Candidates who treat Aras as a conventional application with a database behind it build badly, and it shows within months.
Data modelling is the core skill. Designing ItemTypes, RelationshipTypes and property structures that match a real manufacturing process without becoming unmaintainable is the work.
Aras Markup Language, the XML dialect used to query and update. Fluency in AML is a reliable signal that someone has worked inside Aras rather than alongside it.
Server-side methods in C# and JavaScript, client-side JavaScript, Actions, Forms, Grids and TOC configuration, plus the REST and OData interfaces used for integration.
Workflow maps, lifecycle states, and the Identity and Team model that governs access. Permission design in Aras is more flexible than most platforms and correspondingly easier to get wrong.
Aras upgrades customisations as part of subscription. Candidates who understand what that covers, and which customisation patterns stay within it, design very differently from those who do not.
In Windchill or Teamcenter, functional and technical work separate cleanly. In Aras they overlap, because the platform\'s configuration surface reaches further into what would elsewhere be development. Specifications written from a Windchill mental model tend to mis-scope Aras roles.
Translates manufacturing business process into the Aras data model: which ItemTypes exist, how they relate, what the lifecycle looks like. What to evaluate: ask them to describe an ItemType structure they designed and what they would change now. In Aras this role does substantially more modelling than its equivalent on other platforms, so a purely process-facing background is usually insufficient.
Owns platform architecture, performance, integration strategy and upgrade-safe design. What to evaluate: ask which customisations they kept inside the supported upgrade path and which they accepted as out of scope, and why. That trade-off is the centre of the job.
Builds server methods in C#, client-side behaviour in JavaScript, and works directly in AML. What to evaluate: ask for a method they wrote and what they did with the result. AML fluency is the quickest authenticity check in this market.
Spans functional and technical, usually in a partner or client-facing setting. What to evaluate: whether they can hold both a business process conversation and a data model conversation in the same meeting without handing off.
Aras has grown quickly but its experienced implementation population remains much smaller than Windchill\'s or Teamcenter\'s. Searches that would be routine on an established platform require a far wider net and a more direct approach here.
Organisations moving to Aras from another platform frequently write Aras job descriptions in Windchill or Teamcenter terms. The functional and technical split does not map across, and the resulting specification attracts the wrong shortlist.
Some candidates know Aras well but have thin manufacturing process background. Others know product development deeply but have never modelled an ItemType. Deciding which gap you can close internally is the key scoping decision, and it should be made before the search starts, not during it.
The Aras partner network recruits from the same small pool constantly. A manufacturer hiring directly needs a sharper proposition than title and salary, usually around ownership, scope or the chance to design something from scratch.
Every Aras candidate is asked to describe a structure they designed and defend it. AML fluency and ItemType reasoning are established before anyone reaches your shortlist.
Because the line sits differently in Aras, we agree what the role actually is before sourcing begins. That conversation prevents most failed Aras searches.
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 architect decides what the model should be: which ItemTypes exist, how they relate, what the lifecycle and workflow look like, driven by how the business actually builds product. A technical architect decides how the platform delivers it: performance, integration, and which customisations stay inside the supported upgrade path. In Aras these overlap more than on other platforms, because the configuration surface reaches further into what would elsewhere be development work.
Partially. PLM process knowledge, change management and BOM thinking all carry over and are valuable. The model-based architecture does not: candidates who approach Aras as a conventional configurable application rather than as a modelling platform tend to build structures that become unmaintainable. Expect a real ramp and screen for whether the person thinks in data models.
The platform's experienced implementation population is substantially smaller than Windchill's or Teamcenter's, and demand from the partner network is continuous. A search that would be routine on an established platform needs a wider net, a more direct approach and realistic expectations about timeline.
That someone has worked inside Aras rather than near it. AML is used constantly in real implementation work and almost never learned from documentation alone. It is the fastest authenticity check we have in this market, which is why we ask about it early.
Decide before the search starts, because you will rarely get both. If your process is complex and unusual, domain depth matters more and Aras skills can be developed. If you are on a deadline with a defined scope, platform experience matters more. Organisations that refuse to choose run long searches and usually end up compromising under time pressure anyway.
Yes, alongside manufacturers running Innovator directly. Partner-side and client-side Aras roles differ considerably in pace, breadth and client exposure, and we match candidates to the setting where they will actually perform.
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 Aras Innovator 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