3 of 3 Permanent Model Context Protocol Jobs in Rhondda Cynon Taff

admin position. A. Agentforce Architecture & System Design Solution Architecture: Translate complex enterprise business processes into end-to-end agentic workflows (Intent $rightarrow$ Agent $rightarrow$ Context $rightarrow$ Reasoning $rightarrow$ Actions $rightarrow$ Systems $rightarrow$ Outcome). Core Agent Engineering: Design, configure, and build enterprise agents using Agent Builder, Agentforce Studio, Agent … search, and Knowledge libraries. System Interoperability: Architect REST API callouts, event-driven integrations, and MuleSoft platform pipelines, incorporating Model Context Protocol (MCP) standards. D. Testing, Security & Strategic Advisory Testing & Quality Assurance: Drive automated testing and multi-turn conversation tracing using the Agentforce Testing Center. Security & Guardrails: Design ...

expand into agentic solution delivery and broader business transformation. Our conviction is that engineers are uniquely positioned to lead this transformation. The strongest mental model for designing, deploying, and governing AI agents in production lives in software engineering. The teams that change how their organization builds software … assumptions, risks, milestones, and dependencies Embed with customer teams to co-build agentic applications on the Claude developer platform Build technical artifacts — evaluation frameworks, MCP servers, sub-agents, and deployment configurations — tailored to the customer's stack What Success Looks Like Customers move from proof-of-value to production Engineering ...

moving from a traditional SaaS posture to a platform built around agents - parent agents fronting our compensation data, specialist agents underneath, durable workflows, an MCP-based tool layer, and an eval harness to maintain consistency. You’ll own architecture and technical design across the stack: the customer-facing … have Production experience with agentic systems - tool calling, multi-step orchestration, LLM evals. Workflow engines (Temporal, Cadence, Step Functions) - even if not Temporal specifically MCP, Anthropic SDK, or other LLM platform work Building developer platforms, internal SDKs, or framework-shaped surfaces Eval-driven development, prompt engineering at scale, LLM-judge ...