SME - AWS IAC, Terraform,Python

Sapsf; United States; On-site; USD 120,000 - 160,000; Full time

Job summary

Sapsf is seeking a migration-focused engineer to own the plan and technical execution from discovery through decommissioning. The role emphasizes IaC-driven automation, preserving existing function names, and maintaining a rollback path until production is accepted.

You will coordinate with CloudOps/SRE, AWS admins, Slack admins, Jira/GitHub owners, and observability stakeholders to ensure secure, auditable changes and comprehensive documentation across the project lifecycle.

Qualifications

• Experience planning and executing migration from discovery to decommissioning.
• Ability to use IaC or automated processes aligned with standards.
• Maintain existing function names and behavior unless changed and approved.
• Keep a rollback path until production acceptance is reached.
• Protect credentials and avoid exposing secrets in sources or logs.
• Produce implementation notes, test evidence, risk decisions, and changes.
• Coordinate with CloudOps/SRE, AWS admins, Slack admins, Jira/GitHub owners, and observability teams.

Responsibilities

• Own the migration plan and technical execution from discovery through decommissioning.
• Use infrastructure-as-code or repeatable automation where supported by the repository and 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.

Skills

Migration planning

IaC/Automation

Preserve function names

Rollback readiness

Secrets management

Documentation

Cross-team coordination

Tools

AWS

Terraform/CloudFormation

Jira

GitHub

Job description

Requisition ID177755-Posted10/08/2026

Key Responsibilities

• 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.

Skill Requirements

• 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.

Other Requirements

• 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.