S/P

SAMIR POKHREL

Software Engineer

Backend systems, real-time infrastructure, and agentic platforms.

I build the parts of software systems that are usually invisible when they work well: gateways, queues, transport layers, real-time pipelines, and the glue between products and infrastructure.

Right now I'm leading core engineering for Lasius at Adex International, where I work on agentic workflows, MCP server ecosystems, connector frameworks, and unified auth across tools and transports.

Before that, I spent several years on Eventsmo building large-event media systems, including WebRTC ingest, FFmpeg processing, RTMP pipelines, and HLS delivery. I write here to think clearly about these systems and the tradeoffs behind them.

What keeps me interested is the point where product decisions meet systems design: how tools are exposed, how failures are handled, how observability is built in, and how complexity can stay manageable as a platform grows.

My Career So Far

Roles that shaped how I build backend systems, real-time infrastructure, and production software.

  1. 2025 — NOW
    Software Engineer · Adex InternationalLeading core engineering on Lasius, with work across agentic workflows, MCP infrastructure, connector systems, unified auth, and transport layers.
  2. 2022 — 2025
    Full-Stack Developer · Yellow NepalBuilt real-time video and event systems for Eventsmo, including WebRTC ingest, FFmpeg processing, RTMP pipelines, HLS delivery, payments, and platform tooling.
  3. 2022 — 2023
    Software Developer · Mehta Heino Industry OyWorked remotely on 3D printing software and a custom Stripe-powered commerce platform.
  4. 2022
    Software Developer · Sriyog ConsultingRebuilt a Flutter app from scratch and shipped the supporting backend and web dashboard.

How I Work

I like systems that are explicit, observable, and easy to reason about under pressure. That usually means clear contracts, boring-but-reliable infrastructure where possible, and careful attention to failure modes before scale forces the issue.

I tend to work from the boundaries inward: transport, auth, data flow, and operational constraints first, then the product surface that sits on top of them.

  • Design around failure before traffic exposes it.
  • Prefer clear interfaces over clever abstractions.
  • Build for observability, not just correctness.

Beyond Work

Outside of engineering, I spend a lot of time reading, writing, and trying to sharpen how I think. I care about good questions, clear communication, and the kind of long-term craft that only shows up after repetition.

Kathmandu evenings, headphones on, and notes half-finished in a draft folder is usually where the next idea starts.

  • Reading systems, product, and software design books.
  • Writing long-form notes to sharpen technical thinking.
  • Paying attention to craft, taste, and clear communication.

Call To Action

Let's build something ambitious.

If you're building something ambitious and need a strong systems engineer, let's talk.

LET'S WORK