BC Solution Architect
Permanent • Full-time • Remote — UK or EMEA
Most BC implementations have the same gap. There is a lead consultant who knows the functional domain, and a project manager who tracks the timeline. But nobody owns the technical design — what the solution actually looks like, how it integrates, where the extensions start and the configuration ends, and whether the data migration is built on something that will hold. On the projects where it goes wrong, that gap is usually why.
We are building a BC partner where the Architect role is structural, not honorary. If you have been operating as the senior technical mind on BC implementations — defining the solution design, owning integration architecture, and making the calls that determine whether a project lands cleanly — this is the role we are building around.
The Role
Title: BC Solution Architect
Type: Permanent employee
Location: Remote — UK or EMEA (project travel as required)
Start: Pipeline building now — first engagements Q3 2026
Growth path: Senior IC with structured path to leading a small delivery team
What You’ll Do
You are the technical design authority across Hybrid AI Solutions engagements. In practice that means:
- Owning solution architecture on complex implementations — multi-entity, multi-currency, integration-heavy — where functional delivery alone is not enough.
- Defining the boundary between configuration, AL extension, and ISV — and producing design artefacts that make that boundary explicit and change-controlled.
- Designing integrations — REST/OData, Power Platform, Azure Logic Apps, or third-party iPaaS — and validating they are implementable before they appear in a scope document.
- Providing technical authority in presales — reviewing prospect environments, flagging complexity, and making the technical case in front of the client.
- Setting and enforcing technical standards across the partner — not just on your current engagement, but as the baseline for how Hybrid AI Solutions delivers.
- Maintaining the Hybrid AI Solutions ISV register — the assessed and approved library of add-ins for document management, warehousing, EDI, and reporting.
- Directing AI tooling on technical artefacts — integration specs, extension scope documents, migration plans — and maintaining the quality bar on output.
What We Need
If the list below does not describe your current capability, this is not the right role.
- 7+ years BC or NAV implementation experience, with at least 3 years in a senior technical or architect capacity.
- Deep knowledge of BC architecture: database layer, application layer, AL extension model, and where configuration ends and development begins.
- Hands-on integration experience — REST/OData APIs, Power Platform, Azure integration services, or equivalent.
- Full lifecycle data migration experience: schema design, transformation, AL or RapidStart loading, and rigorous validation on complex open-entry migrations.
- MB-800 certified; MB-820 (Developer Associate) strongly preferred.
- Track record of producing and owning technical design artefacts — architecture documents, integration specs, data migration plans.
Why This Is Different
- The Architect role is structural here. Technical design authority is built into the delivery model, not an afterthought when something goes wrong.
- Cross-engagement scope. You set technical standards across the partner, not just on a single project. Decisions you make become methodology.
- Real conditions for good delivery. Every engagement runs on a phase-gated methodology with formal scope control. The Architect’s sign-off is a named gate — not optional.
- Growth path. The role is structured to evolve: as the partner scales, you lead a small delivery team. That transition is planned, not incidental.
- Early-stage influence. We are at the partner-building stage. If you want a stake in how a BC delivery model develops — not just a seat in one that is already fixed — that opportunity is real.
Also Valued
- AL development capability — enough to define scope, review output, and make informed build-vs-buy decisions.
- BC Manufacturing experience: production orders, BOMs, routings, capacity planning.
- ISV ecosystem familiarity: Continia, TaskLet, Warehouse Insight, Jet Reports, or equivalent.
- Experience with cloud migration: on-premises NAV to BC SaaS.
Interested?
Send a brief note and your CV to careers@hybridsolutions.ai. No covering letter required.
We do want to know: the implementation where the technical design made or saved the project — and what your role in it was.
Hybrid AI Solutions Ltd | BC Implementation Partner | EMEA | hybridsolutions.ai
…