As a Solution Architect - ERP / EAM, you sit at the intersection of product strategy, deep solution knowledge, and real‑world customer process understanding. You are part of a small, high‑calibre team whose purpose is to accelerate IFS’s ability to deliver meaningful value through AI, agentic capabilities, and digital workers — embedded directly into ERP and EAM workflows. This is not a generic presales or product management role. It is a specialist position designed for individuals who understand IFS ERP and EAM at depth: down to the business process, down to the sub‑process, and in many cases down to the functional object, data model, or workflow component level. You will use that knowledge to identify where emerging IFS capabilities — including IFS Loops, digital workers, and the IFS agentic AI platform — can generate real, verifiable customer value.
Role Description
This role requires a senior individual contributor who operates across product, engineering, sales, and customer conversations. The primary alignment sits within the IFS product organisation, with a close working relationship to R&D and a dotted‑line into sales and go‑to‑market. The role requires fluency in both the language of engineering and product, as well as in customer outcomes and commercial opportunity. The individual will help shape what gets built, validate whether it works, and communicate what it means—to internal stakeholders and to customers alike. In short, this role exists to ensure that IFS’s most advanced ERP and EAM capabilities are delivered into the right contexts, in the right way, with the right supporting evidence.
Operating Model & Time Allocation
This role operates across four primary dimensions. The split below reflects a realistic working rhythm, though the balance will shift based on business cycle and opportunity:
- 30%: Customer‑facing support – active opportunities, strategic conversations, and “what next” engagements with key accounts.
- 30%: Product organisation collaboration – process mapping, solution design, and Loops / digital worker opportunity identification within ERP and EAM.
- 20%: Engineering engagement – validation, feasibility assessment, and pre‑release pressure‑testing of proposed capabilities.
- 20%: Research, self‑development, and internal enablement – staying current with IFS platform direction, ERP/EAM domain trends, and Industrial AI advances.
IFS ERP Portfolio Depth (Mandatory)
Candidates must demonstrate genuine, hands‑on depth across the IFS ERP portfolio. This is a non‑negotiable requirement. Experience across core IFS ERP functional areas – including financials, supply chain, manufacturing, procurement, and project‑based operations – is expected, whether gained as an IFS employee, IFS partner professional, or in a customer‑side implementation role.
IFS Cloud / IFS Applications Experience
Practical working experience with IFS Cloud and/or IFS Applications, with the ability to operate at functional and process level, not simply at a conceptual overview.
ERP & EAM Process Fluency
Demonstrable ability to work at the level of detailed business processes and sub‑processes in ERP and EAM environments. Understanding of how these processes connect, depend on each other, and create operational outcomes.
IFS EAM Familiarity
Strong working knowledge of IFS EAM‑related capabilities is highly desirable. Candidates who can operate across both ERP and EAM process domains are strongly preferred.
AI & Automation Orientation
Genuine curiosity and working understanding of how AI, agentic capabilities, and workflow automation tools can be applied inside complex enterprise processes. Ability to identify opportunity areas and assess their practical viability.
Cross‑Functional Credibility
Proven ability to work effectively with product managers, engineers, sales leaders, and senior customer stakeholders. Comfortable challenging assumptions and bringing clarity to ambiguous situations.
Communication & Articulation
Ability to communicate complex product and process concepts clearly, credibly, and concisely – to both technical and non‑technical audiences.
