Lead Software Engineer · Nike

I build thelayer beneaththe launch.

Kalidas Kanniappan architects web platforms, event-driven services, and AI-native engineering systems at Fortune-500 scale—so product teams can move independently without losing coherence.

Years
15+
Companies
9+
Scale
F500
Native
AI
spatial system · live
01Web platform
02AI-native
03API mesh
04Event systems
One platform. Many autonomous teams.
Chapter 01point of view

Complexity should become leverage.

I'm a Lead Software Engineer with 15+ years architecting and shipping cloud-native systems at Fortune-500 scale. At Nike, I drive Microfrontend architecture with Module Federation, build complex React SPA + SSR / Next.js monorepo applications, and power them with Java Spring WebFlux microservices on AWS Lambda, Step Functions, DynamoDB, and S3. I own the Web Experimentation platform built on Adobe Experimentation APIs. I'm an early adopter of AI-driven development — production workflows built around Claude Code, Cursor, MCP servers, custom Skills, RAG-backed memory, and Spec-Driven Development with OpenSpec — using AI to accelerate delivery while raising the bar on code quality, observability, and contract discipline.

Platform ArchitectureModule FederationEvent-Driven SystemsAI-Native EngineeringAPI GovernanceMicrofrontends
01 · Years of Experience
15+
02 · Companies Served
9+
03 · Fortune 500 Giants
2
04 · Anna University, CS
B.E.
Chapter 02selected systems

Platforms with leverage.

Selected architecture work across web platforms, streaming data, API ecosystems, and agentic developer experience. The common outcome: more autonomy with fewer accidental seams.

01
Principal work

Nike Web Platform

Architected Nike's Shell Application — a unified React + Next.js host in a monorepo providing the runtime shell, shared design system, auth, telemetry, and routing for dozens of product surfaces across nike.com. Built Microfrontend platform using Module Federation and the Experimentation runtime integrated with Adobe APIs.

ReactNext.jsTypeScriptModule FederationGraphQLtRPC
Global commerceVisit ↗
02
Principal work

Walmart Data Platform

Built Java backend APIs and React dashboards powering Customer Experience analytics at Walmart's Data Ventures domain. Designed event-driven architectures using Kafka, CQRS, Event Sourcing, and Saga patterns. Built Looker dashboards on curated data marts with LookML models.

JavaKafkaSpring WebFluxReactgRPCGraphQL
Decision systemsVisit ↗
03
Principal work

AI-Native Engineering Platform

Pioneered production-grade AI-native workflows at Nike — building MCP servers exposing internal tooling, authoring reusable Skills encoding engineering standards, and establishing team-wide agentic development practices with Claude Code and Cursor IDE.

Claude CodeMCP ServersCursor IDERAGContextual EngineeringTypeScript
Engineering intelligence
04
Principal work

Microservices & API Platform

Designed and implemented robust API platforms across multiple paradigms: HTTP REST + OpenAPI 3 for external contracts, GraphQL at the edge, tRPC for type-safe internal calls, and gRPC for low-latency service-to-service communication. Established API governance patterns across dozens of consuming squads.

JavaSpring BootNode.jsRESTGraphQLtRPC
Contract architecture
05
Foundation

Module Federation Architecture

Architected and implemented micro-frontend solutions using Module Federation, enabling product teams to run A/B and multivariate experiments as independently-deployable React remotes without coupling to the shell's release cycle.

ReactNext.jsModule FederationTypeScriptMicrofrontendWebpack
Release autonomy
06
Foundation

FIS Multi-Tenant Banking Application

Designed and developed multi-tenant support applications using Java Spring Framework, JPA-Hibernate, and IBMMQ for FIS Global. Worked with System Engineers on requirement reviews, creating sequence and flow diagrams for enterprise banking systems.

JavaSpring FrameworkJPAHibernateIBMMQSQL
Financial systems
Chapter 03capability map

Breadth with a center.

Full-stack range is useful only when it sharpens architecture decisions. The center of gravity is platform engineering: contracts, boundaries, delivery systems, and the teams around them.

Current frontier01 / 06

AI-Native Engineering

Production agentic workflows built around Claude Code, Cursor, MCP servers, and Spec-Driven Development — shipping at enterprise scale with AI as a first-class engineering partner.

Agentic DevelopmentClaude CodeCursor IDEMCP ServersContextual EngineeringSpec-Driven DevelopmentRAG ArchitectureCustom Skills & HooksAI Tool IntegrationPrompt EngineeringOpenSpec / OpenAPIAI Workflow Automation
02

Frontend

React / Next.jsJavaScript / TypeScriptModule FederationMicrofrontend ArchitectureHTML / CSSAngularPerformance OptimizationResponsive Design
03

Backend & APIs

Java / Spring WebFluxREST + OpenAPI 3GraphQLtRPCgRPCNode.js / ExpressJSJPA / HibernateSpring Boot
04

Cloud & Infrastructure

AWS Lambda / Step FunctionsDynamoDB / S3Docker / KubernetesTerraformCI/CD PipelinesGitHub ActionsCloudflareGCP
05

Event-Driven & Data

Kafka StreamsCQRS / Event SourcingSaga OrchestrationLooker / LookMLData PipelinesObservabilityPact CDC TestingIBMMQ
06

Leadership

Architecture ReviewAPI GovernanceMonorepo StrategyEngineering StandardsMentorshipAgile / ScrumCross-functional CollaborationTechnical Strategy
Chapter 04career arc

Built in layers.

Fifteen years of widening scope—from applications and services to the architecture, standards, and AI-enabled workflows behind entire product ecosystems.

Architecting and scaling Nike's Web Platform — driving Microfrontend architecture with Module Federation, building AI-native engineering workflows with Claude Code and MCP, and owning the Experimentation platform that validates product ideas with live traffic across nike.com.

ReactNext.jsTypeScriptModule FederationJavaSpring WebFluxAWS LambdaStep FunctionsDynamoDBGraphQLtRPCgRPCClaude CodeMCP
  • Architected Nike's Shell Application — a unified React + Next.js host in a monorepo providing the runtime shell, shared design system, auth, telemetry, and routing for dozens of product surfaces across nike.com
  • Designed monorepo conventions (workspace boundaries, shared dependency strategy, build caching, type-safe contracts) so independent product teams could ship into the shell without breaking each other
  • Designed and shipped a Microfrontend platform using Module Federation enabling product teams to run A/B and multivariate experiments as independently-deployable React remotes, decoupled from the shell's release cycle
  • Built the Experimentation runtime integrated with Adobe Experimentation APIs, ensuring SSR/CSR consistency, reliable exposure events, and per-member assignment with failure fallbacks
  • Designed APIs across multiple paradigms: HTTP REST + OpenAPI 3 for external contracts, GraphQL at the edge, tRPC for end-to-end type-safe internal calls, and gRPC for low-latency service-to-service communication
  • Established API governance patterns — versioning, deprecation, Pact CDC contract testing, rate-limiting, idempotency, and pagination — scaling cleanly across dozens of consuming squads
Chapter 05connection

Bring me the problem behind the problem.

Platform architecture, AI-native engineering, or a difficult scaling boundary—I’m always interested in a thoughtful technical conversation.

kalidas.k21@gmail.com
Beaverton, OregonResponse channel · email