Ritvik Dayal Senior Software Engineer
Who Work Source Track Stack Contact
your tap · 34 ms ago
stacked drawing layers
1.2 million lit dots
glass · 0.2 mm apart
the part that decides
memory, handed out in blocks
every app gets a private map
turns taken, 1000× a second
the outer envelope
where to · where from
the actual message
1500 bytes, no more
ask the top of the tree
then who owns .com
an address, at last
13 strangers pass it along
a rack, one of thousands
power, overhead
cold air in, hot air out
an agent is watching the logs
picks a machine that's free
seen this one before?
narrowing, half at a time
one row, found
bytes become structure
everything gets a place
painted, dot by dot
all of it, inside 16 ms
01the tap
ina fingertip→outa signal

You touch
glass.

One tap. Seven layers now have to cooperate to answer it, and each one hands its work to the next. Follow the whole chain down.

02the order
ina signal→outa decision

Software
keeps order.

Hundreds of programs, one chip, a thousand handoffs a second. Something decides who goes next — and what happens when one of them fails.

03the transmission
ina decision→out1,500 bytes

The ask gets
wrapped and sent.

A parcel inside a parcel inside a parcel. Every layer is a note for whoever handles it next, and none of them may read what's inside.

04the route
ina name→out13 hops

Nobody knows
the whole way.

The name is traded for an address, then the parcel is passed between strangers who each know only who's next. Reliability is won or lost here.

05the room
ina request→outa queued job

It lands in a
room that hums.

Aisles of machines, cold air in and hot air out, and an agent reading the logs at 3 a.m. so nobody gets paged. This is the floor I work on.

06the processing
ina queued job→outone row

Data becomes
an answer.

A doorman, a cache, a pipeline, a sorted index that halves the search at every step — until billions of rows collapse into the one you asked for.

07the return
inone row→outlight

And then,
light again.

Back up all seven layers and painted onto glass inside sixteen milliseconds. My job is the middle five — the ones you never see fail.

01
02
03
04
05
06
07
00
layer 01 · surface
5 layers · 1.2 M lit dots
layer 02 · kernel
312 programs · 1 referee
layer 03 · transport
4 wrappers · 1500 bytes
layer 04 · network
name → address · 13 hops
layer 05 · platform
40,000 machines · 92 MW
layer 06 · data
4.1 B rows · 900 µs
layer 07 · return
round trip · 16 ms
Ritvik Dayal · portfolio

Under
the Hood

Seven layers stand between a tap and an answer, each one handing its work to the next. I'm a senior software engineer who builds and holds up the middle of that chain. Scroll down through it — the work is on the other side.

scroll to descend
layers 02 to 06 are my job keep scrolling
01 who

I build the layers you just flew through.

Senior software engineer, five-plus years on AI platforms, distributed backends and cloud infrastructure. I've proposed, won buy-in for, and shipped two production platforms end to end — an AI incident-investigation system and a browser-based BIM authoring platform — and I tend to be the one who turns a manual process into something that runs itself.

Based in Noida, working remote with teams in the US. I cut cloud costs, harden systems for SOC 2, and mentor engineers across a six-hour time gap. Recognised company-wide with the Q1 2026 award for Exceptional Innovation and Advancement in AI.

100×
lower cost per
incident investigated
$35K+
saved per year on
licences and time
500+
production incidents
auto-investigated
3 min
average, down from
15–60 by hand
02 selected work

Five things I proposed, built, and shipped.

01 Doxel · 2026 Latest

BIM review and markup, in a browser tab

Reviewing a model used to mean Navisworks or AutoCAD on a workstation, a paid seat for every reviewer, and a file shipped around by hand. This replaces all of that with a link: open the model in a browser, walk it in 3D, draw straight over the floor plan, and leave the markup where the next person will find it.

The 3D model, the 2D floor plan and site imagery share one review surface, so a comment can point at the geometry instead of describing it. People who never had a desktop licence can now take part in the review, and the model never has to leave the platform to get looked at.

2 → 0
desktop licences to
review a model
3D + 2D
model, floor plan and
imagery in one view
50,000+
elements, rendered in
a browser tab
1 link
to open a review,
nothing to install
3D
MARKUP
model and plan, one review surface
Replaces Navisworks · AutoCAD three.js · WebGL Floor-plan markup React PostGIS
02 Doxel · 2025

AI incident-investigation platform

