👋 Hey, I'm

Leander Cibi.
SDE-2 at SatSure.

Five years writing production backends: pipelines, search, observability, the boring parts that decide whether anything else gets to be interesting. Off the clock I prototype obsessively: agents, dashboards, swing-trading sandboxes, an NL→SQL middle layer. On weekends, a camera, a list of dishes worth a detour, and whatever's playing at the nearest single-screen.

📍 Bengaluru · willing to relocate ⚙ SDE-2 @ SatSure ⌘ five years in, still curious 🎬 312 films & counting
Leander Cibi
FX3 · 2.39 : 1 REC
Leander Cibi · BLR · 2026
that's me
Shipping since
5yrs
backend, geospatial, agents
Services migrated
5
monolith → microservices, SatSure
Side projects live
4
SwingPick, Cere-bro, DB-Agent…
Where I've worked · 2020 → now

Two companies, five years, one recurring story.

I keep ending up as the person who owns the backend nobody wants to maintain: pipelines, search, observability. And I turn it into something the rest of the team trusts.
Currently5yrs
"Most of my paid work is the 'boring' middle layer the rest of the product gets to stand on."
SatSure Analytics
Jan 2022 → present · Bengaluru
SDE-2 led the monolith → microservices migration · owned architecture decisions and API contracts
Turning satellite pixels into decisions an underwriter will defend.

Lead the migration from a five-year-old monolith to a properly bounded microservices setup, giving us clearer ownership, independent scaling, and a narrower blast radius. Three juniors joined that work and now own services of their own. Most of my mentoring is engineering design: how to read a service, when to push back in product review, what to do with the half-finished thing on the staging branch.

Engineered a hierarchical region-discovery layer with multi-strategy search (direct → fuzzy → phonetic) so messy administrative names resolve cleanly across pan-India geospatial datasets. Built and orchestrated the Airflow pipelines that turn raw satellite tiles into report-ready rasters. Added Redis caching and a Datadog observability stack that catches issues before customers do. Designed the public APIs underneath: versioned, rate-limited, contract-enforced.

+40%API reliability 5services migrated 3search strategies
PythonFastAPIAirflowCeleryPostgres / PostGISRedisDatadogDockerK8s
SDE-1 same company, the chapter before

Owned end-to-end backend of Sparta Maps, the GT data collection platform: API design, database schema, mobile integration. Wrote Bash and Python scripts that automated the geospatial workflows the GIS team used to do by hand, and Streamlit APIs that accelerated raster generation. Most of the tools other engineers ended up reaching for came out of this period.

PythonFastAPIStreamlitGDAL · RasterioBash
I-TechZone
2020 → Jan 2022 · Bengaluru
Software Engineer first production job, first big lesson in ownership
Where production first hit different.

Built full-stack features in a fast-moving product team. Learned fast that production ownership is different from everything the textbooks say: you're on call for what you ship, and the customer timeline doesn't wait for the sprint cycle.

PythonDjangoJavaScriptReactPostgreSQL
B.Tech · Mechatronics
2016 → 2020
Hindustan Institute of Technology and Science · Chennai

Where the loops first made sense. Final year project: an automated IoT home built on a Raspberry Pi. Early lesson in tying software to hardware and shipping the whole loop.

Toolkit · across work & projects

What I reach for, and why.

Covers both work (SatSure, I-TechZone) and personal projects. Backend-heavy by nature, but I've touched enough of the stack to know where the real bottlenecks live.
Languages
Python JavaScript Bash SQL
Backend & data
FastAPI Airflow Celery Django Node.js Streamlit
Stores & search
PostgreSQL / PostGIS Redis Elasticsearch SQLite MongoDB
Geospatial
GDAL Rasterio GeoJSON Shapely PostGIS
Cloud, infra & obs
Docker Kubernetes OCI Datadog GitHub Actions Nginx
Frontend & tools
React HTML / CSS Telegram Bot API Notion API Obsidian
Currently exploring: LLM tool-use, structured output, multi-agent orchestration
Personal projects · side bets I shipped

Off the clock, I build things for myself first.

These aren't portfolio pieces built to impress; they're tools I actually use. SwingPick tells me what to watch. Cere-bro handles my second brain. DB-Agent saves me from writing the same joins.
Right now · live

What I'm actually doing,
updated as it happens.

cached 60s · BLR --:-- IST
Last filmLetterboxd
The Peanut Butter Falcon
Tyler Nilson & Michael Schwartz · 2019
★★★★☆ · 4 / 5
Currently readingBookshelf
Exhalation
Ted Chiang
nine stories · on time, memory, and what persists
Last commitGitHub
swingpick
fix: regime gate respects holidays
2h ago · main
Last tripGeo
Pondicherry
3 days · French Quarter, mostly walking
jun 2026 · shot some 9:16
Reading · blogs I liked

