About

Why this company exists

There’s a gap that’s been obvious to everyone in this industry for years and that nobody sensible has fixed. Genuinely senior engineers exist in plenty of places that aren’t San Francisco or London. Companies that need them mostly can’t find them, and when they do, they get routed through an agency that takes the margin and hands the work to whoever’s free.

We’re not the first people to notice this. We’re just trying to do it without the parts that make it not work — the account manager between you and the engineer, the senior person who sells and then disappears, the team of twelve that turns out to be a team of two.

So: four specialists who each own their part, and you talk to the people writing your code.

How we’re set up

We’re in both places. The technical work is done from Kathmandu, on a shift chosen to overlap you rather than us: the whole UK working day, and the US morning through to early afternoon. Our week runs Sunday to Friday.

Crimson Umbrella Technologies is the trading name of two companies. They’re separate legal entities operating under one brand, which is a detail most clients don’t care about until their legal team asks — so we’ve put the specifics on the legal page rather than burying them.

Every engagement is staffed with senior engineers, and a project manager where coordination is the hard part rather than the building. The people you meet before you sign are the people who do the work.

The team

The four of us met at Kathmandu Engineering College and never really stopped working together. Saurav started the company on his own. Yunik came next — the one the rest of us call when a system has to hold — and Rujen and Sahil followed.

Nobody here is a generalist. Data, backend, mobile, frontend: each of us is the person the other three go to when it’s our part of the system. That’s the whole firm, and it’s deliberate. The people who scope your work are the people who build it, and they don’t change after you sign.

CEO · Data and BI

ingestion, platforms, reporting

Saurav Raj Joshi

Founder & CEO · Principal Data & BI Engineer

Saurav started the company and runs it. He also leads the data work — ingestion, pipelines, the warehouse and the reporting layer on top of it — and holds both of Microsoft’s Fabric certifications, Data Engineer and Analytics Engineer.
He is also the one who will tell you a migration is not worth it, which is the most expensive sentence a consultant can say out loud and the reason clients keep calling back.
- LinkedIn
- Microsoft Fabric
- Azure Data Factory
- Synapse
- Snowflake
- AWS
- PySpark
- Power BI
- PostgreSQL
- Python
Mobile and delivery

iOS, Android, and the schedule

Rujen Shakya

Head of Project Management · Senior Mobile Engineer

Rujen runs delivery and keeps the team on schedule. He is also the senior mobile engineer, so the person managing your timeline has built the thing he is estimating — which is why his estimates survive contact with the work.
Flutter and Kotlin, and the unglamorous parts around them: release pipelines, store review, crash reporting, and the security and compliance work that decides whether an enterprise deal closes.
- LinkedIn
- Flutter
- Kotlin
- Jetpack Compose
- Agile/Scrum
- ISO 27001
- SOC 2
- Fastlane
- Firebase
- MCP
CTO · Backend and systems

distributed systems, APIs, infrastructure

Yunik Maharjan

CTO · Principal Backend & Systems Engineer

Yunik owns the technical direction, and he is the one the rest of us call when a system has to hold. Distributed systems, APIs and the infrastructure underneath them, in Go and Rust — and the kind of engineer who writes open-source infrastructure tools for fun. His is UNIQX, an Ngrok alternative.
Microservices, event pipelines, wallet authentication across chains, agentic workflows that open their own pull requests. If it runs on a server and has to stay up at four in the morning, it is his.
- LinkedIn
- Go
- Rust
- TypeScript
- Python
- FastAPI
- PostgreSQL
- MongoDB
- Redis
- Kafka
- AWS
- MCP
- RAG
- Docker
- Airflow
Design and frontend

dense interfaces that stay fast

Sahil Shrestha

Design Lead · Senior Frontend Engineer

Sahil leads the design and the frontend work, and he is good at the part most frontend engineers find tedious: making a screen with four thousand rows on it feel fast. Admin portals, banking interfaces, anything where the data is dense and the user is in a hurry.
React and Next.js, and the accessibility and performance work that decides whether people actually use what you built rather than tolerating it.
- LinkedIn
- React
- Next.js
- TypeScript
- Redux
- React Query
- Tailwind
- Ant Design
- Chart.js
- Jest
- Storybook

The rest of the team

Behind the four of us there’s a wider bench — senior backend engineers in Python, Go and TypeScript; senior data engineers across Fabric, Databricks, Azure, AWS and Snowflake; senior data analysts; Fabric-certified data engineering associates; mobile engineers; and associates growing into it on real work.

That means we can staff an engagement the way it actually needs staffing. A senior lead with junior support when that’s the sensible shape, a full senior team when the work is hard or the deadline is real.