Skip to content
Snehal Prajapati

Independent Full-Stack Engineer

Full-stack engineer for the products you're building next.

I design and build web applications end to end, and modernise older ones without stopping your business.

Start a projectSee the work
Portrait of Snehal Prajapati

About

I build new web products and modernise existing ones: I connect the systems that don't talk to each other, and ship the features that were stuck behind them.

  • 5+

    years building and shipping web applications for businesses, government and enterprise.

  • 03

    domains: property management, public sector and recruiting.

  • 04

    layers covered by one person: front end, back end, data and cloud.

What I can build and fix for you

Most work starts as a conversation about a problem, not a feature list. These are the areas where I'm most useful.

  • Web applications and new products

    Founders, agencies and teams with a product idea or client brief.

    “We have an idea (or a client brief) and need someone to build it properly.”

    React · .NET · Azure

    What's included
    • Requirements turned into a working plan
    • Front-end and back-end build
    • Database design
    • Azure-based deployment
    • Handover and documentation

  • Front-end design and website makeover

    Businesses with an old, slow or hard-to-use website; agencies needing a front-end specialist.

    “It looks dated, it's slow on phones, and nobody wants to touch it.”

    React · Angular · Accessibility

    What's included
    • Modern responsive interface
    • Accessibility basics
    • Performance tuning
    • Reusable components so the site is easy to extend

  • Legacy modernisation and migration

    Teams running older front ends or frameworks that are getting hard to maintain.

    “We're afraid to change it, but we can't stay on it.”

    AngularJS to React · Module by module

    What's included
    • Assessment of what to keep
    • Module-by-module migration so the system stays live
    • Testing alongside the old behaviour
    • Documentation

  • System integration and business problem solving

    Organisations whose data lives in several places and people re-enter it by hand.

    “We have three systems and a spreadsheet that nobody trusts.”

    APIs · Event-driven · SQL / CosmosDB

    What's included
    • Mapping the problem
    • A plain-language plan
    • Integration or a single consolidated view
    • Automation of repetitive steps

  • Cloud design and migration planning (Azure)

    Teams moving from on-premises or ageing hosting towards the cloud, and new products that should be cloud-native from day one.

    “We want out of our old hosting but need a sensible plan first.”

    Microsoft Azure · Planning · Builds

    What's included
    • Target architecture on Azure
    • Migration plan and sequencing
    • Identity and security basics
    • Cost-aware choices
    • Hands-on build of cloud-based applications

  • SEO-friendly websites

    Businesses whose website is hard to find in search, doesn't show up for what they sell, or isn't getting enquiries; and agencies that want the technical side done properly.

    “We have a site, but customers can't find us, and competitors show up first.”

    Technical SEO · Speed · Search Console

    What's included
    • Technical SEO audit of the current site
    • Fixes at the source: page structure, speed, mobile-first layout, prerendered pages, metadata, sitemap, structured data
    • Page titles, headings and descriptions matched to what customers search for
    • Search Console and basic analytics set up in your name
    • Local-business basics where relevant

    What you can expect

    • No guaranteed rankings. Anyone promising "#1 on Google" is selling something they can't deliver.
    • It takes time. Technical fixes can show effects in weeks; competitive terms usually take months of steady work.
    • Clean methods only. No bought links, hidden text or tricks that can get a site penalised.
    • Clear reporting on what changed, why, and how visibility and enquiries are moving.
    • Your site and accounts stay yours.
    • Honest scope. I handle the technical and on-page side; fresh content and reviews are shared work, and I'll say when something is outside what I do.

And afterwards

Ongoing support, review and improvement

A named person after launch: review with prioritised findings, performance and dependency clean-up, small changes on a regular cadence.

Three things I built, drawn

These systems sit inside enterprise products, so I show them as architecture drawings with the reasoning behind each decision, not as screenshots.

System integration · Web applications

One real-time view from scattered office databases

A recruiting platform · 2024 - 2025

  • React
  • .NET
  • Azure Function Apps
  • MS SQL Server
  • CosmosDB
  • MSAL
  • JWT
DISTRIBUTED OFFICESNO SHARED VIEWCHANGE EVENTS, NOT POLLINGRECORD + PROJECTIONSONE REAL-TIME TRUTHOffice DB - AOffice DB - BOffice DB - CAzure Function AppsMS SQL ServerCosmosDBAdmin portalSQL SERVERSQL SERVERSQL SERVEREVENT-DRIVEN PIPELINESYSTEM OF RECORDREAD PROJECTIONSMSAL / JWT
Fig. I - real-time data consolidation from distributed office databases into one system. Swipe the drawing sideways to see all of it.

An application-tracking system that brought recruiting data from several separate office databases into one live, secure view.

The problem

Each office kept its own database. There was no single place to see candidates and applications as they changed.

What I did

Designed and built a secured admin portal and an event-driven pipeline on Azure Functions that pushed changes between SQL Server and CosmosDB as they happened, instead of polling.

What changed

Staff work from one trusted view in place of separate, disconnected systems.

Front-end design · Application development

A large hierarchical data set made usable

A government-grade electoral management system · 2021 - 2024

  • .NET Core
  • Entity Framework Core
  • MS SQL Server
  • Angular 12+
  • Syncfusion
BEFOREAFTER - FOUR RESPONSIBILITIESTHE STACKTHE VIEWGOVERNMENT-GRADE, STRICT AGILEUSABLE AT SCALEONEOVERSIZED COMPONENTEVERY CHANGE A REGRESSION RISKQuery / filterHierarchy builderPaging + virtualisationRender adapterEF CoreASP.NET Core APIAngular 12+MS SQL SERVERPAGED SUBTREESSYNCFUSION TREE-GRID
Fig. II - an oversized component split into focused parts, then visualised through a tree-grid. Swipe the drawing sideways to see all of it.

