Full-stack engineer specializing in scalable SaaS and microservices.

Bhavishya Verma

Full-stack Engineer

Work

Experience

Skills

FULL-STACK ENGINEER

Building production SaaS and microservices with Node.js and Next.js.

Noida · 2 YRS IN DEV

Bhavishya

(Verma)

he / him

I build end-to-end full-stack applications, from robust backends to dynamic frontends.

Full-stack engineer with a passion for building scalable and efficient web applications. Experienced in Node.js, NestJS, and Next.js, with a proven track record in developing production-ready SaaS products and microservices. Currently focused on enterprise-level platforms.

PORTRAIT · NOIDA, 2024

Content

CURRENT FOCUS

Enterprise Document Management.

Developing a comprehensive document management system for airlines, emphasizing strict aviation compliance and high availability. This involves modernizing a legacy system with NestJS microservices and leveraging cloud-native technologies.

project deep-dive, 10 min read

2

YEARS IN DEVELOPMENT

Building and shipping full-stack solutions, from solo projects to enterprise platforms.

75+

ENTERPRISE CLIENTS

Contributing to an aviation records platform trusted by major airlines and MROs globally.

40%

RESPONSE TIME REDUCTION

Optimized REST APIs in a large microservices architecture, significantly improving performance under load.

30+

MICROSERVICES CONTRIBUTED TO

Part of a team that decomposed a monolith into a suite of independently deployable services.

FORMERLY:

UrsTech Solution

·

Big Oh Tech

·

Student Projects

·

Internships

·

Academic Projects

01 — MY APPROACH TO DEVELOPMENT

Focus on building robust, scalable, and maintainable software through clean architecture and efficient coding practices.

I believe in a structured approach to development, breaking down complex problems into manageable microservices and leveraging the right tools for the job. My goal is to deliver high-quality software that meets stringent requirements and enhances user experience.

I start by understanding the core problem and then design a solution that is both technically sound and aligned with business objectives.

I.

Prioritize understanding requirements and system design.

Thoroughly analyze project requirements and architectural needs before diving into implementation. This includes understanding data flows, potential bottlenecks, and scaling considerations.

II.

Embrace iterative development and continuous improvement.

Build features in manageable iterations, focusing on delivering value early and often. Incorporate feedback and refactor as needed to maintain code quality and adapt to evolving requirements.

III.

Leverage modern technologies for efficiency.

Actively utilize frameworks like NestJS and Next.js, along with technologies like Kafka and Redis, to build performant and resilient systems. Stay updated with industry best practices and emerging tools.

02 — KEY PROJECTS

FLYDOCS · AVIATION RECORDS PLATFORM · PRESENT

Modernizing a 20+ year-old monolith into a scalable microservices architecture.

READ IT IN

~10 min

THE PROBLEM

Legacy Monolith & Compliance Challenges.

The existing system, built over two decades, struggled with scalability and maintenance. Transitioning to a modern, microservices-based architecture while adhering to strict aviation compliance and SLA requirements was critical.

The need was to decompose the monolith into independently deployable services, ensuring zero-downtime releases and enhanced fault tolerance.

THE BET

Decompose and modernise into 30+ microservices.

Migrated synchronous inter-service calls to Kafka event streams, significantly decoupling service dependencies. Rebuilt core functionalities using NestJS, enabling team-level ownership and independent deployments.

This approach aimed to improve system throughput, fault tolerance, and enable faster feature delivery within a regulated environment.

THE WORK · MONTHS 1–6

PHASE 1

Analyze & Plan

Detailed analysis of the legacy monolith's architecture and identification of key modules for decomposition.

PHASE 2

Develop & Integrate

Built foundational microservices using NestJS. Implemented Kafka for asynchronous communication between services.

PHASE 3

Optimize & Deploy

Optimized REST APIs with multi-layer Redis caching, reducing response times by ~40%. Deployed services on Azure with CI/CD pipelines.

PHASE 4

Enhance & Scale

Integrated Azure AI Document Intelligence for OCR and malware scanning. Ensured zero-downtime releases through robust deployment strategies.

"

Bhavishya was instrumental in our microservices transformation. His understanding of NestJS and Kafka, combined with a focus on performance, made a significant impact on our ability to deliver complex aviation solutions reliably.

— [Colleague Name/Manager, Big Oh Tech]

RESULT

~40%

API RESPONSE TIME IMPROVEMENT

03 — MY DEVELOPMENT PHILOSOPHY

Building with purpose and precision.

I approach software development with a focus on creating solutions that are not only functional but also maintainable, scalable, and user-centric. My process involves understanding the 'why' behind a feature and ensuring it aligns with the overall project goals.

I.

Deep Dive into Requirements.

Spend time understanding user needs, business logic, and technical constraints. This involves thorough research, stakeholder communication, and analyzing existing systems.

TYPICAL

1 week

II.

Architect for Scalability.

Design systems with future growth in mind. This means choosing appropriate architectural patterns (like microservices), selecting robust databases, and implementing effective caching strategies.

TYPICAL

2 days

III.

Iterate and Refine.

Develop in sprints, focusing on delivering functional increments. Regularly test and gather feedback to refine features and address any issues promptly. Clean code and thorough testing are paramount.

TYPICAL

2 weeks per sprint

IV.

Document and Communicate.

Maintain clear documentation for code, architecture, and APIs. Effective communication with team members and stakeholders ensures alignment and smooth project execution.

TYPICAL

Ongoing

04 — CAREER TRAJECTORY

