I'm not a task-taker. Give me a problem — I'll come back with a shipped solution.

At Levo.ai I joined as a founding engineer before the product was defined. I talked to enterprise customers, found the gaps, and built the infrastructure they now depend on daily: kernel-level traffic sensors, API security engines, agentless discovery tooling, and a CLI built from zero. At IndiaMART, I ran ML search infrastructure at millions-of-queries-per-day scale.

I've also tried to build 2 companies. Both failed. Both taught me more than any job ever has.

Here's what 4+ years of owning problems end-to-end looks like:

Most engineers write code. Fewer try to build products. I've done both — and failed — which is worth more than you'd think.

Build Verge Inc — AI-Powered AEC Platform (with Stanford engineers)

Built an NLP + BIM platform to automate construction workflows using LLMs — generating rooms, walls, doors, voids programmatically from language prompts. Ran into product-market fit and funding walls. The research lives on.

Washbe — On-Demand Campus Laundry

Launched a React Native-based laundry platform with real-time scheduling. COVID hit. The market changed faster than we could pivot.

Both failed. I learned what you can't learn from any job: how to define a problem without a PM, talk to customers without a script, make architectural bets with no safety net, and keep shipping even when it's not working.

That's the founder mindset. That's what I bring to an engineering team.

Most production work lives in private Levo.ai repos. Public activity is open tooling, side projects, and experiments.

  

type Focus struct {
    Topic string
    Why   string
}

currentWork := []Focus{
    {"eBPF + XDP",              "Wire-level packet processing — no kernel modules, no overhead assumptions"},
    {"Agentic Debug Tooling",   "AI-assisted root cause analysis for live production incidents"},
    {"API Behavioral Drift",    "Detecting when APIs deviate from their established production baseline"},
    {"OpenTelemetry Internals", "What tracing frameworks actually do — and what they still miss"},
}

I'm looking for a team that's building something hard — where the problems aren't solved yet, the architecture isn't locked in, and engineers are expected to think, not just execute.

If that's you, let's talk.