Python Architect
AWS Cloud Architecture | Integration Systems | 10+ Years | Multiple Openings
Application Process: Interested Candidates are required to fill the below screening form.
Screening Form: https://forms.gle/8U16bpDTtJk5RwU38
The Work
You will architect a large-scale integration platform for a leading distribution and e-commerce business, connecting customer-facing storefronts with order management, inventory, product catalog, warehouse, and enterprise systems.
You’ll make the key architectural decisions: serverless vs. containers, event-driven vs. synchronous, build vs. buy, and help engineering teams, including our Node.js/TypeScript engineers, implement those decisions properly.
Python is your primary tool, but you should be comfortable using Node.js or other technologies when the problem calls for them.
We currently have two openings: one requires a valid AWS certification as a condition of hire; the other does not. Both require the same depth of hands-on AWS experience. If you’re unsure which opening fits, apply and mention your certification status.
What You’ll Own
- End-to-end architecture for integration between storefronts, warehouse, order management, inventory, product, and enterprise systems.
- Translating business requirements into scalable, production-ready technical designs and making clear trade-offs around cost, performance, reliability, and maintainability.
- Python application and service architecture, including appropriate frameworks, libraries, testing, packaging, and performance considerations.
- AWS architecture across serverless and containerized workloads, including Lambda, API Gateway, S3, SQS, SNS, EventBridge, DynamoDB, RDS, CloudWatch, IAM, and ECS/EKS.
- Architecture and engineering standards, design reviews, and technical direction for critical systems.
- Mentoring engineers and architects, including the Node.js/TypeScript team.
- Partnering with Product, Business, and Engineering leadership on technology strategy and roadmap decisions.
Must-Have
Python & Systems
- 10+ years of professional software engineering experience, with substantial hands-on Python development in production.
- Strong understanding of Python concurrency, performance, testing, packaging, and maintainability.
- Proven ownership of architecture decisions for distributed, production-grade systems.
- Strong knowledge of API design, event-driven and asynchronous systems, databases, messaging, caching, security, and observability.
AWS
- Deep, hands-on production experience with AWS Lambda and serverless architecture.
- Working fluency across core AWS services including API Gateway, S3, SQS, SNS, EventBridge, DynamoDB, RDS, CloudWatch, IAM, and ECS/EKS.
- Ability to design and operate AWS systems at scale—not simply work through PaaS or managed abstractions.
- AWS certification is mandatory for one of the two openings (Solutions Architect Associate/Professional, Developer Associate, DevOps Engineer Professional, or equivalent).
Breadth & Leadership
- Professional experience with Node.js, strong enough to design and build production systems.
- Ability to evaluate and adopt technologies based on the problem rather than personal stack preference.
- Experience leading engineering teams, mentoring engineers, or driving significant technical initiatives.
- Ability to communicate architectural decisions and trade-offs to both technical and non-technical stakeholders.
Good to Have
- Additional AWS certifications
- Terraform or AWS CDK
- Docker and Kubernetes
- CI/CD and modern DevOps practices
- Microservices and event-driven architecture at scale
- Product engineering or fast-paced technology experience
- AI-assisted or agentic software engineering workflows
What Strong Looks Like Here
- You turn business requirements into system designs and can clearly explain the trade-offs.
- You can justify Lambda vs. containers based on cost, performance, reliability, and operational complexity—not preference.
- You’ve operated systems in production, learned from failures, and changed how you design as a result.
- You can explain architectural decisions clearly enough to guide junior engineers and the teams building against your systems.
- You choose Python, Node.js, or another technology based on the problem—not loyalty to a particular stack.
Who This Is Not For
- Candidates whose AWS experience is primarily through PaaS/managed abstractions rather than direct use of AWS services.
- Candidates who have only built serverless side projects and never operated production workloads.
- Candidates looking for a purely individual-contributor role with no mentoring or cross-team responsibility.
- Candidates whose 10+ years are primarily maintenance work without meaningful architecture ownership.
- Architects who design isolated systems without considering the engineers and teams who have to build, integrate, and operate them.
Application Question(s):
- Have you filled the screening form mentioned in the job description?
Work Location: Remote
