Senior Backend Engineer - Platform engineering

< p> Job_Description":"< span> < p> < b> < b> < span> < span> About the role < br> < p> < span> Phoenix is the platform engineering squad - the team responsible for the shared backend infrastructure that all squads build on. API gateway, service mesh, shared platform services, the AI SDK integration layer, and the IAM/RBAC SDK are all Phoenix territory. < br> < p> < span> Senior Backend Engineers on Phoenix are building the surfaces other engineers use. Your customer is not the end borrower - it is the 12 squads that depend on Phoenixs APIs, SDKs, and shared services to build their features. Platform engineering is a product discipline, and the quality of what you build determines the velocity of the entire engineering organisation. < br> < p> < b> < b> < span> Key Responsibilities < br> < p> < b> < span> Platform Service Development < br> < p> < span> < span> - < span> < span> Build and maintain the shared backend platform services - the IAM/RBAC SDK, the AI SDK wrapper, the notification service, the event bus, and the feature flag system that every squad consumes < br> < p> < span> < span> - < span> < span> Own the IAM/RBAC SDK implementation - translating the Cloud-Native Platform Architects design into a production-ready SDK that twelve squads can integrate with confidence < br> < p> < span> < span> - < span> < span> Build the AI SDK integration layer - the secure, consistent interface for squads to call LLM APIs with rate limiting, cost tracking, PII redaction, and fallback handling built in < br> < p> < span> < span> - < span> < span> Design and implement the shared event bus patterns - how domain events are published, subscribed to, and replayed across services using SQS or Kafka < br> < p> < span> < span> - Write the platform SDK documentation and integration guides that product squad engineers use to onboard themselves without requiring Phoenix involvement < br> < p> < b> < span> API Gateway & Service Mesh < br> < p> < span> < span> - < span> < span> Own the API gateway implementation - routing configuration, authentication enforcement, rate limiting rules, and the observability instrumentation that feeds into the platform monitoring stack < br> < p> < span> < span> - < span> < span> Implement service mesh configuration for inter-service communication - mTLS, circuit breakers, retry policies, and traffic management for the twelve-service landscape < br> < p> < span> < span> - < span> < span> Define and enforce API standards in collaboration with the Cloud-Native Platform Architect - contract-first development, OpenAPI spec, versioning, and backward compatibility discipline < br> < p> < span> < span> - Build the API testing infrastructure - consumer-driven contract tests that catch breaking changes before deployment and give squads confidence in the API gateway configuration < br> < p> < b> < span> AI-Native Platform Engineering < br> < p> < span> < span> - < span> < span> Use Cursor and Claude as primary development tools - the Phoenix engineering standard is AI-augmented development; all code, tests, and documentation are AI-assisted < br> < p> < span> < span> - < span> < span> Build the n8n and AppSmith integration hooks - the platform-level API endpoints and webhooks that allow Rangers automations to interact safely with platform services < br> < p> < span> < span> - Implement observability instrumentation across platform services - distributed tracing (OpenTelemetry), structured logging, and metrics that give the organisation visibility into platform health < br> < p> < b> < span> Quality, Reliability & Mentoring < br> < p> < span> < span> - < span> < span> Set and maintain code quality standards within Phoenix - code review, refactoring discipline, test coverage, and the mentoring of Intermediate and Associate engineers < br> < p> < span> < span> - < span> < span> Own platform service reliability - SLO monitoring, incident response, and the postmortem process when platform services affect product squad delivery < br> < p> < span> < span> - Contribute to the Platform Guild - share platform engineering knowledge, present implementation decisions, and participate in cross-squad technical discussions < br> < br> < span> Requirements < p> < b> < b> < span> Professional Experience < br> < p> < span> < span> - 6 to 8 years in backend engineering with experience building shared services or platform components consumed by other teams - understanding that your customer is internal engineering is essential < br> < p> < span> < span> - Has designed and maintained SDKs or shared libraries in production - knows what SDK stability means and has experienced the pain of breaking changes < br> < p> < span> < span> - Experience with API gateway configuration and service mesh management in a microservices environment < br> < p> < span> < span> - Active AI tool user - uses Cursor and Claude for development today; AI-assisted engineering is standard practice < br> < div> < b> < b> < span> Mindset & Soft Skills < br> < p> < span> < span> - Platform identity: Platform identity: my customer is other engineers - takes pride in developer experience, documentation quality, and SDK ergonomics < br> < p> < span> < span> - Reliability: Reliability obsession: platform services fail twelve squads simultaneously when they go down - takes on-call, postmortems, and SLO management seriously < br> < p> < span> < span> - AI-native: AI-native developer: Cursor and Claude open all day - models the AI-augmented engineering practice Phoenix is responsible for demonstrating < br> < p> < span> < span> - Documentation: Documentation culture: platform code without great docs is unusable - writes runbooks, SDK guides, and ADRs as part of the definition of done < br> < div> < b> < b> < span> Technical Skills < br> < div> < b> < span> Backend Engineering - Core < br> < div> < span> Java / Spring Boot & Microservices / platform service design < br> < div> < span> REST API design (OpenAPI) & Event-driven architecture (SQS / Kafka) < br> < div> < span> SDK design and development & Distributed systems patterns < br> < div> < br> < div> < b> < span> Platform Engineering - Core < br> < div> < span> API gateway implementation & Service mesh (Istio / Linkerd) < br> < div> < span> IAM / OAuth2 / RBAC implementation & Feature flag systems < br> < div> < span> OpenTelemetry / distributed tracing & Contract testing (Pact) < br> < div> < br> < div> < b> < span> AI Native - Core Expectation < br> < div> < span> Cursor for daily development & Claude for coding and documentation < br> < p> < span> AI SDK integration design & LLM API patterns (rate limiting / fallback) < br> < div> < b> < span> Added advantage < br> < div> < span> Kotlin & AWS (API GW / SQS / Lambda < br> < div> < span> Kong / Envoy & Kafka < br> < p> < span> Domain-driven design < br> < br> < span> Benefits < div> < span> < span> < span> < span> SarvaGram is on a mission to revolutionize financial services for millions in rural India. Were building the nations first data-driven platform that combines cutting-edge technology with a human touch to unlock financial possibilities for underserved households. < span> < span> < br> < div> < span> < span> < span> < span> This is your chance to be at the forefront of innovation. Join us and: < span> < span> < br> < div> < span> < span> < span> < span> - Shape the future of FinTech: Were not just building a product, were creating a new category. Be a part of defining the future of financial inclusion for rural India. < span> < span> < br> < div> < span> < span> < span> < span> - Embrace a high-growth, high-impact environment: This is a non-linear growth opportunity. Build a platform used by millions and witness the network effect drive massive scale. < span> < span> < br> < div> < span> < span> < span> < span> - Tackle real-world challenges: Apply your skills to solve critical problems and directly empower rural communities. < span> < span> < br> < div> < span> < span> < span> < span> - Craft solutions that touch lives: Develop innovative products used by diverse household members, each with unique needs < br> < br> ","< /span> < /span> < /span> < /span> < /div> < /span> < /span> < /span> < /span> < /span> < /span> < /div> < /span> < /span> < /span> < /span> < /span> < /span> < /div> < /span> < /span> < /span> < /span> < /span> < /span> < /div> < /span> < /span> < /span> < /span> < /span> < /span> < /div> < /span> < /span> < /span> < /span> < /span> < /span> < /div> < /span> < /span> < /p> < /span> < /div> < /span> < /div> < /span> < /b> < /div> < /span> < /p> < /span> < /div> < /span> < /b> < /div> < /div> < /span> < /div> < /span> < /div> < /span> < /div> < /span> < /b> < /div> < /div> < /span> < /div> < /span> < /div> < /span> < /div> < /span> < /b> < /div> < /span> < /b> < /b> < /div> < /span> < /span> < /p> < /span> < /span> < /p> < /span> < /span> < /p> < /span> < /span> < /p> < /span> < /b> < /b> < /div> < /span> < /span> < /p> < /span> < /span> < /p> < /span> < /span> < /p> < /span> < /span> < /p> < /span> < /b> < /b> < /p> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /b> < /p> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /b> < /p> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /b> < /p> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /span> < /span> < /span> < /p> < /span> < /b> < /p> < /span> < /b> < /b> < /p> < /span> < /p> < /span> < /p> < /span> < /span> < /b> < /b> < /p> < /span> < /p> Disclaimer : This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.