BOT Development Engineers for Audiocare

**Greetings from BizTech Fusion!** We are seeking for seeking a **BOT Development Engineers for Audiocare,** kindly go through the job description below and let me know your thoughts. **Job Title: BOT Development Engineers for Audiocare** **Location: Remote (United States)** **Duration: 12+ Months Contract** **Note: Clearance: US Citizen, pass background check, drug screening, and Public Trust clearance.** **Job Description** **AWS Platform Expertise** - AWS Solutions Architect–level knowledge (Associate minimum; Professional preferred) - Core compute/storage: EC2, Lambda, S3, ECS/EKS (if containerized workloads are in scope) - Networking: VPC design, Transit Gateway, Direct Connect, Site-to-Site VPN, security groups/NACLs, Route 53 - Streaming/data services: Kinesis Data Streams, Kinesis Firehose (for call/event data pipelines from Genesys) - API Gateway (REST and/or WebSocket APIs), including throttling, usage plans, and request/response transformation - IAM policy design (roles, resource-based policies, cross-account access) directly relevant given the deny-policy issue you hit - Certificate management: ACM (AWS Certificate Manager), mutual TLS (mTLS) configuration for API Gateway and Lambda, private CA if applicable - CloudWatch, CloudTrail, X-Ray for observability/troubleshooting distributed integrations - Infrastructure as Code: CloudFormation or Terraform (Terraform is increasingly the industry default for multi-account AWS environments) **Programming/Development** - Python (strong) — Lambda functions, data transformation, API clients/servers - JavaScript/Node.js — Lambda functions, potentially frontend/widget integrations custom UI components - RESTful API design and consumption (OpenAPI/Swagger spec experience a plus) - SOAP/XML integration experience — WSDL interpretation, XML parsing/transformation - Experience with API authentication patterns: OAuth 2.0, API keys, mTLS client certificates **Integration & Architecture Experience** - Designing and building middleware/integration layers between SaaS platforms and internal enterprise systems - Event-driven architecture patterns, queues, event buses — SQS/SNS/EventBridge experience relevant) - Experience translating between REST and SOAP paradigms - API gateway patterns for legacy system integration - Data transformation/mapping between disparate schemas (contact center data models vs. internal system data models)