Job Description & Details
This is a heavy-hitting remote contract role focused on building out serverless Python workloads and modernizing deployment pipelines. If you enjoy jumping across the entire stack from databases to AWS cloud services without needing hand-holding, this 12-month gig will keep you thoroughly engaged.
What You'll Actually Be Doing
You'll be embedded in an Agile setup working on everything from API design to debugging distributed systems. A major chunk of your time will go into architecting serverless AWS solutions, building local build and deployment pipelines, and troubleshooting complex issues that span across frontend, backend, and cloud infrastructure. You are expected to operate autonomously in straightforward domains while figuring out tricky integration points with minimal oversight.
The Core Tech Stack
Python is your primary weapon here, paired heavily with robust API design, SQL, Spark, and workflow orchestrators like AWS Step Functions or Airflow. Because the infrastructure relies on AWS Serverless and various container technologies, you need a strong grasp of cloud-native patterns. Knowing how to handle relational and NoSQL databases alongside these tools is non-negotiable since you'll be fixing data issues and optimizing backend performance.
Interview Expectations
Expect the hiring team to test your deep understanding of asynchronous Python and serverless architectural anti-patterns, likely asking you to design a distributed event-driven system using AWS Step Functions and Lambda. They want to see if you can articulate failure modes in cloud architectures and explain how you handle idempotent retries. Another common trap is troubleshooting a broken CI/CD pipeline under pressure, so brush up on container build optimizations and local deployment strategies.
Application Advice
Make sure your resume doesn't just list Python and AWS as buzzwords, but explicitly highlights complex serverless deployments and orchestration tools like Airflow or Step Functions that you've managed in past roles. Lean into your CI/CD and troubleshooting experience to show you can fix broken pipelines independently. Inject terms like 'API design', 'distributed systems', and 'root cause analysis' directly into your work history to easily clear the ATS filters.