Hi, I’m Mujeeb.

A product engineer who likes to see the whole thing through.

I work across web, mobile, and the systems behind them. Most at home in small teams, working with people who care about what they’re putting into the world.

Mujeeb Muhideen
Mujeeb MuhideenEngineer, builder, occasional speaker.

My range grew with the work.

I didn’t set out to work across every layer. I kept finding that making one part of a product better meant understanding another.

2021–2023

Timart & FoodNow

Start with the conditions people actually work in.

At Timart, I worked on an offline-first commerce app as a contract Flutter engineer. The product served over 200 businesses at the time. Local storage, unreliable networks, and getting data back in sync were everyday product concerns.

At FoodNow, I built ordering and real-time order status experiences. Both taught me the same thing: the interface needs to make sense even when the system isn’t having a perfect day.

2022–2024

SwervLead Software Engineer

Take responsibility for the connections.

I was one of two engineers responsible for Swerv’s embedded-finance platform. My work connected public APIs, backend services, partner tools, cloud infrastructure, and the consumer mobile app.

The APIs served nearly 20 partner businesses, and the app reached approximately 100,000 combined iOS and Android downloads. A payment screen, a webhook, and a reconciliation job were different parts of the same responsibility.

More about my work at Swerv

2024–2026

Tempo LabsSoftware Engineer

Stay close to the people making the decisions.

Most recently, at Tempo Labs (YC S23), I built web and mobile products for 5+ startup clients. I worked directly with founders, designers, and product teams, taking features from technical design through deployment and support.

That meant thinking through the whole experience: streamed AI responses, authentication, uploads, and what people see while the backend is still doing its work.

More about my work at Tempo

What working with me looks like.

I ask for the context.

Who is this for? What are they trying to do? What’s getting in their way? I do my best work when I can help shape the answer, then take responsibility for building it.

I take time seriously.

Time matters to me. I know it’s one of a founder’s most valuable resources, too. I aim to protect it by keeping priorities clear, raising blockers early, and getting useful work into people’s hands without creating avoidable rework.

I pay attention to the in-between states.

The upload that hasn’t finished. The connection that dropped. The payment that needs a retry. Those moments are part of the experience, and I want the interface and the system to agree.

I stay with it after release.

Deployment is one step. I care about how the product behaves in use, what support teaches us, and whether the next engineer can understand and change what I’ve built.

Still making things. Still sharing what I learn.

I also build products of my own. Link Pocket, my app for saving links and returning to them with a next step, is available on iPhone, iPad, and Mac. My open-source work explores the systems behind products, from job queues to moving databases.

Building something independently makes every decision personal: what to leave out, what needs another pass, and whether it’s ready for someone else to use.

I write about the decisions behind that work. I also share what I learn through talks on Flutter, Go, and Kubernetes, including appearances at DevFest and Google I/O Extended.

The kind of team I’m looking for.

A small team, a problem worth understanding, and room to take responsibility. I like working close to founders, designers, and other engineers, with enough context to make good decisions together.

I’m looking for my next product engineering role and I’m open to relocation. If that sounds like your team, I’d love to hear what you’re working on.

Find the résumé that fits your role

Thanks for getting to know me.

Mujeeb

Say hello Back to contact