The Work

You will architect a large-scale integration platform for a leading player in the distribution and e-commerce industry, connecting customer-facing storefronts with warehouse and enterprise systems: order management, inventory synchronization, product catalogs, and system interoperability across a multi-layered architecture. You will decide what runs on Lambda versus a container, what needs to be event-driven versus synchronous, and what gets built in-house versus bought, then help the team, including our Node.js/TypeScript engineers, build it properly. Python is your primary tool, but you will be expected to reach for Node.js or whatever else the problem needs without complaint.

Cidroy is a small, founder-led team building scalable enterprise software across industries, including defence-adjacent and high-security deployments. You get direct access to the people making company decisions, a real Engineering Ladder, and systems that carry live order and inventory data for a real business, so a bad design decision shows up quick. Relocation support is available for the right candidate.

Note: We currently have two openings for this role. One requires a valid AWS certification as a condition of hire; the other does not. Both openings require the same depth of real, hands-on AWS experience described below. If you are unsure which opening fits you, apply anyway and mention your certification status.

What You Will Own

- Architecture for the integration platform end to end: how storefronts, warehouse systems, and enterprise systems stay in sync without falling over
- Translating business and product requirements into technical designs that hold up under real order volume
- Python-based application development, including framework and library choices made for the problem at hand, not out of habit
- AWS infrastructure design across serverless and containerized workloads: Lambda, API Gateway, S3, SQS, SNS, EventBridge, DynamoDB, RDS, CloudWatch, IAM, and ECS/EKS where relevant
- Engineering and architectural standards across the platform, including design reviews for critical systems like order management and inventory sync




- Technical mentorship for engineers and architects working under you, including the Node.js/TypeScript team building the storefront-facing layer
- Trade-off calls between serverless, containerized, and traditional deployment models, made on cost, performance, and maintainability grounds
- A direct line to Product and Business leadership on technology strategy and roadmap decisions

Must-Have

Python Engineering

- Demonstrated production experience designing and building Python applications and services, not just scripting or maintenance work
- Working understanding of Python internals: concurrency, performance characteristics, testing, packaging, and long-term maintainability

Architecture and Systems

- A track record of owning architecture decisions for distributed, production-grade systems, with the scars to show for it
- Solid grounding in API design, event-driven architecture, asynchronous processing, databases, messaging, caching, security, and observability

AWS

- Real, hands-on experience with AWS Lambda and serverless architecture in production, not lab exercises
- Working fluency across core AWS services (API Gateway, S3, SQS, SNS, EventBridge, DynamoDB, RDS, CloudWatch, IAM, ECS/EKS) and how they combine into a coherent architecture
- For one of our two open positions, a current AWS certification (Solutions Architect Associate or Professional, Developer Associate, DevOps Engineer Professional, or equivalent) is mandatory. For the other, certification is not required, but the depth of AWS experience must be equivalent either way.

Breadth

- Working professional experience with Node.js, strong enough to design and build with it, not just read it




- Comfort picking up an unfamiliar technology when the problem calls for it, rather than defaulting to what you already know

Leadership

- Experience guiding engineering teams or technical initiatives, and communicating architectural reasoning to both technical and non-technical stakeholders

Good to Have

- AWS certifications beyond whichever one applies to your opening
- Hands-on Terraform or AWS CDK experience
- Docker and Kubernetes experience
- CI/CD and modern DevOps practice
- Microservices and event-driven architecture at scale
- Experience in product engineering or fast-paced technology environments
- Familiarity with AI-assisted or agentic software engineering tools and workflows

What Strong Looks Like Here

- You read a business requirement and come back with a system design and its trade-offs, not a list of clarifying questions
- When you propose Lambda over a container (or the reverse), you can explain the cost and operational reasoning, not just a preference
- You have shipped something that failed in production, know exactly why, and changed how you design because of it
- You can walk a junior engineer through why an architecture decision was made, not just what it is
- You choose Node.js, Python, or something else entirely based on the problem, and can articulate why without defending a stack for its own sake

Who This Is Not For

- Candidates who have only worked with AWS through managed platforms or PaaS abstractions, without touching the underlying services directly
- Candidates who have configured serverless functions for a side project but never operated one under real production load
- Candidates looking for a pure IC role with no mentorship or cross-team responsibility
- Candidates whose "10+ years" is mostly maintenance work on someone else's architecture, without ever having owned a design decision themselves
- Architects who think in isolated services and have no interest in how their design decisions land on the teams building against them, including the frontend and full-stack engineers integrating with what you design .

📌 Python Architect (India)
🏢 Cidroy Infotech
📍 India