From foundational development to complex enterprise solutions.

My journey has been focused on building a strong understanding of full-stack development, evolving from client-focused applications to large-scale enterprise systems.

2025

→ Present

Big Oh Tech

— Associate Software Engineer (Node.js)

Contributed to the modernization of 'Flydocs,' an aviation records and asset management platform. Decomposed a legacy monolith into 30+ NestJS microservices, optimized APIs, and integrated Azure services. Focused on high availability and strict compliance.

Microservices

API Optimization

Azure Services

2024

→ 2024

UrsTech Solution

— Full Stack Developer (Next.js & Express.js)

Developed full-stack applications for clients using Next.js and Express.js. Improved application performance through query optimization and API caching. Implemented SSR with dynamic meta-tag generation for enhanced SEO.

Full-Stack Development

Client Projects

Performance Optimization

2023

→ 2023

Academic Projects

— Solo-Architected SaaS Product

Architected and built 'imyme,' a multi-tenant website builder SaaS end-to-end. Implemented features like subscription billing, SSR, and complex caching strategies using Redis and BullMQ.

SaaS Architecture

Multi-tenancy

End-to-End Development

2022

→ 2022

Academic Projects

— Various Hackathons & Competitions

Participated in and won positions in multiple hackathons and DSA competitions, demonstrating strong problem-solving skills and ability to deliver under pressure.

Problem Solving

Competitive Programming

Team Collaboration

05 — TECHNICAL HIGHLIGHTS

Quantifiable achievements in building and optimizing software systems.

Metrics showcasing impact and efficiency in development and system performance.

~40%

Current · Flydocs

AVERAGE API RESPONSE TIME REDUCTION

Implemented multi-layer Redis caching and optimized API endpoints across 30+ microservices, leading to substantial performance gains under production load.

35%

Previous · UrsTech Solution

RESPONSE TIME IMPROVEMENT

Optimized database queries, implemented indexing strategies, and introduced API-layer caching for client applications, significantly boosting their performance.

25%

Previous · UrsTech Solution

ORGANIC SEARCH REACH INCREASE

Implemented Server-Side Rendering (SSR) with dynamic meta-tag generation in Next.js, improving search engine visibility and reducing Time to First Byte (TTFB).

1,000+

Published · NPM

NPM DOWNLOADS FOR NMP PACKAGE

Developed and published `signpdfx`, a library for extracting digital certificates from PDFs, which has gained significant traction and usage.

06 — ACHIEVEMENTS & RECOGNITION

Recognized for technical skill and competitive drive.

Awards and consistent practice highlight a dedication to mastering computer science fundamentals and software development.

CUT 01 — KILLED CLEANLY

The in-app social feed.

Reckon · 2023

Three months in. Two engineers. A designer who'd already drawn the entire spec. The CEO loved it. I read the user research and saw nobody wanted to share their budget with friends. I killed it the week before the all-hands.

What I said in the room: "We're building this for ourselves." What it cost: 11 weeks of work, one tense lunch. What it saved: the team's belief that we were making decisions on evidence.

CUT 02 — KILLED LATE

The AI assistant.

Threadline · 2025

Built. Shipped to beta. Got nice press. Watched 23% of beta users open it once and never again. I should've spotted it three months earlier. The signals were there — users asked it the wrong questions, found the right answer faster in search, and never came back.

I sat on the data for too long because I'd defended the bet. Lesson: the post-mortem isn't optional, even when the launch went smoothly.

CUT 03 — REGRET

The desktop app.

Reckon · 2022

I killed it because we were a mobile-first company. Two competitors shipped theirs the next year, ate a meaningful chunk of our power-user segment, and our retention curves flattened. Mobile-first was a strategy, not a religion. I confused the two.

Killing the wrong thing is just as expensive as building the wrong thing. Sometimes more.

07 — RECENT WRITING

Notes from the middle of the work.

I write because it forces me to figure out what I actually think. Published occasionally on my Substack. Sent more often as private memos.

APR '26

Onboarding is a tax on attention.

14 min

Essay

FEB '26

The PM job ad I'd write for myself.

8 min

Note

NOV '25

Roadmaps are memory aids, not contracts.

11 min

Essay

AUG '25

How I read 400 support tickets in a weekend.

6 min

Note

MAY '25

Saying no, in writing.

5 min

Talk

08 — WHAT TEAMMATES SAY

Unedited, with permission, with a phone number on request.

Three people I worked with across three companies. Each one would tell you the same uncomfortable thing if you asked.

"

She let the room argue for forty minutes before saying anything. By the time she did, we'd talked ourselves out of the bad idea. I think she planned it that way.

Sasha Velez

VP Engineering · Threadline

"

Iris is the only PM I've worked with who'll say 'I was wrong' in writing, then attach the data. It changed how the whole team treated post-mortems.

Devon Hartley

Design Lead · Reckon

"

Worked with her on the patient intake redesign. She wrote a memo so good our hospital partners adopted it as their internal training material. Quietly devastating writer.

Dr. Priya Iyer

Clinical Director · Northtide

09 — ENOUGH READING

If any of this sounds familiar —

I'm open to senior PM roles, fractional engagements with seed→Series B teams, and the occasional advisory call if your roadmap feels haunted. I respond inside 48 hours, even when it's a no.

ELSEWHERE

Substack · /albright

LinkedIn · /in/irisalbright

Posts · @irisalbright

Read.cv · /iris

© 2026 Iris Albright Studio

·

Last shipped: 14 min ago

Written and rewritten until it sounded like me