Applied AI Engineer – Agentic AI & Automation

About Us: Xpedeon is an integrated purpose-built ERP Suite contributing to digital transformation in the construction and engineering industry across the globe.

Backed by more than two decades of industry experience, Xpedeon has been helping businesses to scale up efficiency, increase profitability, and maximize margins in today’s dynamic business environment. Our integrated solution stack addresses the unique requirements and challenges of building contractors, civil engineering contractors, specialist contractors, and housebuilders by simplifying their business systems with our powerful, comprehensive suite.

More than 30,000 users have gained quantum leaps in productivity and control, improving their operational efficiency and growing their bottom line with Xpedeon.

Job Description: Applied AI Engineer - Agentic AI & Automation

Team: Product Engineering (AI Platform)

Reports to: Engineering Lead

Level: Mid–Senior

About the role

We’re extending our AI platform beyond answering questions into agents that take real action on a user’s behalf executing multi-step tasks, calling internal and external tools/APIs, and completing work that has actual consequences if done wrong. This is a different discipline from building a Q&A or retrieval system: the central engineering problem is safety and reversibility under autonomy, not just answer quality. You’ll design how the agent decides what it’s allowed to do, how it recovers when a multi-step task fails partway through, and when it must stop and ask a human before proceeding.

What you’ll do

• Design and build multi-step agent execution loops that plan, call tools/APIs, observe results, and adapt not single-shot prompt/response.
• Build the tool-calling layer: define what actions an agent can take, with strict schemas and validation on every tool invocation before it executes.
• Design authorization and scoping so an agent can only take actions within an explicit, auditable allowlist never inferring permission from context or “the user probably meant.”
• Build human-in-the-loop approval flows: identify which actions are safe to auto-execute versus which require explicit user/operator confirmation before running and design the UX/API for that checkpoint.
• Design for partial failure: make multi-step tasks idempotent and resumable, so a crash or timeout mid-task doesn’t leave data in an inconsistent or duplicated state and build rollback/compensating actions where true undo isn’t possible.
• Build comprehensive audit logging of every action an agent takes what it decided, what tool it called, what the result was, and why sufficient to reconstruct and explain any outcome after the fact.
• Implement rate limiting, circuit breakers, and hard stop conditions so a misbehaving agent loop can’t run away (excessive retries, repeated failed actions, runaway cost/API usage).
• Write test suites that simulate multi-step task execution, including deliberate failure injection at each step, to prove the agent handles partial failure and unauthorized-action attempts correctly not just that the happy path works.
• Collaborate with product/ops stakeholders to define which actions are in scope for automation at all, and which should remain human-only regardless of technical feasibility.
• Monitor agents in production for anomalous behavior (unexpected tool calls, repeated failures, actions outside historical patterns) and build alerting around it.

Required qualifications

• 3+ years of professional software engineering experience, with strong backend proficiency (Python or comparable).
• Experience building systems that call external or internal APIs with real side effects — not read-only integrations. (Payments, provisioning, order/workflow systems, infra-automation, RPA any domain where “the call executed” matters.)
• Experience designing for idempotency and safe retries in distributed or multi-step systems.
• Experience with authorization/permission modeling scoping what a given actor (human or automated) is allowed to do and enforcing it centrally rather than trusting caller intent.
• Hands-on experience with LLM tool-calling/function-calling APIs and building the orchestration logic around them (not just prompting a chat model).
• Strong instincts for failure-mode thinking given any action, can you name what goes wrong if it runs twice, runs out of order, or fails halfway and design for it up front.
• Experience building audit/logging systems sufficient for …