Skip to content
View jeshwinwilliam's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report jeshwinwilliam

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
jeshwinwilliam/README.md


πŸ’« About Me

Software Engineer with 4+ years of experience across distributed systems, AI-enabled platforms, backend services, and cloud infrastructure, working primarily with Java, Python, Kafka, and AWS.

  • 🧠 Building backend platforms where AI-assisted tooling meets production-grade reliability β€” not just prompt wrappers, but event-driven services with retries, observability, and failure recovery
  • πŸ—οΈ Deep focus on Kafka-based orchestration, idempotent processing, sagas, and dead-letter isolation at scale
  • πŸ“„ Peer-reviewed Springer publication (ICSADL 2022) on mobile payment security
  • ☁️ AWS Certified Solutions Architect – Associate
  • πŸ’¬ Ask me about event-driven architecture, AI-assisted review pipelines, or reconciliation systems at scale

⚑ Core Skills

Backend Engineering β€” Java Β· Spring Boot Β· REST APIs Β· gRPC Β· Spring Security Β· Hibernate Β· JPA Β· service design

Distributed Systems β€” Kafka Β· JMS Β· asynchronous workflows Β· retry strategies Β· dead-letter queues Β· resiliency patterns

AI Platforms β€” Python Β· workflow orchestration Β· AI-assisted review systems Β· platform integration Β· evaluation-minded tooling

Cloud, Data & Operations β€” AWS Β· GCP Β· Docker Β· Kubernetes Β· PostgreSQL Β· Oracle Β· Redis Β· Prometheus Β· Grafana Β· ELK Β· CI/CD


πŸ— System Architecture β€” Distributed Event Processing Platform

A deeper reference architecture reflecting the backend platforms I build day-to-day: request path, async event backbone, storage-per-service, and full observability.

flowchart TB
    Client[Client Applications]

    subgraph Edge["Edge Layer"]
        LB[Load Balancer]
        APIGW[API Gateway<br/>Rate Limiting Β· AuthN]
    end

    subgraph Services["Service Layer"]
        Auth[Auth Service]
        Order[Order Service]
        Payment[Payment Service]
        Inventory[Inventory Service]
        Notification[Notification Service]
    end

    subgraph Messaging["Event Backbone"]
        Kafka[(Apache Kafka<br/>Partitioned Topics)]
        DLQ[(Dead Letter Queue)]
    end

    subgraph Data["Storage β€” Database per Service"]
        PG[(PostgreSQL<br/>Orders / Payments)]
        Redis[(Redis<br/>Session & Cache)]
        Cassandra[(Cassandra<br/>Inventory β€” high write)]
    end

    subgraph Observability["Observability Stack"]
        Prometheus[Prometheus]
        Grafana[Grafana]
        ELK[ELK Stack]
        Tracing[Distributed Tracing<br/>OpenTelemetry]
    end

    Client --> LB --> APIGW

    APIGW --> Auth
    APIGW --> Order
    APIGW --> Payment
    APIGW --> Inventory

    Order -- OrderCreated --> Kafka
    Payment -- PaymentProcessed --> Kafka
    Inventory -- StockReserved --> Kafka
    Kafka -- consume --> Notification
    Kafka -- consume --> Inventory
    Kafka -- consume --> Payment
    Kafka -. failed events .-> DLQ

    Auth --> Redis
    Order --> PG
    Payment --> PG
    Inventory --> Cassandra

    Auth & Order & Payment & Inventory --> Prometheus
    Auth & Order & Payment & Inventory --> ELK
    Auth & Order & Payment & Inventory --> Tracing
    Prometheus --> Grafana
Loading

Design decisions worth calling out:

Concern Approach Why
Service coupling Kafka as async backbone instead of sync REST chains Decouples producers/consumers, absorbs traffic spikes, enables replay
Data ownership Database-per-service (PostgreSQL, Cassandra, Redis) Avoids shared-schema coupling; each store matches its access pattern
Failure handling Dead-letter queues + retry topics Poison messages don't block partition consumers
Consistency Eventual consistency via event choreography, sagas for multi-step transactions Avoids distributed locks; each service stays autonomous
Observability Metrics (Prometheus), logs (ELK), traces (OTel) per service Root-causing latency across service boundaries

πŸ’Ό Experience

Software Engineer β€” State Street (Jan 2026 – Present) Built low-latency fund transaction and reconciliation services using Java, Spring Boot, Kafka, JMS, Oracle, PostgreSQL, Docker, Kubernetes, Jenkins, and AWS.

  • Improved platform throughput by 40% through event-driven transaction pipelines
  • Reduced database query latency from 3.2s to under 1.1s in production
  • Enabled operations teams to resolve breaks 35% faster with workflow dashboards

Software Engineer β€” Accenture (Client: Flipkart, Feb 2022 – Dec 2024) Delivered backend systems for large-scale checkout and payment flows using Java, Spring Boot, Kafka, Cassandra, MySQL, Redis, Elasticsearch, Docker, Kubernetes, Jenkins, and GCP.

  • Improved payment success rate by 12% with smart-retry payment orchestration
  • Reduced end-to-end API latency by 35% through performance tuning
  • Cut infrastructure overhead by 22% via scaling and cloud optimization

πŸš€ Featured Builds

AI-assisted pull request analysis platform with event-driven review orchestration, persistent review history, and observability-first service design. Spring Boot Kafka AI-assisted review Docker πŸ“ System design write-up

Order, payment, inventory, and logistics workflow architecture with Kafka-driven orchestration, idempotent processing, and resilient failure recovery across service boundaries. Java Spring Boot Kafka PostgreSQL Saga pattern πŸ“ System design write-up

IMEI-driven device verification system for mobile payment authentication and fraud-aware decision flows β€” connected to a peer-reviewed publication. Java Spring Boot REST APIs Security πŸ“ System design write-up

Real-Time Transaction Reconciliation System

Trade ingestion, validation, ledger updates, duplicate detection, and reconciliation workflows for high-integrity financial operations. Kafka Partitioned processing Auditability πŸ“ System design write-up (case study generalized from production work)


πŸ“„ Publication

"Improved Security on Mobile Payments Using IMEI Verification" Peer-reviewed conference paper, ICSADL 2022 β€” published in Springer's Advances in Intelligent Systems and Computing (Sentiment Analysis and Deep Learning, 2023, pp. 183–193). View on Springer Β· DOI Β· 1120 accesses Β· 1 citation


πŸ“Š GitHub Stats

πŸ“ˆ Activity Graph

🐍 Contribution Snake

snake animation


πŸŽ“ Education & Credentials

MS in Computer Science β€” Oklahoma City University (2026) B.Tech in Computer Science and Engineering β€” Hindustan University (2022) AWS Certified Solutions Architect – Associate β€” issued March 2026


πŸ“« Contact

Open to software engineering roles across backend, distributed systems, and AI platforms β€” especially event-driven architecture, cloud infrastructure, and developer-facing systems where reliability, scale, and product thinking matter.

⚑ Systems, scale, signal β€” building AI-enabled platforms and resilient backend infrastructure for production environments.

Pinned Loading

  1. pr-intelligence-platform-jeshwin pr-intelligence-platform-jeshwin Public

    Java 1

  2. distributed-event-processing-system distributed-event-processing-system Public

    Java 1

  3. vaultmesh-banking-platform vaultmesh-banking-platform Public

    Java

  4. mobile-payment-security-system mobile-payment-security-system Public

    Java 1

  5. distributed-order-processing-platform distributed-order-processing-platform Public

    Java 1

  6. jesh-chatbox-python jesh-chatbox-python Public

    Python