Danish
Javed.
Five years building FinTech systems
used in real payment workflows.
I build software for high-trust environments where reliability matters. Backend-first, full-stack in practice: Java, Spring Boot, Kafka, Node.js, React, Angular, Oracle, Docker. Currently expanding into applied AI and intelligent product workflows.
I write about what I build — because engineers who can explain things are rare.
I build systems
that need to stay reliable.
Working in FinTech raises the standard for quality and attention to detail. The platform I have spent three years building processes over a billion dollars annually. That scale changes how you approach pull requests, schema migrations, and configuration changes.
My core strength is backend engineering, with hands-on experience in Kafka consumer groups, Oracle query plans, and Spring Security filter chains. I also contribute comfortably across the frontend when needed, which gives me practical full-stack range.
What I care about: shipping features that work, finding bugs before they cost money, and leaving codebases in better shape than I found them. I was recognized for Best Collaborator at an AI Hackathon in 2025 — which is more accurate than any "team player" line on a resume.
I Finish Things
Features don't count until they're in production and working. I track the full journey — design to deployment to monitoring. 143 PRs is what finishing things looks like over time.
I Ask Why First
Before writing a line, I want to understand what we're solving and whether we're solving the right thing. That instinct has saved more time than any framework.
In a room full of people building fast, the recognition went to how I work with others, not just what I built. That's the part I'm most proud of.
Five Years. Consistent Standards.
I work on systems where reliability, security, and maintainability are expected. That standard shapes how I build.
Promoted into this role based on sustained delivery and impact. I contribute across full-stack development within a team of 8–10 engineers building financial applications processing real payment workflows. My role is to keep quality high, unblock delivery, and help production stay stable while shipping.
Core engineering work on a FinTech platform that processes over $1B annually. I owned features end-to-end — design through deployment. The same focus on quality throughout that journey.
- Identified a query taking 50 seconds per run, optimized it to 9ms, and delivered the improvement to production.
- Led a security remediation initiative — identified and resolved cross-codebase vulnerabilities before anything reached customers.
- 143 pull requests over the full tenure: features, hardening, refactors, production fixes. The number reflects consistency.
- Worked daily in Oracle, Kafka, Docker — not as bullet points but as the actual tools production ran on.
Full-stack delivery across client engagements — Java backend, Angular frontend, Node.js services. Structured remote cycles, multiple simultaneous projects. Where I learned to deliver without being in the same room.
First real engineering role post-internship. Java, Angular, iterative delivery. The year I learned that debugging someone else's code is the fastest way to understand a codebase.
Six months at a global technology consultancy. Java, Maven, professional engineering practices. The start.
Built to Understand.
Each project is built to deepen my understanding of a real technical problem, then document the learning publicly.
Ask a question in plain English, get a chart and an answer. No SQL required. Built a full abstraction layer — LLM provider strategy, modular router, ChromaDB for semantic lookup — so the AI backend can be swapped without touching the rest.
Built to understand Spring Cloud patterns through hands-on implementation and practical tradeoffs. Independent deployable services, Eureka discovery, centralised gateway, Zipkin tracing. The kind of architecture I work adjacent to at Paxcom.
GraphQL for a payment backend — wallet, transactions, real-time subscriptions over WebSocket. Built alongside the GraphQL article series. Writing the article first, then the code, then revising both, is how I actually learn something.
Mutual TLS is widely discussed but less often implemented end-to-end in practice. Built a full local setup — CA, certificates, Nginx reverse proxy, Dockerised — then wrote the article series to make sure I understood it well enough to explain it.
A clean layered backend — auth, roles, product management, image uploads to S3. The goal was a real reference architecture, not a tutorial project. JWT, Spring Security, MongoDB, no shortcuts.
Java and Node.js producers and consumers across topics, partitions, and consumer groups. Modelled after payment event flows. Docker Compose up, everything talking. The goal was to see the guarantees — and the failure modes — firsthand.
Utility-focused Spring Boot web application for file operations and downloadable resource workflows through a browser-based interface. Built as a practical full-stack Java project combining backend services, file I/O, download link generation, and server-rendered Thymeleaf UI.
Writing is How I Test My Understanding.
If I cannot explain something clearly to another developer, I treat that as a signal to understand it better.
A practical guide that goes beyond basic Docker commands. Containers, images, networking, volumes, custom DNS, Compose, Spring Boot and Node in Docker — each piece built on the last. Written for developers who want to actually understand what they're running.
From the TLS handshake to a production-style mTLS setup with Nginx as reverse proxy. Local certificate generation, CA trust, Dockerised deployments. I built the repo first, then wrote until every step made sense without assumptions.
Most Spring Security articles tell you what to configure, not why it works. This one starts with how a CSRF attack actually plays out in a browser, then traces exactly what Spring's token mechanism does and why that breaks it.
Written alongside the PayDan project. Schema design, resolver patterns, real-time subscriptions over WebSocket, full-stack integration. The article and the repo were written in parallel — neither made sense without the other.
Tools I've Used Under Pressure.
Not a wishlist — what I've shipped production code with.
Available for
coffee & ideas.
Good conversations build surprising opportunities. If you're into product ideas, engineering tradeoffs, AI experiments, or thoughtful tech chats, I'm always up for a sharp conversation.
Happy to meet thoughtful people, exchange ideas, and explore interesting collaborations.