{"schemaVersion":"jobsearcher.job.v1","id":"2e3bd5fa32f5a37de4196910","url":"https://jobsearcher.com/jobs/2e3bd5fa32f5a37de4196910","canonicalUrl":"https://jobsearcher.com/jobs/2e3bd5fa32f5a37de4196910","title":"AWS Agentcore Platform Engineer","description":"Role: AWS Agentcore Platform EngineerLocation: Reading, PA (Hybrid 2-3 days a week from office) Contract- We are looking for a highly technical Lead Platform Engineer to architect the observability, cost governance, and security framework for our enterprise AI agent ecosystem. You will be responsible for ensuring our agentic workflows—built on AWS Bedrock, AgentCore, and MCP servers—are scalable, observable, and cost-efficient.The ideal candidate bridges the gap between traditional DevOps and the emerging world of LLMOps, with a deep focus on distributed tracing for non-deterministic AI workloads.RequirementsExperience: 8+ years in Platform Engineering, DevOps, or Site Reliability Engineering (SRE).Cloud Expertise: Deep proficiency in AWS (IAM, CloudWatch, Bedrock, Lambda).Observability Tools: Proven experience with Dynatrace, Jaeger, or Honeycomb, and distributed tracing standards.AI/LLM Interest: Familiarity with the LLM lifecycle, including prompt execution, token usage, and frameworks like LangChain or AgentCore.Automation: Advanced experience with Terraform and CI/CD pipeline design.Collaboration: Experience working in an Agile environment with integrated tools like Microsoft Teams and Confluence.Job ResponsibilitiesObservabilityAssess 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 modulesRegardsRaahul Bansiwallinkedin.com/in/rahul-b-14b5a4168(2014792186) | Office: (201) 479 2186 EXT: 444rahulb@net2source.comwww.net2source.com270 Davidson Ave, Suite 704, Somerset, NJ 08873, USAKnowledge is Power.","company":"Net2Source","rawCompany":"net2source n2s","city":"Reading","state":"PA","isRemote":false,"isActive":false,"createdAt":"2026-07-03T10:34:05.150Z","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":"Role: AWS Agentcore Platform EngineerLocation: Reading, PA (Hybrid 2-3 days a week from office) Contract- We are looking for a highly technical Lead Platform Engineer to architect the observability, cost governance, and security framework for our enterprise AI agent ecosystem. You will be responsible for ensuring our agentic workflows—built on AWS Bedrock, AgentCore, and MCP servers—are scalable, observable, and cost-efficient.The ideal candidate bridges the gap between traditional DevOps and the emerging world of LLMOps, with a deep focus on distributed tracing for non-deterministic AI workloads.RequirementsExperience: 8+ years in Platform Engineering, DevOps, or Site Reliability Engineering (SRE).Cloud Expertise: Deep proficiency in AWS (IAM, CloudWatch, Bedrock, Lambda).Observability Tools: Proven experience with Dynatrace, Jaeger, or Honeycomb, and distributed tracing standards.AI/LLM Interest: Familiarity with the LLM lifecycle, including prompt execution, token usage, and frameworks like LangChain or AgentCore.Automation: Advanced experience with Terraform and CI/CD pipeline design.Collaboration: Experience working in an Agile environment with integrated tools like Microsoft Teams and Confluence.Job ResponsibilitiesObservabilityAssess 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 modulesRegardsRaahul Bansiwallinkedin.com/in/rahul-b-14b5a4168(2014792186) | Office: (201) 479 2186 EXT: 444rahulb@net2source.comwww.net2source.com270 Davidson Ave, Suite 704, Somerset, NJ 08873, USAKnowledge is Power.","datePosted":"2026-07-03T10:34:05.150Z","dateModified":"2026-07-03T10:34:05.150Z","hiringOrganization":{"@type":"Organization","name":"Net2Source","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Reading","addressRegion":"PA","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"2e3bd5fa32f5a37de4196910"},"url":"https://jobsearcher.com/jobs/2e3bd5fa32f5a37de4196910"}}