Danish
Javed.
Five years building FinTech systems
used in real payment workflows.
I build and lead delivery of software in 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 — And Help Others Finish
Features don't count until they're in production and working. I track the full journey — design discussions through deployment to monitoring — and make sure the team lands it together. 143 PRs is what that 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 — not optional. That standard shapes every line I ship.
Promoted based on sustained delivery and growing influence on how the team works. I lead projects — not just write code for them. Payment Plans was mine from design discussions through production: I guided the team through implementation, reviewed their PRs, managed stakeholder expectations, and adjusted timelines when scope shifted. My own code lands clean: 100% merge rate in 2026, zero reverts.
- Led the security hardening initiative across the customer portal — XSS prevention, error response fixes, HTML injection remediation — spanning 100+ files across multiple releases. This meant running impact analysis, coordinating with stakeholders on rollout timing, and guiding team members through unfamiliar areas of the codebase.
- Drove a platform-wide password policy rollout across 47 files and 3 release cycles. When the first deployment had to be reverted because billers weren't given advance notice, I owned the communication gap — built biller identification tooling, aligned notification timelines, and redelivered cleanly.
- Actively review PRs across the team — not just for correctness, but for design direction, consistency, and whether the approach will hold up at scale. That's where most of the mentoring happens.
- Added observability instrumentation to a critical notification pipeline. When notifications got stuck in maintenance mode in production, I traced the root cause and shipped the fix the same day.
Core engineering on a FinTech platform processing over $1B annually. Over two years, I grew from handling isolated bug fixes to owning cross-system features and participating in design decisions that shaped how the team approached new work. By the end of this period, my code was landing with 66% fewer review comments than when I started, on PRs that were 6x larger — and I was increasingly the person others came to when something in the payment flow didn't make sense.
- Traced a production query that was taking 50 seconds per run, rewrote it, and got it down to 9 milliseconds. Still running in production today.
- Built Recurring Maintenance Mode end-to-end — a 29-file feature spanning Java services, FTL templates, and admin configuration.
- Integrated Google Pay into the payment flow, including tokenized iframe support and follow-up production fixes.
- Shipped an alert mechanism for scheduled payment failures — because production stability isn't just about code, it's about knowing when something breaks before customers do.
- 143 pull requests over the full tenure. The number reflects consistency, not a sprint.
Full-stack delivery across client engagements — Java backend, Angular frontend, Node.js services. Multiple simultaneous projects, fully remote. This is where I learned that clear communication is a prerequisite for good engineering, not a nice-to-have.
First real engineering role. Java, Angular, iterative delivery. The year I learned that debugging someone else's code teaches you more about a codebase than writing your own — and that reading code carefully is an underrated skill.
Six months at a global technology consultancy. Java, Maven, professional engineering practices. Where I learned that professional code has a different standard than academic code — and decided that's where I wanted to be.
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.