System onlineChennai, India

I turn enterprisecomplexityinto scalable software.

Lead Software Engineer with 12+ years connecting full-stack implementation, architecture, infrastructure, product requirements, and engineering teams.

Explore the system View résumé

12+: Years building
06: Career releases
04: System layers

InterfaceAngular · React

ServicesNode · Spring

PlatformOpenTofu · Cloud

EngineeringARUNSANKAR
SLead / 12+ yrs

ArchitectureStableDeliveryActive

01Capability architecture

One system. Four connected responsibilities.

Strong delivery happens when interfaces, services, platforms, and people are designed as parts of the same system. Select a node to inspect the evidence.

Full-stackDelivery

Node inspected

Build across the stack

Create dependable product experiences from responsive interfaces through secure services and data layers.

Enterprise interfaces with Angular, React, TypeScript, RxJS, and NgRx
REST services and integrations using Node.js, Spring Boot, Java, and PHP
Automated coverage with Playwright, Jest, Jasmine, Karma, and Karate

AngularReactNode.jsSpring BootTypeScript

02Modernization lab

Move the system forward without stopping it.

A conceptual view of how I approach legacy modernization: discover dependencies, define boundaries, automate repetition, and improve operability in deliberate stages.

ModernClear boundaries

LegacyCoupled system

01Discover
02Decouple
03Automate
04Operate

03Release history

Built in layers. Refined through delivery.

Twelve-plus years of increasing scope—from building individual workflows to connecting architecture, infrastructure, teams, and stakeholders.

v6.02023 — Present

Current selection

Lead Software Engineer / Tech Lead

HTC Global Services

Leads full-stack delivery, infrastructure automation, architecture decisions, and engineering growth.

Shapes HLD and LLD while collaborating with client and stakeholder teams
Builds repeatable OpenTofu/Terraform workflows and mentors developers

System designOpenTofuTerraformMentoringAI-assisted engineering

04Selected systems

Decisions, not just deliverables.

Anonymized engineering stories focused on scale, constraints, decisions, and outcomes without exposing client identities or proprietary implementation details.

Context

An anonymized insurance platform processed approximately 10,000 requests per minute while rendering large datasets. Working in a team of three to seven engineers, I helped redesign the experience and migrate workloads from WebSphere to a multi-region Red Hat OpenShift Service on AWS (ROSA) architecture.

Context boundaryClient identity and proprietary implementation details are intentionally omitted.

Engineering decisions

01Optimize high-volume queries and combine Redis caching with deliberate frontend state and LocalStorage use so large datasets remain responsive
02Implement MSAL and Azure AD authentication, bearer-token security, secrets management, database-backed UI RBAC, and PII encryption
03Apply optimistic or pessimistic locking according to the workflow, with synchronized methods where stronger coordination was required
04Design Angular and React interfaces across SSR and CSR use cases without allowing data volume to freeze or break the experience

Outcomes

Reduced application load time from more than five seconds on WebSphere to approximately 0.5 seconds or less in the new architecture
Maintained effectively continuous availability through multi-region AWS deployment and pipeline-managed disaster recovery
Supported approximately 10,000 requests per minute while keeping high-volume data workflows usable

AngularReactSpring BootRedisMSALAzure ADWebSphereROSA

Context

Insurance workloads required Dev, QA, and Prod environments on AWS and ROSA, with instance counts adjusted to expected load. Rebuilding project-specific Terraform or OpenTofu configuration typically required one to three weeks, depending on complexity and engineer experience.

Context boundaryPresented separately from the migration story to show the reusable platform and delivery architecture; company details are omitted.

Engineering decisions

01Create a reusable parent OpenTofu project that applications import through main.tf and customize only through approved variables
02Create a reusable GitLab CI/CD parent pipeline with feature branches mapped to Dev, develop mapped to QA, and main mapped to Prod
03Store secrets in AWS Secrets Manager and CI variables, with branch-specific configuration and Config Server support for production
04Apply no approval to feature branches, two-person review for develop, and four-person approval—including a manager—for main
05Use technical documentation and AI-assisted engineering with GitHub Copilot and OpenAI Codex to support implementation

Outcomes

Replaced repeated one-to-three-week configuration rebuilds with shared parent projects and focused overrides
Made Dev, QA, and Prod provisioning consistent while retaining environment-specific configuration and controls
Supported better infrastructure cost control by scaling application instances according to expected load
Established clear code-review and deployment governance from feature development through production

OpenTofuTerraformGitLab CI/CDAWSROSAAWS Secrets ManagerSpring BootGitHub CopilotOpenAI Codex

Context

An in-house product was initially configured for a dental hospital while retaining the flexibility to support other hospitals through configuration changes. I created the complete desktop interface before the product's production launch.

Context boundaryCompany and product names are omitted. Usage metrics are not claimed because I left before the product went live.

Engineering decisions

01Build the entire desktop UI from scratch with Angular and Electron, organizing modules around reusable, configurable workflows
02Connect the interface to Laravel application services and optimize MySQL access through indexing, query tuning, SOLID design, and clear boundaries
03Provide role-aware administrative impersonation for support workflows while securing personal data through encryption, SSL, and encrypted files
04Support receipt printing and live doctor worklists as soon as a patient is allocated

Outcomes

Delivered a cohesive desktop foundation covering the core operational modules of a hospital
Enabled the same product structure to adapt from dental workflows to broader hospital use through configuration
Integrated secure data handling, printing, and live patient-allocation visibility into the desktop experience

AngularElectronLaravelMySQLHTMLCSSJavaScript

05Leadership operating system

Clarity compounds.

The technical work matters. So does building the context, feedback loops, and shared ownership that allow a team to keep improving it.

EngineeringDelivery

Operating principle

System design

Make constraints, boundaries, and trade-offs visible before they become expensive.

HLD and LLD
Architecture walkthroughs
Pragmatic decision records

Technology matrix

Tools change. Sound boundaries and engineering judgment travel well.

Frontend

AngularReactTypeScriptRxJSNgRxHTMLCSS

Backend

JavaSpring BootNode.jsExpressPHPRESTMicroservices

Platform & data

OpenTofuTerraformDockerMySQLMongoDBIBM DB2

AI & delivery

GitHub CopilotOpenAI CodexClaudePrompt engineeringAI-assisted reviewAI-assisted refactoring

Quality

PlaywrightJestJasmineKarmaKarateESLint

06Full-stack engineering expertise

Lead full-stack engineering for enterprise modernization.

Based in Chennai, India, I lead the architecture and delivery of maintainable enterprise applications across frontend platforms, backend services, data, security, testing, and infrastructure. My work connects hands-on software engineering with the technical direction teams need to deliver safely at scale.

Angular and React frontend architecture

Design scalable TypeScript applications with Angular, React, RxJS, NgRx, reusable UI patterns, automated testing, and accessible responsive interfaces.

Node.js, Java, and Spring Boot services

Build secure REST APIs and microservices using Node.js, Spring Boot, JWT, OAuth2, database integrations, and clear service boundaries.

Legacy application modernization

Plan incremental migrations from tightly coupled MVC and legacy systems to maintainable frontend, API, and infrastructure layers without disrupting ongoing delivery.

Technical leadership and system design

Guide HLD and LLD, architecture decisions, code quality, mentoring, stakeholder communication, and Infrastructure as Code with OpenTofu and Terraform.

Read the full software engineering résumé View professional profiles

Currently leading full-stack engineering delivery

07Professional presence

Good engineering starts with a clear conversation.

I believe the best systems leave both the codebase and the team clearer than they found them.

Start a conversation View résumé