Jatin Sharma · Senior Software Design Engineer at Newgen Software

products, tools,
and the layers under them.

Enterprise software by day; by night, aidevkit, a package manager for AI agents, skills and MCP servers, plus SaaS and developer tools. Frontend, backend, infrastructure and AI, with a standing curiosity about the layers below: networks, operating systems and memory.

frontendbackendinfrastructuresystems+ the whole toolbox →
See my work

4 projects · 3 live in production

Resume

PDF · one page

stack --top-to-bottom6 layers
  1. 01
    ApplicationReact, Next.js, MUI, microfrontendsUI architecture, themes, RTL, Webpack and Vite builds
  2. 02
    ServicesNode.js, Spring Boot, RESTAPIs, auth, enterprise integrations
  3. 03
    DataMongoDB, PostgreSQL, Oracle, RedisModelling, caching, query behaviour
  4. 04
    InfrastructureDocker, Caddy, Jenkins, AWSDeployments, reverse proxies, CI/CD
  5. 05
    NetworkHTTP, TLS, TCP/IPWhat actually happens on the wire
  6. 06
    SystemLinux, processes, C++, memoryWhere the abstractions bottom out
full stack, top to bottomstill digging ↓

curious about
what’s underneath.

the path so far

  1. JavaScript
  2. Backend
  3. Databases
  4. Networking
  5. Linux
  6. Docker
  7. C++exploring
  8. Operating systemsexploring
  9. Systems programmingexploring
  10. Distributed systemsexploring
  11. AI infrastructureexploring
one layer down at a time

I started with application development: components, endpoints, forms. It worked, and at some point “it works” stopped being a satisfying answer. Why is this request slow? What does the database do with that query? What actually happens between a browser and a server?

Each question pulled me one layer down: from JavaScript into backend services, into databases, into networking, then Linux and Docker. That curiosity is now pointing at C++, operating systems and distributed systems, and, more recently, at what it takes to run AI systems.

At work that habit shows up as debugging production problems and carrying large migrations through. Outside work it shows up as building the whole thing, then running it.

Jatin

read my resume ↗see my GitHub ↗

things i built,
shipped and run.

Each one started from a specific problem. The pages behind them cover what I built, the decisions that mattered, and the architecture.

Newgen Software Technologies · Senior Software Design Engineer

building NewgenONE.
banks build on it.

Senior SDE.

Building NewgenONE at Newgen Software: one enterprise platform for content, process and customer communication. Promoted from SDE-2 to Senior SDE in July 2026.

NewgenONE is Newgen’s enterprise platform for banks, financial institutions, insurers and governments. It brings content management, business process management and customer communication management together, with business rules, document intelligence and AI agents built on top, and it is used by around 500 enterprises across 79 countries.

I build across its frontend, backend and platform layers: features for major releases, client requirements, production fixes and performance work, while keeping a large product modern as it keeps shipping.

parts of the product i’ve built on

  • NewgenONE Workspace
  • Business Admin
  • Queue and criteria management
  • Advanced search
  • Multilingual and RTL support
  • Themes

across

  • Frontend
  • Backend
  • Platform
  • Microfrontends
  • Enterprise deployments
  • Performance

built for enterprise IT.

Content, process, communication

ECM, BPM and CCM in one low-code platform, with business rules, document intelligence and AI agents on top.

  • ECM
  • BPM
  • CCM
  • Business rules
  • AI agents

Any cloud, or on-premise

The same product ships to public cloud, private data centres and hybrid setups.

  • AWS
  • Azure
  • Google Cloud
  • On-premise
  • Hybrid

Enterprise app servers

Deployed on the Java application servers banks already run.

  • Red Hat JBoss EAP
  • IBM WebSphere

Enterprise databases

Runs on the databases regulated institutions standardise on.

  • Oracle
  • PostgreSQL
  • MySQL
  • Redis cache

Under the hood: Java and Spring Boot services, REST APIs, FreeMarker templates, React and MUI microfrontends, Docker and CI/CD pipelines.

Alongside features: microfrontend compatibility, theme architecture, RTL support, and platform-wide React, MUI and Java upgrades.

things
i’m
exploring.

I learn by building. These are areas I’m working through, not claims of expertise.

C++ and memory.

Pointers, allocation and object lifetimes, to see what a garbage collector or a framework hides.

systems

TCP servers and HTTP internals.

Sockets, framing and parsing, down to what a request is before a framework gets hold of it.

networking

TLS and cryptography.

Handshakes, certificates and why HTTPS works the way it does.

security

Redis and Kafka.

Caching, rate limiting, queues and logs, and how they behave under failure.

data

WebSockets.

Long-lived connections and the state and scaling problems that come with them.

realtime

Operating systems and Linux.

Processes, scheduling and concurrency, from the shell side and the kernel side.

operating systems

Docker and distributed systems.

Networks, volumes, restarts, and the failure modes that appear once there is more than one machine.

infrastructure

AI agents and LLM infrastructure.

Agents, model APIs, AI-assisted engineering, and what running them costs.

AI

what i work with,
grouped by job.

Languages
JavaScriptTypeScriptJavaC++
Frontend
ReactNext.jsViteMUITailwind
Backend
Node.jsNestJSExpressSpring Boot
Data
MongoDBPostgreSQLMySQLOracleRedis
Infrastructure
DockerJenkinsAWSLinuxCaddyNginxJBoss
Systems
TCP/IPHTTPTLSLinuxC++Networking
AI
LLMsAI APIsAI developer toolingAgents

building something
where the details matter?
let’s talk.

Email me

jatinsj710@gmail.com

Resume

PDF · one page