Software Engineer 3 · Backend systems

Hi, I’m Somen.

From the interface
to the system.
I build the whole story.

I started with interfaces. Today I own backend services from architecture to production. I care about both sides: how a product feels, and how reliably it works.

Explore selected work
Two sides. One product.Try a layer

An interface people can use.

Vue and Nuxt interfaces, responsive layouts, and merchant dashboards that turn a workflow into a clear next step.

Vue · Nuxt · Responsive UI

A visual sketch of my craft, from the screen to production.

Vue & NuxtNode.js & TypeScriptSystems & scale
6Microservices owned end to end
~300kMonthly active users on Vision
Architecture through operations.Development, testing, CI/CD, and deployment

01 / Selected work

Systems with
real responsibilities.

Hackathon platforms, catalog search, and commerce operations. Different problems, the same focus on ownership and performance.

01

Hackathon platform

Vision

End-to-end ownership of six microservices supporting hackathon experiences, mentor bookings, and new ways to participate.

Node.jsKafkaRedisMicroservices
Product workflowsParticipation. Mentorship.
Evaluation.
MeetupsPrompt WarsEmail tracking
Explore my work on Vision

The work

Implemented Kafka event streaming, Redis caching, and query optimization. Built mentor–mentee booking with calendar integration, email pixel tracking, and Prompt Wars with AI evaluation.

Ownership at scale

Responsible for development, testing, deployments, CI/CD, and production operations. Optimized the platform to support around 300,000 monthly active users.

02

Shopify catalog search

Sparq

Search and synchronization for large product catalogs, with attention to indexing speed, operational cost, and store data freshness.

TypeScriptKoaPostgreSQLLucene
Search pipelineFrom a changing catalog
to a useful result.
SyncIndexSearch
Explore my work on Sparq

Search and synchronization

Built a wrapper over Lucene for fast search and worked on product synchronization for Shopify catalogs. Led development and supported improvements to the synchronization pipeline.

Infrastructure decisions

Migrated object storage from AWS S3 to Cloudflare R2 and deployments from DigitalOcean to Azure Container Apps. Used Redis, Jest, and GitHub Actions in the delivery workflow.

03

BigCommerce operations

Trackorder

Built a delivery tracking dashboard from scratch so merchants could monitor orders, configure views, and trigger custom emails.

Node.jsVue / NuxtPostgreSQLAzure
End-to-end deliveryA merchant’s delivery workflow,
in one place.
Track ordersConfigure viewsNotify customers
Explore my work on Trackorder

From concept to launch

Led a team of four developers, one QA, and one designer. Owned frontend and backend reviews and helped take the BigCommerce application live.

Delivery and reliability

Deployed on Azure Container Apps with autoscaling. Used PostgreSQL for application data, Jest for tests, and GitHub Actions for continuous delivery.

My developer story

One layer led
to the next.

Frontend work taught me to see the user. Backend work taught me to see the system. Ownership brought them together.

01 / THE INTERFACE

I started with what people see.

At TO THE NEW, I worked on mobile and desktop interfaces. That foundation helped me understand layout, responsiveness, and the experience on the other side of an API.

02 / THE PRODUCT

Then I built across the stack.

Trackorder brought Node.js services, PostgreSQL, and Vue/Nuxt dashboards together. I led four developers, one QA, and one designer to take the application from scratch to launch.

03 / THE SCALE

I learned to look beneath the surface.

With Sparq, I worked on catalog search, indexing, synchronization, and infrastructure migrations. A useful interface depends on fast results and dependable data behind it.

04 / THE OWNERSHIP

Today, I carry it into production.

At Vision, I own six microservices end to end. My work spans product features, Kafka, Redis, query optimization, testing, deployments, and production operations.

02 / Engineering approach

Make complexity
easier to own.

01

Start with boundaries.

Give each service a clear responsibility. Understand the workflow and its dependencies before deciding where the code belongs.

02

Make performance deliberate.

Look at queries, indexing, and repeated reads. Use caching and asynchronous work where they address a concrete bottleneck.

03

Carry the work into production.

Testing and delivery are part of the feature. Take responsibility for deployment, operations, and what happens after the release.

03 / Experience

A builder.
And an owner.

Current focus

Software Engineer 3 · Vision

Backend engineering and independent ownership across six microservices, from feature development to production operations.

Commerce & search

Green Apple Solutions

Worked on Sparq and Trackorder. Built search and merchant tooling, led development, and improved infrastructure and delivery workflows.

Foundations

TO THE NEW · Frontend Engineer Trainee

Built interfaces for mobile and desktop, developing a practical understanding of the product experience beyond the API.

04 / Contact

Let’s talk about
what you’re building.

Backend engineering, performance, and taking a system from idea to production.

Connect on LinkedIn