Pieces that made me think long after I closed the tab.

Not a curated list, just what landed. Things I'd forward to someone without needing a reason.
The Weekly Scrapbook
Your phone is the reason you have no attention span

The frame here isn't "phones bad". It's that the feed doesn't just reflect who you are, it decides who you become. The "you are what you pay attention to" line stuck with me for a week.

Read →
Cameron Wolfe · Deep (Learning) Focus
Agentic RL

Best read on why the current agent stacks feel off. The move from flat token rollouts to step-level trajectories is the kind of unlock you only see once you've fought retokenization drift yourself.

Read →
Feifei Writes
How to start having original thoughts

Original thinking is synthesis, not invention. The bit about capturing your raw reaction before you check anyone else's take is what I keep coming back to.

Read →
Reel · 2025 → 2026

When the laptop is shut, I'm making things with a camera.

Started cutting short videos this year; a few pieces so far, plus a roll of stills from the same trips. All shot on a phone, edited on it too. Same loop as engineering: shoot, edit, ship, repeat.
9:16 · Star trails
Star trails, stackedlong exposure, put together in InShot
16:9 · Sikkim
Sikkim, on the move
16:9 · Dawn
First light
Yumthang Valley, Sikkim
Yumthang Valley, Sikkim
Zero Point, Sikkim
Zero Point, where the road ends
Monkeys at Tiger Point, Lonavala
Tiger Point, only the monkeys turned up
The view from Tiger Point, Lonavala
Tiger Point, the actual view
Macro shot
Macro, just because
Bhaje Caves, Lonavala
Bhaje Caves, Lonavala
Macro shot of a small spider
A small spider, up close
Bengaluru at sunset
Bengaluru, at sundown
Bengaluru Karaga ritual
Bengaluru Karaga, mid-ritual
Bengaluru Karaga ritual
Karaga, later that night
About

The shorter version, in my own voice.

I'm an engineer who likes the boring middle layer. The pipelines, the search, the contracts, the parts of a system nobody wants to inherit; those are usually where the real product lives. The interesting work is almost never in the model on top; it's in whether the layer underneath can answer the same question twice the same way.

Five years in, I keep ending up as the person teams hand the messy backend to, and I tend to leave it more readable, more observable, and less expensive to change than I found it. I care about ownership: who's on call for this, what the failure mode is, what we'd say if it broke at 2 a.m. I care about product: what the user is actually trying to do, and whether the system makes that easier or harder.

Off the clock I prototype obsessively: agents, dashboards, telegram bots, small tools that scratch a real itch. Less hobbyist, more practice ground for product thinking: surface, flow, decision, follow-up. And on weekends, a camera, a list of places, and whatever's playing at the nearest single-screen.

The quick details

Based
Bengaluru, India
Role
SDE-2 · SatSure Analytics
Stage preference
Early-stage & scale-up startups
Open to
Product- and engineering-focused roles
Location
Bengaluru · open to relocating abroad
Reach
Email · GitHub · LinkedIn
How I work
Backend first
Pipelines, search, observability, contracts. The boring layer the rest of the product gets to stand on.
What I value
Ownership
Who's on call, what the failure mode is, what we'd say if it broke at 2 a.m. Code that's readable two years later.
What I'm chasing
Product sense
Less hobbyist, more practice ground. Surface, flow, decision, follow-up: the whole arc of how a thing actually gets used.
Now showing · also

And yes, when the work shuts down, I'm at the movies.

Films are the longest hobby I've ever stuck with. They live at the end of this page because they're not what the work is, but they are part of how I think about it.
Admission · ★★★★★ Gate 04 · 21:30

In the Mood for Love

dir. Wong Kar-wai · 2000 · re-watch
★★★★★

A film I keep returning to and never finish thinking about. The restraint is the technique. Half the year I'm trying to write code with the same discipline: fewer moves, each one paid for. Also: 12 Angry Men + Eternal Sunshine on the same shelf, for very different reasons.

logged 2 nights ago on letterboxd →
Total logged
312 films, 4 yrs
avg ★★★★ 3.8 / 5
Currently in heavy rotation
12 Angry Men · Eternal Sunshine
one for the team-lead head, one for the personal one
Best of last quarter
Past Lives
★★★★★ Celine Song. Knows how to wait.
end credits, but first,

Got a hard problem,
or a product worth building?
[email protected]

Open to interesting briefs GitHub LinkedIn