as

Abhishek Sharma

— Engineering

Work

Principles

Stack

SOFTWARE ENGINEER

Currently building at Big Oh Tech

NEW DELHI · SOFTWARE DEV

Abhishek

(Sharma)

he / him

I build scalable backend systems that handle complexity with clean, efficient code.

Backend engineer focused on microservices and performance. I bridge the gap between complex legacy systems and modern, modular architecture. I write code that lasts.

PORTFOLIO · NEW DELHI, 2025

Content

SYSTEM PERFORMANCE GAIN

40% faster APIs.

Through strategic code-level optimizations and query restructuring, I cut down latency significantly for Flydocs users.

project showcase, 5 min read

4

MAJOR PROJECTS

From legacy migration to full-stack feature development.

100k+

DOCUMENTS MANAGED

Handled high-volume audit records with secure MongoDB architectures.

99.9%

UPTIME MAINTAINED

Ensured high availability and performance for complex web platforms.

850+

ALGORITHMIC PROBLEMS

Sharpened logic through LeetCode and GeeksforGeeks. See section 06.

EXPERIENCE:

Big Oh Tech

·

Jellyfish Technologies

·

MCA

·

BCA

·

Competitive Coding

01 — MY APPROACH

Clean architecture is the backbone of long-term maintainability.

Every project I touch starts with modularity. By decoupling systems, I ensure that the code is easier to test, scale, and refactor.

Once the architecture is sound, the features naturally follow.

I.

Legacy code is a challenge, not a dead end.

I enjoy the process of dissecting monoliths into microservices. It's about preserving functionality while drastically improving speed.

II.

Optimization is continuous.

Whether it's Redis caching or query restructuring, I look for efficiency in every line of code I deploy.

III.

Security is built-in.

From role-based access to robust audit trails, I ensure that data integrity is never treated as an afterthought.

02 — SIGNATURE WORK

FLYDOCS · MONOLITH MIGRATION · 2025

Transitioned to microservices to scale.

READ IT IN

~4 min

THE PROBLEM

Legacy PHP constraints.

Flydocs relied on a rigid PHP monolith. The system was struggling with scalability and modularity. My goal was to migrate the platform to a performant NestJS microservice architecture.

We needed to ensure traceability for over 100,000 aircraft records without compromising performance.

THE STRATEGY

Modularize and optimize.

I focused on building a secure Audit Trail Service in MongoDB. By restructuring queries and implementing strategic caching, we significantly increased API performance.

I worked on-site to bridge the gap between technical hurdles and business expectations, ensuring the transition was smooth for the end-users.

THE WORK · WEEKS 1–12

WK 1–4

Analyze

Deconstructed the legacy PHP monolith and mapped out the core services for the migration.

WK 5–8

Develop

Implemented NestJS microservices and designed the robust MongoDB audit trail.

WK 9–10

Optimize

Introduced caching mechanisms and performed code-level optimizations to boost speed by 40%.

WK 11–12

Deploy

Managed client site deployments and ensured full system stability during the transition.

"

Abhishek brought a technical discipline to our migration that allowed us to move faster than we ever anticipated. He understands both the code and the business.

— Team Lead, Big Oh Tech

RESULT

40%

API performance boost

03 — HOW I WORK

A structured development lifecycle.

I follow a logical progression: understand the pain point, architect the solution, optimize for performance, and maintain with clean code.

I.

Understand the requirements.

I spend time analyzing the existing tech stack and stakeholder needs. I don't build until I understand the 'why' behind the technical debt.

TYPICAL

1–2 weeks

II.

Architect with scalability.

Whether it's database schema design or choosing between SQL and NoSQL, I document the choices and ensure modules remain decoupled.

TYPICAL

3 days

III.

Refine and optimize.

Post-development is where I focus on performance. Redis, indexing, and efficient code paths make the difference between a prototype and a product.

TYPICAL

2 weeks

IV.

Document and sustain.

Writing clean code and maintaining documentation is critical. I ensure that the next developer can build on top of my work easily.

TYPICAL

Continuous

04 — TRAJECTORY

Evolving from student to professional engineer.

From academic foundations to high-traffic commercial platforms, my career has been about solving increasingly difficult engineering problems.

2025

→ now

Big Oh Tech

— Software Engineer