Every PagerDuty incident used to cost an engineer 15–60 minutes of digging. I architected and shipped an LLM-agent platform with 22+ tools — code search, git history, the production database, Datadog, Jira — that investigates on its own and posts root-cause analysis straight to Slack.

Proposal to prototype in three days, prototype to production in four weeks on GKE. It grew into a company-wide platform with 12 integrations, an org-wide MCP server, 1,000+ unit tests and a self-learning feedback loop — closing the six-hour overnight gap between the India and US teams.

< 3 min
average investigation
vs 15–60 manual
$0.10–0.40
per incident, against
~$25 of engineer time
80%
rated helpful by
on-call engineers
23
auto-generated
draft fix PRs
22 TOOLS
1 AGENT
one spine, every source it can read
LLM agents MCP server · 7 tools GKE Terraform · Helm Datadog · PagerDuty
03 Doxel · 2025

Browser-based BIM authoring & review

A zone-authoring workflow spread across three commercial desktop tools and two teams, with a multi-day handoff in the middle. I proposed and designed a single web app to replace it, then built it end to end from solo proof-of-concept to production.

A three.js/React viewer rendering 50,000+ element BIM models in-browser, a 2D floorplan editor with wall snapping, PostGIS-backed zone geometry, and an async write path over REST and Airflow. Duplicate zone drawing across two teams disappeared; the cross-team handoff collapsed into a same-tool review.

$35K+
saved per year in
licences and time
3 → 1
desktop tools folded
into one web app
50,000+
model elements
rendered in-browser
30+
PRs merged, POC
to production
→
WEB
three desktop tools, one browser tab
three.js · WebGL React · Vite PostgreSQL · PostGIS FastAPI Airflow
04 GeeksforGeeks · 2022

Code-execution architecture around an existing compiler

The obvious answer to running learners' code was to build a compiler service. We didn't. I designed the system around the compiler that already existed — an IDE-like execution server that wraps it in a Docker sandbox, isolates multi-language runs, and treats the toolchain as a dependency rather than a product.

The architecture was the win: 30–40% less cost and complexity than building and maintaining our own, 20% less compute at peak traffic, and Python and Go supported on day one instead of one language at a time.

30–40%
less cost and
complexity
−20%
compute at
peak traffic
0
compilers written
or maintained
−25%
API latency on the
surrounding backend
CC
SANDBOX
wrap the compiler, don't rebuild it
System architecture Docker sandboxing Python · Go Microservices
05 Doxel · 2023–2025

The unglamorous half: cost, latency, CVEs

Re-architected entity-element mapping from synchronous APIs to async Kubernetes jobs across four repositories, cutting hot-path response times 25–45% with caching. Right-sized Kubernetes compute for Airflow pipelines with Terraform and took 10% off cloud compute while making reliability better, not worse.

Shipped infrastructure security checks that lifted security posture 35% by Vanta's measure, directly supporting SOC 2 procurement. In one hardening sprint: 406 unit tests across 15 previously untested modules and 19 CVEs patched. Mentored three engineers from junior to senior along the way.

25–45%
faster hot-path
API responses
+35%
security posture,
SOC 2 support
406
unit tests across 15
untested modules
19
CVEs patched in one
hardening sprint
LATENCY · COST · CVEs
every number pointing down
On the table
Proposal · benchmarked

Vision-language shadow annotator

A design proposal, not a shipped system: VLM inference with cross-frame consensus and graph propagation, aimed at removing 60–70% of manual BIM element annotation. I built the case with numbers before asking anyone to fund it.

663
ground-truth
cases
4
models
compared
$0.046
best run, 100%
precision
03 open source

Shipping to strangers
is a different job.

FeatherWall is my first open-source project. A live-wallpaper engine for Windows 10 and 11 in 7.5 MB — one process, no bundled browser engine, which is the whole point and the reason it stays out of your RAM. It went public under MIT on 15 August 2026. What follows is what came back.

First open source · MIT

FeatherWall

Video and image wallpapers per monitor, a designed clock widget drawn as an overlay, auto-pause when something takes the foreground, and a self-healing re-attach for when the desktop rebuilds itself underneath you. The category standard is to ship a browser engine to draw a clock. This one doesn’t.

C# Windows 10 / 11 No browser engine Repository →
18
github
stars
7.5 MB
the whole
application
0
browser engines
bundled
v0.1.0
shipped
15 aug 2026
What came back Reddit · 15–16 Aug 2026
5
subreddits,
~24 comments
84
of ~118 github
referrals
111
clones in the
first days
187
repository
views

