Job Description & Details
This is a heavy-hitting backend engineering role focused on building secure, scalable enterprise APIs and cloud-native services using Python and AWS. If you enjoy owning the full API lifecycle from contract design to production observability rather than just writing isolated code snippets, this gig will keep you thoroughly engaged.
What You'll Actually Be Doing
You will spend your days architecting RESTful services, integrating AWS components like API Gateway, Lambda, and ECS, and making sure your systems don't fall over when hit with high traffic. A massive part of this job revolves around test automation and security; you aren't just tossing code over the fence to QA. You are writing robust automated test suites using pytest or Playwright, handling OAuth 2.0/OIDC auth flows, and ensuring your CI/CD pipelines in GitHub Actions are airtight.
The Core Tech Stack
Python is non-negotiable here, specifically paired with modern frameworks like FastAPI or Flask, and you'll need a deep grasp of OpenAPI/Swagger for API-first design. On the infrastructure side, deep hands-on AWS chops are required—think API Gateway, SQS/SNS, Aurora/RDS, and IAM. You also need to know your way around relational databases like PostgreSQL and be comfortable implementing rigorous automated testing and security standards like OWASP.
Interview Expectations
Expect the hiring team to grill you on your approach to API contract design and versioning under high-load distributed environments. They will likely ask you to explain how you handle idempotency, token validation, and secure secrets management using tools like AWS Secrets Manager. The interviewer is trying to sniff out whether you truly own operational readiness or if you just build things until they compile and walk away.
Application Advice
Skip the generic corporate summary on your resume and highlight your direct, hands-on experience scaling Python microservices on AWS. Make sure keywords like FastAPI, OpenAPI, OAuth 2.0, pytest, and specific AWS services are front and center so you easily clear the ATS filters. Prove that you treat testing and observability as first-class citizens in your workflow.