Platform Engineer - CI/CD Pipeline
First seen by Alion on Nov 14, 2026.
Profile: Platform Engineer
About SolarSquare:
At SolarSquare we are building the Home-Energy brand of future India. We help homes switch to rooftop solar and move away from traditional coal electricity. We are a full-stack D2C residential solar brand - designing, installing, maintaining (after-sales), and financing solar systems for home-owners across India.
In a few short years we have scaled to become the leading residential solar brand in India. We are obsessed with quality, customer service, and innovating to make it simple for homes to switch to solar. We are looking for leaders to join us in this mission.
What Platform is here to do:
Platform builds the systems every other team depends on and makes them simple to use. In practice that means:
- Designing systems and the contracts between them so teams can work together without knowing each other's internals.
- Hiding complexity behind clean interfaces: one way to authenticate, publish an event, schedule work or call a vendor, instead of five.
- Treating cost as a design requirement. A service should be cheaper to run next quarter than it is today.
- Keeping the architecture small enough for one person to understand and able to scale without a rewrite.
- Defining the guardrails, templates and standards that engineers and coding agents both build within.
What you'll do:
- Write TRDs precise enough for an agent to execute and clear enough for a new engineer to review, then drive them to production, checking and correcting what the agents produce.
- Build and run shared backend services such as authentication, event streaming, scheduling and deep linking, and the integrations that connect them.
- Find the same problem being solved in three places and replace it with one service, library or guardrail.
- Make the infrastructure calls for what you own (data stores, queues, caching, scaling, failure handling) and write down the trade-offs.
- Turn what works into org-wide practice: reusable skills, agent instructions, review checklists and sessions that bring other pods along.
- Question decisions, including leadership's, when the evidence points to a better way.
You'll fit if:
- You have 3 - 6 years building backend systems in production, with strong fundamentals: data structures, concurrency, networking, and how databases and queues behave under load.
- You think in systems and interfaces. You can explain why a boundary sits where it does, and you notice when an abstraction has started costing more than it saves.
- You work hands-on with AI coding agents every day and have opinions, backed by experience, on where they help, where they fail and how to constrain them.
- You write well. Your design docs remove ambiguity instead of moving it somewhere else.
- You can't leave a known problem alone, and you insist on doing things the right way. When you find a better practice, you make sure the rest of the org adopts it, not only your team.
- You move fast because your designs are clear, not because you skip steps. You would rather cut scope than ship something you will need to apologise for.
- You know containers, Kubernetes, CI/CD and cloud infrastructure well enough to deploy and debug your own services without waiting on anyone.
- You judge your work by what it changed for the people using it: cost saved, hours removed, incidents that stopped recurring.
The tech you'll work with :
- AWS, Kubernetes, Terraform, CI/CD pipelines, Kafka, Redis, and Datadog, Prometheus and Grafana for observability, alongside coding agents and internal tooling built on top of them.
Skills
AWS, Kubernetes, Terraform, CI/CD Pipeline, Kafka, Redis, DevOps