I'm Aman.
Software doesn't start with code.
It starts with understanding.
Every architecture,
every network,
every distributed system
begins with a question.
Selected Work
A multi-service banking backend where independent services communicate asynchronously through Kafka. Designed with fault tolerance and long-term maintainability as the primary constraints — not speed to ship.
View Project → Backend · ArchitectureDeveloped a machine learning application that predicts likely crime patterns using historical crime datasets to support proactive policing and resource planning. Built with a Flask-based ML backend, React frontend, and Random Forest model, the project combined data preprocessing, predictive analytics, and visualization to transform raw crime data into actionable insights.
View Project → Networking · SystemsA collection of experiments and notes on how the infrastructure beneath software actually works — from TCP/IP behaviour under load to the invisible decisions that connect billions of devices every day.
View on GitHub →Background
Working in the Financial Services Business Unit, contributing to enterprise Java backend development and banking domain applications. Designed and implemented secure REST APIs, JWT-based authentication, role-based authorization, and domain-driven backend services while strengthening knowledge of Spring Boot, PostgreSQL, microservices, and clean software architecture through production-style and internal banking projects.
Completed a Software Engineering Internship focused on Java backend development, object-oriented programming, SQL, and enterprise software engineering practices. Worked with REST APIs, database integration, version control, and collaborative development workflows while building a strong foundation in designing maintainable backend applications.
Developed a strong understanding of core computer science concepts including Object-Oriented Programming, Data Structures & Algorithms, Operating Systems, Database Management Systems, Computer Networks, and Software Engineering. These fundamentals continue to shape the design and implementation decisions in my backend projects.
OOP DSA DBMS OS Computer Networks Software EngineeringThe Person
I'm a software engineer driven by curiosity more than code. Before I write a line, I want to understand the system — what it's for, how it fails, who depends on it, and what it will look like three years from now. That instinct shapes everything I build, from small utilities to larger backend services. To me, good software starts with understanding the problem long before thinking about the implementation.
My projects reflect this. From a banking system built around microservices and secure authentication, to explorations of enterprise backend patterns that prioritise clarity over cleverness — I'm drawn to problems where architecture is the work, not a prelude to it. I enjoy breaking large systems into smaller responsibilities and understanding how those pieces communicate, evolve, and remain maintainable over time.
Much of my learning happens outside project requirements. I enjoy studying software design principles, design patterns, Spring internals, distributed systems, and the decisions behind enterprise applications. I'm less interested in simply making features work than in understanding why certain approaches scale better, remain easier to maintain, or become industry standards.
Beyond software, I'm fascinated by networking and system design because they reveal the invisible infrastructure connecting billions of people. Every API request, database query, and distributed service is part of a much larger system, and understanding those interactions is what keeps me motivated. My long-term goal isn't to collect technologies — it's to understand increasingly complex systems and contribute to building software that operates reliably at global scale.
This portfolio reflects the same values I bring to engineering: clarity, structure, restraint, and intentionality. Every element exists for a reason. The focus stays on ideas, thoughtful design, and continuous learning rather than unnecessary complexity. I believe the best software isn't defined by how much code it contains, but by how clearly it solves the problem it was built for.
Languages
Backend & Frameworks
Databases & Infrastructure
Core Computer Science
Focus Areas
Tools
Get In Touch
If you're building something at scale and care about getting the foundations right — I'd like to hear about it.
hello@amanjaiswal.cc