{"schemaVersion":"jobsearcher.job.v1","id":"88dc67ac4999996bd7ac9f4e","url":"https://jobsearcher.com/jobs/88dc67ac4999996bd7ac9f4e","canonicalUrl":"https://jobsearcher.com/jobs/88dc67ac4999996bd7ac9f4e","title":"AWS AgentCore Platform Engineer","description":"Position : AWS AgentCore Platform EngineerLocation : Reading, PA (Hybrid 2-3 days/wk at client office6-12+ months contract• Python (3.11+): Hands-on experience building robust applications and agentic logic.• Amazon SageMaker Unified Studio (SMUS) & MLOps: Hands-on experience with SMUS to manage the end-to-end ML lifecycle. This includes automating model training, registering models in the centralized registry, and configuring real-time/asynchronous inference endpoints within the SMUS ecosystem.• Infrastructure as Code (IaC):Production-level expertise using Terraform to provision AWS services, including Bedrock Agents, Knowledge Bases, DynamoDB, Lambda, etc.• CI/CD & DevOps: Proven track record in building and maintaining automated deployment pipelines for cloud-native applications and MLOps workflows.• AWS Security & Identity: Deep experience with IAM for fine-grained permissions and secure service communication.• AWS Bedrock AgentCore : Familiarity with the latest ecosystem, specifically the Agent Runtime, Memory, Identity, and Tool Gateway layers.• Multi-Agent Orchestration: Experience building or enabling collaborative systems using frameworks like LangGraph, strands, etc.• Model Context Protocol (MCP): Strong understanding of MCP and modern tool/API integration patterns for AI agents.• AWS Certification (Optional): Holding one or more AWS Professional-level certifications—specifically the AWS Certified AI Practitioner or AWS Certified Machine Learning – Specialty—is highly preferred and considered a strong plus.• Continuous Learning: Willingness to learn emerging AI technologies, frameworks, and evolving cloud services.Please check if the next candidate has some experience with at least 50% of below items:• Implementation of Agents on Agentcore runtime• Implementation of Agentic SDLC in Agentcore• Understanding of Strands or any other Agentic AI framework like Langraph, Langchain or Crew AI• Implementation of Bedrock Knowledge Base• Implementation of Knowledge Graph• Implementation of MCP servers in Agentcore• Implementation of Agentcore Gateway• Implementation of Agentcore Identity• Implementation of Agentic AI Observability• Implementation of Agentcore Evaluations• Implementation of AWS Bedrock• Implementation of AWS Bedrock Inference Profile• Implementation of AWS Sagemaker• AWS Services (Cloud) in General• TerraformObservabilityAssess CloudWatch, X-Ray, Bedrock logging, AgentCore traces vs. agentic workflow requirements; produce gap analysis, Setup observability in DynatraceDesign post-deployment validation pipeline for agents & MCP servers (deployment health + tool registration checks)Implement distributed tracing & structured logging: LLM decisions, tool selections, sub-agent calls, MCP interactionsEvaluate LangFuse / LiteLLM proxy vs. AWS-native; deliver target-state observability architecture recommendationCost Tracking & TCOExtend tagging taxonomy to cover agent runtimes, MCP servers, vector DBs, Bedrock token consumption per namespaceDesign cost visibility model: aggregate agent, MCP, vector DB, and Bedrock token costs per team/departmentBuild CloudWatch (or equivalent) dashboards for per-team spend; configure AWS Budgets with alerting thresholdsAutomate cost reports delivered via email / Microsoft Teams; implement anomaly detection rulesMonitoring & AlertingDefine P1–P4 alerting rules: deployment failures, runtime errors, tool invocation failures, MCP connectivity issuesIntegrate alert notifications to Microsoft Teams channels and email; route by resource ownership tagsAuthor runbooks linked to every alert; publish in Confluence for developer self-service resolutionEvaluate AWS-native vs. third-party monitoring stack; deliver recommendation aligned to observability architectureSecurity & Access ControlAssess current IAM + tagging approach for multi-team isolation; identify scalability gaps and risksEvaluate Cedar policy engine (AgentCore) for fine-grained tool access control; document enterprise-scale gapsDesign scalable ABAC-based identity model for multi-team isolation without IAM policy sprawl; deliver Terraform modules","company":"Glove","rawCompany":"glove","city":"Reading","state":"PA","isRemote":false,"isActive":false,"createdAt":"2026-10-29T08:08:35.042Z","occupations":[{"code":"15-1299.08","title":"Computer Systems Engineers/Architects","slug":"computer-systems-engineers-architects"},{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1211.00","title":"Computer Systems Analysts","slug":"computer-systems-analysts"}],"industries":[{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"AWS AgentCore Platform Engineer","description":"Position : AWS AgentCore Platform EngineerLocation : Reading, PA (Hybrid 2-3 days/wk at client office6-12+ months contract• Python (3.11+): Hands-on experience building robust applications and agentic logic.• Amazon SageMaker Unified Studio (SMUS) & MLOps: Hands-on experience with SMUS to manage the end-to-end ML lifecycle. This includes automating model training, registering models in the centralized registry, and configuring real-time/asynchronous inference endpoints within the SMUS ecosystem.• Infrastructure as Code (IaC):Production-level expertise using Terraform to provision AWS services, including Bedrock Agents, Knowledge Bases, DynamoDB, Lambda, etc.• CI/CD & DevOps: Proven track record in building and maintaining automated deployment pipelines for cloud-native applications and MLOps workflows.• AWS Security & Identity: Deep experience with IAM for fine-grained permissions and secure service communication.• AWS Bedrock AgentCore : Familiarity with the latest ecosystem, specifically the Agent Runtime, Memory, Identity, and Tool Gateway layers.• Multi-Agent Orchestration: Experience building or enabling collaborative systems using frameworks like LangGraph, strands, etc.• Model Context Protocol (MCP): Strong understanding of MCP and modern tool/API integration patterns for AI agents.• AWS Certification (Optional): Holding one or more AWS Professional-level certifications—specifically the AWS Certified AI Practitioner or AWS Certified Machine Learning – Specialty—is highly preferred and considered a strong plus.• Continuous Learning: Willingness to learn emerging AI technologies, frameworks, and evolving cloud services.Please check if the next candidate has some experience with at least 50% of below items:• Implementation of Agents on Agentcore runtime• Implementation of Agentic SDLC in Agentcore• Understanding of Strands or any other Agentic AI framework like Langraph, Langchain or Crew AI• Implementation of Bedrock Knowledge Base• Implementation of Knowledge Graph• Implementation of MCP servers in Agentcore• Implementation of Agentcore Gateway• Implementation of Agentcore Identity• Implementation of Agentic AI Observability• Implementation of Agentcore Evaluations• Implementation of AWS Bedrock• Implementation of AWS Bedrock Inference Profile• Implementation of AWS Sagemaker• AWS Services (Cloud) in General• TerraformObservabilityAssess CloudWatch, X-Ray, Bedrock logging, AgentCore traces vs. agentic workflow requirements; produce gap analysis, Setup observability in DynatraceDesign post-deployment validation pipeline for agents & MCP servers (deployment health + tool registration checks)Implement distributed tracing & structured logging: LLM decisions, tool selections, sub-agent calls, MCP interactionsEvaluate LangFuse / LiteLLM proxy vs. AWS-native; deliver target-state observability architecture recommendationCost Tracking & TCOExtend tagging taxonomy to cover agent runtimes, MCP servers, vector DBs, Bedrock token consumption per namespaceDesign cost visibility model: aggregate agent, MCP, vector DB, and Bedrock token costs per team/departmentBuild CloudWatch (or equivalent) dashboards for per-team spend; configure AWS Budgets with alerting thresholdsAutomate cost reports delivered via email / Microsoft Teams; implement anomaly detection rulesMonitoring & AlertingDefine P1–P4 alerting rules: deployment failures, runtime errors, tool invocation failures, MCP connectivity issuesIntegrate alert notifications to Microsoft Teams channels and email; route by resource ownership tagsAuthor runbooks linked to every alert; publish in Confluence for developer self-service resolutionEvaluate AWS-native vs. third-party monitoring stack; deliver recommendation aligned to observability architectureSecurity & Access ControlAssess current IAM + tagging approach for multi-team isolation; identify scalability gaps and risksEvaluate Cedar policy engine (AgentCore) for fine-grained tool access control; document enterprise-scale gapsDesign scalable ABAC-based identity model for multi-team isolation without IAM policy sprawl; deliver Terraform modules","datePosted":"2026-10-29T08:08:35.042Z","dateModified":"2026-10-29T08:08:35.042Z","hiringOrganization":{"@type":"Organization","name":"Glove","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Reading","addressRegion":"PA","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"88dc67ac4999996bd7ac9f4e"},"url":"https://jobsearcher.com/jobs/88dc67ac4999996bd7ac9f4e"}}