Working on high-stakes migrations and cloud services. Focused on NestJS architecture and ensuring smooth deployments through on-site collaboration.

Microservices

API Architecture

Optimization

2022

→ 2025

Jellyfish Tech

— Software Engineer

Developed and maintained high-traffic web applications. Mastered the full-stack lifecycle and learned to deliver quality solutions under tight deadlines.

NodeJS/Express

Cloud Integration

Full-Stack

2021

→ 2023

BVICAM

— Master of Computer Applications

Built a strong foundation in OS, DBMS, and advanced data structures. Graduated with honors, focusing on competitive programming.

Algorithms

Databases

Operating Systems

2018

→ 2021

JIMS

— Bachelor of Computer Applications

Early immersion in software development principles and object-oriented programming. Where the passion for coding really began.

OOP

Networks

C++/Java

05 — IMPACT, WITH CONTEXT

Numbers reflect engineering decisions.

Four outcomes I'm proud of, representing the technical challenges I navigated.

40%

2025 · Flydocs

API PERFORMANCE

Improved response times through code restructuring and cache optimization.

100k+

2025 · Flydocs

DOCUMENT TRACEABILITY

Developed a secure Audit Trail system in MongoDB, ensuring complete traceability.

99.9%

2022–2025 · Tpoint Tech

PLATFORM UPTIME

Maintained high-traffic platforms, ensuring reliability during peak user activity.

850+

2023 · Personal

ALGORITHMIC PROBLEMS

Mastered complex structures through LeetCode and GeeksforGeeks to stay sharp.

06 — THE PROBLEM SOLVING LIST

Challenges I've conquered.

Technical growth comes from the problems that force you to stretch. Here are three challenges I've solved.

SOLVED 01 — ARCHITECTURAL DECOUPLING

PatraCorp module decoupling.

PatraCorp · 2024

The system was tightly coupled and difficult to maintain. By utilizing NestJS dependency injection, I successfully decoupled the core modules.

Resulted in a cleaner codebase, easier debugging, and improved long-term maintainability.

SOLVED 02 — DATA INTEGRITY

Election member management.

Nasscom-Election · 2024

Built a robust API for CSV uploads and voting with strict CASL authorization. Ensured that roles were respected at every level.

Learned the importance of strict access control in sensitive data environments.

SOLVED 03 — PERFORMANCE

Redis caching implementation.

JavaTpoint · 2023

Database load was too high during peak hours. By integrating Redis, I cached common content and saw an immediate drop in retrieval time.

Proved that sometimes the simplest architecture change can save the most resources.

07 — RECENT LEARNINGS

Engineering notes.

I enjoy documenting the technical hurdles I face. It helps in solidifying my understanding of the stack I use daily.

MAR '25

Microservices vs Monolith.

5 min

Note

JAN '25

Caching strategies with Redis.

4 min

Blog

NOV '24

Optimizing MongoDB queries.

6 min

Essay

APR '25

Modernizing legacy architectures for scale.

4 min

Project

JAN '24

Improving API performance through caching.

3 min

Technical

08 — PROFESSIONAL FEEDBACK

Reflections from colleagues and project leads.

Selected perspectives from individuals I have collaborated with during my time in software engineering.

"

Abhishek has a great ability to bridge the gap between business needs and technical implementation. His work on our migration projects was instrumental.

Project Manager

Big Oh Tech

"

He consistently maintained high code quality under pressure, even when handling multiple high-traffic projects simultaneously. Very reliable.

Senior Lead

Jellyfish Technologies

"

His technical skills, especially with NestJS and database optimization, have significantly improved the modularity of our backend systems.

Technical Lead

Engineering Team

09 — GET IN TOUCH

If you're building robust backend solutions —

I am a software engineer open to new opportunities in backend development. I specialize in Node.js, NestJS, and scalable microservices. I respond to all inquiries within 48 hours.

ELSEWHERE

LeetCode · /Abhishek_Sharma_1999

LinkedIn · /in/abhishek-sharma-735a9a16a

GitHub · /Abhishek-Sharma-1999

GeeksforGeeks · /Abhishek_Sharma

© 2026 Abhishek Sharma

·

Based in New Delhi, India

Software Engineer · Backend Specialist

Designed onimyme· Create yours