Skip to main content
Life at Darse

Small team. Real ownership. Work that matters.

We're eight engineers who chose to stay small — so every person shapes the culture, every contribution is visible, and every project is one we're proud of.

Most agencies scale by hiring fast and staffing bodies. We took the other path. Darse stays small because the work is better when everyone on the team is someone you’d choose to build with — not just someone who was available.

That means you won’t get lost here. You’ll work directly with the founder, ship to production in your first week, and have real influence over how we build. The tradeoff is that we expect ownership — not just output, but judgment.

How we work.

Remote-first, async by default

We work from wherever we do our best work. Nepal hours are the anchor, but async habits keep everyone unblocked. No one is penalized for being offline — we care about what ships, not when your Slack dot turns green.

Learning through real work

You'll work across industries — IoT, fintech, SaaS, computer vision — often within the same year. Every engagement is a masterclass you can't get from a course. Senior engineers review your code and explain why, not just what.

Ownership from day one

There's no bench. No months of onboarding before you touch production. You ship to real users in your first week, with the support to do it confidently. Small team means your work is visible and your voice matters.

A typical day.

1

Morning

Async standup

Post what you're working on in the project channel. Read what others shipped overnight. No meetings unless something is blocked.

2

Mid-day

Deep work

Three to four hours of uninterrupted building. This is protected time — no one schedules calls here. Most of our best work happens in this block.

3

Afternoon

Collaboration

Code reviews, pair programming on hard problems, or a quick call with the client when a conversation is faster than a thread.

4

End of day

Ship & handoff

Push your work, update the PR, leave context for anyone picking it up next. Clean handoffs mean no one starts tomorrow confused.

Snapshots.

Team farewell dinner on a Kathmandu rooftop
Desk setup with code on screen
UNO cards on a retreat evening
Table tennis break between sprints
Team swimming outing
Sensor calibration on hardware project
Sprint board during an active iteration
Movie night out with the team
Team lunch at a local cafe

What you get.

Fully remote

Work from anywhere in Nepal — or anywhere with reliable internet.

Real projects, not busywork

You work on client products that serve real users, not internal tools no one asked for.

Flexible hours

Core overlap with Nepal business hours, but how you structure the rest is up to you.

Long-term engagements

Most client partnerships run for years. You'll learn products deeply instead of context-switching every sprint.

Direct mentorship

Small team means working alongside the founder and senior engineers daily — not through layers of management.

Diverse tech exposure

IoT hardware, optical networking, SaaS platforms, AI/CV — one role, many domains.

“The best engineers we’ve worked with are the ones who stayed long enough to understand the product — not just the codebase.”

Suvrat, Founder

Ready to build with us?

Check our open roles — or send a general application if nothing listed fits but you like how we think.

We reply within one business day.