> Markdown version of [/jobs/ext/3797039-technical-specialist](https://www.wearedevelopers.com/jobs/ext/3797039-technical-specialist). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Technical Specialist - **Company:** HCL America, Inc. - **Location:** United States - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Amazon Web Services, Application Integration Architecture, Continuous Integration, Github, Load Testing, Systems Integration, Delivery Pipeline, Cloudformation, Api Gateway, Web Api - **Published:** October 17, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=e8ef963c20e3fedf ## About the Role AWS Cloud Engineering CI/CD & GitHub Actions API & Application Integrations Must Have Skill API Gateway,Application Integration Architecture (AIA),AWS CloudFormation,GitHub Actions,CI/CD, * Build the AWS production infrastructure required to support ReleaseBot. * Migrate production and test ReleaseBot functions, API endpoints, deployment workflows, configuration, and integrations. * Validate deployment and application behavior through smoke, integration, and endto-end release testing. * Cut over ReleaseBot to the production account and decommission the legacy AWS development resources. ## Description * Own the migration plan and technical execution from discovery through decommissioning. * Use infrastructure-as-code or repeatable automation where supported by the existing repository and account standards. * Preserve existing function names and application behavior unless a change is required and approved. * Maintain a rollback path until production acceptance is complete. * Protect credentials and tokens; do not expose secret values in source, logs, tickets, or documentation. * Produce implementation notes, test evidence, risk decisions, change records, and support documentation. * Coordinate with CloudOps/SRE, application owners, AWS account administrators, Slack administrators, Jira/GitHub owners, and observability stakeholders.