Principal Software Engineer

RX Global; Chennai District; On-site; INR 3,500,000 - 5,500,000; Full time

Job summary

RX Global is seeking a Principal Software Engineer to lead technical direction across bounded domain teams. You will define architecture, govern non‑functional requirements, and drive reliable, secure, and cost‑effective AWS‑based solutions.

You will influence through data‑driven decisions and strong engineering judgment. You will mentor engineers, own technical delivery, and collaborate with product and engineering leadership to roadmap domain strategies while focusing on long‑term

Qualifications

• Proven senior technical leader across multiple teams/services.
• Strong polyglot background (C#/.NET, Java, JavaScript/Node).
• Experience modernising systems; cloud-native patterns on AWS.
• Experience in systems analysis, design and QA/integration methodologies.
• Experience evaluating third‑party services for security, cost, operations.

Responsibilities

• Create an environment where teams can do their best work by removing blockers and raising engineering standards.
• Mentor engineers across teams in architecture, systems thinking, and operations.
• Promote strong technical ownership and post‑incident learning.
• Support scalable knowledge sharing via tech talks, templates, and playbooks.
• Participate in hiring loops and onboard new engineers into domain patterns.
• Hands‑on contributions when needed (prototypes, refactors, high‑risk changes).
• Guide teams in decomposition and sequencing to reduce delivery risk.

Skills

Technical leadership

Polyglot languages

AWS/cloud-native

Architectural leadership

AI governance

Education

Bachelor's/Master's in CS or related

Tools

AWS

Docker

CI/CD

IAM

Job description

About Team:

RX Global aims to create unforgettable experiences for attendees and exhibitors through organizing events. Innovation, creativity, and collaboration drive the company to offer exceptional services to clients.

About the role:

The Principal Software Engineer is the senior-most hands‑on technical leader for a bounded domain (typically spanning 2–4 delivery teams). This role sets the technical direction, defines and governs domain architecture, and acts as a force multiplier—enabling teams to deliver secure, reliable, maintainable, cost‑effective solutions on AWS that meet business outcomes.

The Principal is accountable for the technical health and evolution of the domain: architectural coherence, non‑functional requirements, reliability, security posture, and continuous improvement. This role influences across teams without direct authority, building alignment through strong engineering judgement, data‑driven decisions, and clear communication.

Serves as a senior source of expertise, is expected to be seen as a “go to” person across the department for a set of technologies. Working collaboratively, will think not only about solving business and technical problems but also about the long term maintenance, risk and cost of change of software solutions.

Requirements

• Proven experience as a senior technical leader across multiple teams/services within a bounded domain.
• Strong polyglot background (e.g., C#/.NET, Java, JavaScript/Node) and ability to choose fit-for-purpose technologies.
• Experience modernising systems: migrating from legacy architectures to cloud‑native patterns, reducing technical debt, and decommissioning safely.
• Experience in systems analysis, design and a solid understanding of development, quality assurance and integration methodologies
• Experience developing integrated solutions within a broad technical and business context of significant impact
• Experience evaluating third‑party services and platforms (security, cost, operations, integration complexity).
• Experience leading cross‑team architectural change, platform adoption, or measurable improvements to reliability/cost/performance (with before/after metrics).
• Familiarity with responsible AI usage in engineering workflows (policy/guardrails, data privacy, human‑in‑the‑loop review).
• Bachelor’s/Master’s degree in Computer Science (or related) or equivalent professional experience.

Technical Skills

A person new into role may not have all technical skills but in time is expected to pick up new skills where they exist.

• Expert software design skills: SOLID, DDD, event‑driven architecture patterns, modular design, and maintainable codebases.
• Strong engineering judgement in trade‑offs: simplicity vs extensibility, performance vs cost, consistency vs availability.
• Distributed systems fundamentals: idempotency, retries/backoff, timeouts, circuit breakers, backpressure, eventual consistency, and data partitioning strategies.
• API and event design governance: versioning, schema evolution, backward compatibility, and contract testing.
• Design and delivery of secure, scalable, and resilient AWS‑based solutions, including IAM, networking, integration patterns, reliability, and cost optimisation.
• Infrastructure‑as‑Code and immutable infrastructure concepts; automated environment provisioning.
• Secure architecture patterns & coding practices, threat modelling, and OWASP Top 10 & software supply chain security awareness.
• Strong testing strategy leadership: unit, integration, contract, performance, and security testing.
• TDD/BDD experience where appropriate; ensures testability and measurable coverage of critical paths.
• Observability and SRE principles, including SLIs/SLOs, operational readiness, incident response, and continuous reliability improvement.
• CI/CD pipelines, deployment safety patterns, source control, code review, and automation.

Responsibilities

Engineering Leadership & Culture

• Create an environment where teams can do their best work by removing blockers, improving engineering practices, and contributing to a culture of psychological safety and high standards.
• Mentor and coach engineers across teams—especially senior engineers and emerging tech leads—in architecture, systems thinking, and operational excellence.
• Promote strong technical ownership (“you build it, you run it”), including operational readiness and post‑incident learning.
• Support scalable knowledge‑sharing mechanisms (e.g., tech talks, playbooks, templates, reference implementations).
• Participate in hiring loops and help onboard new engineers into domain patterns and practices.
• Provide hands‑on contributions where needed (prototypes, reference implementations, complex refactors, high‑risk changes).
• Guide teams in decomposition and sequencing to reduce delivery risk; support estimation/sizing and technical discovery.
• Leads through influence; demonstrates integrity, accountability, and constructive challenge.
• Works with Architects and other Principals to drive technical direction while partnering effectively with Engineering Leads and managers; establishes cross‑team mechanisms for collaboration (review forums, design clinics); builds alignment through trust, clarity, and shared goals.

Product & Domain Leadership

• Develop deep understanding of the domain’s business, user journeys, and strategic goals; connect technical choices to measurable customer and business outcomes.
• Co‑own the domain technical roadmap (12–24 months) with Product and Engineering leadership: Align investments to business priorities, platform strategy, security posture, reliability targets, and cost optimisation. Identify and sequence technical risk retirement (e.g., legacy decommissioning, resilience gaps, security debt).
• Provide clear options and recommendations on buy vs build, integration patterns, and platform adoption—framing trade‑offs in cost, risk, time, and maintainability.
• Contribute to vendor assessments and 3rd‑party evaluations (integration, security posture, cost, operational fit).
• Support product delivery teams to simplify complexity, make sound trade‑offs, and deliver scalable solutions while minimising risk

Technical Excellence & Innovation

• Sets and maintains a high technical bar across teams; ensures long‑term viability and sustainability.
• Own the domain reference architecture and integration patterns across services, APIs, data stores, and events.
• Define domain boundaries (bounded contexts), service responsibilities, and integration patterns to reduce coupling and enable team autonomy.
• Work with other Principals to define, evolve, and govern domain technical standards and cross‑functional requirements (security, reliability, observability, performance, compliance).
• Work with Architect and other Principals to establish and maintain lightweight engineering governance: Architecture documentation (e.g., C4‑style diagrams) Architecture Decision Records (ADRs) and reference implementations. Domain design reviews for critical changes and high‑risk systems.
• Create reusable libraries, templates, and frameworks (“golden paths”) that accelerate teams and standardise best practices.
• Ensure solutions are secure by design, fault