Carried by r/desktops — “No Wallpaper Engine, no Chromium, 7.5 MB Open Source App” — at 25 points and 12 comments, then r/coolgithubprojects at 9. Four concrete asks came out of it, and every one is on the v0.2 roadmap.

01
A weather widget — and the asker raised the lightweight tension themselves. satosru
02
Separate font settings for the date and the time, from someone two days into daily use. Ok_Algae_8222
03
Widgets that go idle — “the clock just stays still until the user minimizes an app”.
04
A measured comparison against Wallpaper Engine, Lively and DesktopHut, asked in two independent threads — one of them had uninstalled both over RAM. Old-Birthday3202

One commenter, scandii, doubted the GPU numbers I had published. They were right to. I re-measured, the original explanation did not survive contact with the benchmark, and the README was corrected the next day.

The most useful thing anyone said all week

Next in the open Nov 2026
Research prototype · MIT

SIRIUS

A second pair of eyes for people who are blind or have low vision. Two webcams on a ruler work out how far away things are, a detector names them, and a voice says it in a few words: person, one metre, ahead. It runs offline on a laptop today; the next build puts the cameras on a worn Raspberry Pi.

Python Stereo depth Offline speech Project page → Repository →
2
cameras, about
12 cm apart
17
kinds of object
it names
~50 ms
for the voice
to start
73
tests in
phase 1
04 track 2021
2025 — presentDoxel · Remote, USA
Software Engineer III

Nobody handed me
the spec.

I look for the workflow quietly costing us money, build the case with numbers, win the buy-in, and then own it end to end. The browser BIM review tool and the AI incident platform both started as proposals nobody asked for — and both are in production.

2023 — 2025Doxel · Remote, USA
Software Engineer II

Two years learning
where things break.

The unglamorous half, on purpose: security posture for SOC 2, Kubernetes right-sized against real pipeline load, redundant deployments deleted, containers where there were none. This is the stretch that taught me what a platform actually costs to keep alive.

2021 — 2023GeeksforGeeks · Noida
SDE II

Real traffic, and a
hard lesson in reuse.

A microservice backend under genuine load — XSS-class holes closed, latency down a quarter. Then the call I still quote in design reviews: build the architecture around the compiler that already existed rather than writing one. Less to own, less to go wrong.

Apr — Nov 2021Disecto · Remote, India
Backend Engineer

Where it started:
ship, then ship again.

Backend engineer on a team spread across three cities, integrating third-party calling services and leading delivery on two projects. Ten features out the door in seven months — the habit everything since has been built on.

2
platforms shipped
3
engineers mentored
Q1 2026
company AI award
+35%
security posture
−10%
cloud compute
3
deployments removed
−25%
API latency
30–40%
less cost & complexity
25,000
member community
10
features shipped
2
projects led
3
cities, one team
2026
2024
2022
2021
2017 — 2021

B.Tech (Honours), Computer Science

Dr. A.P.J. Abdul Kalam Technical University, Uttar Pradesh, India

05 stack

The tools, by layer.

AI / LLM systems
LLM agents (Claude)Agent tool designMCP serversVision-language modelsPrompt engineeringLLM evaluation & cost optimisation
Cloud & infrastructure
GCP · AWSKubernetes (GKE)Terraform · HelmDockerAirflowGitHub Actions CI/CD
Backend & data
FastAPI · REST APIsMicroservicesPostgreSQL / PostGISRedisETL pipelinesDatadog · PagerDuty
Languages · frontend · 3D
Python · Go · SQLTypeScript / JavaScriptReact · Vitethree.jsWebGL / WebGPU rendering

Exceptional Innovation and Advancement in AI

Q1 2026

Company-wide award at Doxel, recognising the AI platform work — including the incident-investigation platform.

Smart India Hackathon — Winner

Jan 2020

Led development of a tool to analyse and visualise CDR and IPDR data, winning a national team-based hackathon.

06 contact

Got a layer that
needs holding up?

AI platforms, distributed backends, cloud architecture, or the security work nobody volunteers for. I'm happy to talk through any of it.

Email
ritvikr1605@gmail.com
LinkedIn
in/ritvikdayal
GitHub
ritvikdayal
Résumé
PDF ↓
Ritvik Dayal · Noida, Uttar Pradesh, India Built in the browser · WebGL