A tree-grid for exploring deeply nested records at scale, built after untangling the component it depended on.

The problem

A single oversized component had become risky to change, and the data needed to be explored by hierarchy across very large sets.

What I did

Broke the component into focused responsibilities (querying, hierarchy building, paging and virtualisation, rendering) and built the tree-grid on top.

What changed

The code became safe to change again, and people could navigate large nested data without waiting.

Legacy modernisation · Web applications

Property Tree: modernising a live property-management platform

MRI Software · Property Tree · 2025 - Present

  • React
  • AngularJS
  • .NET
  • MS SQL Server
  • Microsoft Azure
LEGACY SHELL · ANGULARJSREACT ISLANDLIVE PRODUCT, IN DAILY USEONE QUERY SHAPE, EVERY MODULEMORE RECORDS, ONE SEARCHMIGRATION PATH - MODULE BY MODULE, NO FREEZETenancyOwnerPropertySearch contract.NET · MS SQLExtended searchTenancy resultOwner resultSINGLE ENDPOINTINDEXED READSREACT ON AZURE
Fig. III - old and new front ends running side by side, one shared contract, module by module. Swipe the drawing sideways to see all of it.

Property Tree is MRI's cloud platform that agencies and landlords use to manage rental properties: tenancies, owners and properties, invoicing, receipting, inspections and online access for owners and tenants. I work on its core modules while its front end moves from an older framework to a newer one.

The problem

A product used every day by agencies, with an older front end that was getting harder to extend.

What I did

Replace the front end one module at a time, with old and new running side by side so nobody's working day is interrupted. I led the AngularJS to React migration and extended the existing global search to cover more kinds of records.

What changed

A front end that is easier to maintain and extend, and capabilities such as a broader cross-module search that can grow without being held back by the old structure.

How we'd work together

  1. Discover

    A conversation about the problem, users and constraints. I ask the awkward questions early.

    You get

    A short written summary of what we agreed

  2. Plan

    Scope, approach, milestones and risks laid out in plain language.

    You get

    A plan you can approve, change or take elsewhere

  3. Build

    Work in small, visible steps, with regular updates and working software you can try.

    You get

    Updates you can follow without technical knowledge

  4. Hand over

    Documentation, repository access and a support window after delivery.

    You get

    Code your team (or the next developer) can maintain

Pricing is agreed per project once the problem is understood: fixed scope, or time-based for ongoing work.

Directly with you, or alongside your team

Directly with you

You get one independent engineer who understands the problem, plans it in plain language, builds it, and hands it over. No account managers in between.

  • One named person from first call to handover.
  • Plain-language plans and regular updates.
  • Code and accounts in your name, documented.

Alongside your agency or team

If you run an agency or consultancy and need dependable engineering capacity, I can join your project as a partner.

  • Confidential by default; happy to sign an NDA before we talk specifics.
  • Clean handover into your repositories.

Flexible overlap: meetings arranged to suit your timezone, with delivery work done in Indian working hours.

Where the work happened

  1. Jul 2025 - Present

    MRI Software · Software Engineer II

    Property Tree: led the AngularJS to React move and extended global search.

  2. Jun 2024 - Jul 2025

    Reflik · Software Engineer

    Designed and built a real-time application-tracking system and its Azure pipeline.

  3. Sep 2021 - Jun 2024

    Civica India · Software Engineer

    Electoral management system: component refactor and a hierarchical tree-grid.

  4. 2017 - 2021

    Neotech Institute of Technology · B.E. Computer Engineering

The tools I work with

Front end

  • React.js
  • Angular
  • AngularJS
  • TypeScript
  • JavaScript
  • HTML5
  • CSS3
  • MUI
  • Syncfusion Component Library

Back end & data

  • .NET / ASP.NET Core
  • C#
  • RESTful APIs
  • Entity Framework Core
  • MS SQL
  • CosmosDB

Cloud & architecture

  • Microsoft Azure
  • Azure Function Apps
  • Event-Driven Architecture
  • MSAL
  • JWT

Practice

  • Git
  • Agile / Scrum
  • Code Review
  • Kanban

Tell me what you're building.

Describe the idea, the problem or the page that needs fixing. A few sentences are plenty; I'll reply with questions or a straight answer on whether I can help. Email gets read the same day.

Email
[email protected]
Phone
+91 9106721561
Elsewhere
LinkedInGitHubRésumé (PDF)
Message me on WhatsApp

So I can reply

A short description is enough: what you're building or what's not working

I'm looking for (optional)

Optional. Helps me suggest the right approach

By sending this, you agree I may use your details to reply to you. See the privacy notice.

Privacy

This site is a personal portfolio. It collects only what you choose to send through the enquiry form.

Updated October 2026

What I collect
The details you type into the form: your name, email address, your message, and, if you add them, company, project type, timeline and budget range.
Why
Only to read your enquiry and reply to you. I don't add you to mailing lists or share your details for marketing.
Who handles it
I read it myself. The message passes through the website host and an email delivery service on its way to my inbox.
How long I keep it
For as long as it takes to respond, and up to 12 months afterwards unless we end up working together.
Cookies and tracking
This site doesn't use advertising or tracking cookies. Basic visit counts may be collected without cookies and without profiling individual visitors.
Your choices
Ask me to show or delete anything you've sent, by emailing the address on this page.
Questions: [email protected]