Why I built this
Remesh built a platform so 1,000 people can speak — and actually be heard — at the same time.
“Adding my resume to a pile — when your whole product is about cutting through noise to find what resonates — felt like I missed the point entirely.”
So I spent time actually understanding what Remesh has built. The utility matrix, Remy, where the product is going. Then I rebuilt a working version of your core mechanic. And I put an AI version of me on this page so you can run your own first-round — without either of us needing to schedule a call.
This is what I think a job application should look like, if you genuinely want the role and you actually did the research.
What I know about you
I didn't just read your careers page.
Here's what I actually understand about what Remesh has built — and why it matters.
The Utility Matrix
Your actual IP — not an AI wrapper
In a session with 1,000 participants, no one votes on everything. The algorithm infers full consensus from partial responses using utility matrix completion — similar to collaborative filtering, but for opinion space. Most competitors are LLM layers over survey infra. Remesh built something novel at the mathematical layer. That's rare.
Remy & The Citation Problem
Launched Oct 2025 — the architecture is right
Remy's RAG framework grounding every insight in actual participant quotes solves the enterprise trust problem. In research, a hallucinated insight doesn't just look bad — it drives real decisions. Phase 1 is analysis. Remesh has stated plans to expand to discussion guides, AI moderation, live facilitation. This is a platform play.
The Kantar Signal
IP litigation against a $3B firm means something
Remesh filed against Kantar in September 2025. $76M raised. General Catalyst-backed. Founded 2013. Companies don't pick fights with giants unless they're confident in their moat. This tells me exactly where Remesh sees itself — and the kind of engineering that needs to support that position.
One thing I'd build: Remy for Longitudinal Tracking
Brands don't ask questions once — they ask them quarterly. What if Remy could automatically compare consensus shifts across sessions over time? Run the same study in Q1 and Q3 — Remy surfaces what changed, what held, and what the drift signals. A brand sentiment timeline, not just a snapshot. It's a natural extension of Remy's existing RAG architecture. On the product side, it transforms a transactional tool into a strategic intelligence platform — the move that wins enterprise renewals.
I didn't just read about the utility matrix. I rebuilt it.
Live demo
I rebuilt the core of your product.
Try it.
Paste responses one per line. Hit analyze. Watch consensus emerge — themes, percent agreement, participant quotes. Output styled like Remesh.
Now that you've seen what I built — want to ask me about it directly?
This is where
we actually meet.
No calendar. No PDF. Just a live voice conversation with Jasim — right now.
Talk with Jasim
Live voice · Real-time answers
Voice via ElevenLabs · Intelligence via Claude · Built in one day
Why I genuinely want this
Not just the job.
The team.
I can find engineering roles. What I can't find everywhere is a team that's building something that actually required original thinking to exist.
The problems are genuinely interesting.
Remesh isn't building a wrapper. The utility matrix is novel mathematics. Remy is a RAG architecture solving a real trust problem in a real-stakes industry. These aren't features — they're research problems that happen to have a product around them. That's the kind of work I want to be inside of, not just observing from the outside.
I've built mostly alone. I want to build with people who push back.
At Khadoom.ai, every technical decision was mine. That taught me a lot — but it also meant I never had a senior engineer look at my system design and say "have you thought about X?" I'm at the point in my career where the next leap isn't building more alone. It's building with a team that has strong opinions, high standards, and the experience to show me what I'm missing.
I'm a different kind of builder. I think that matters here.
Self-taught. Product-minded. I've shipped across logistics, telecoms, finance, fleet management — sometimes all in the same sprint. That breadth wasn't random. It trained me to see the same underlying patterns across different problems. I don't just build what's asked. I ask what's actually broken first. At a company that's built something mathematically novel in a $70B industry that was overdue for disruption — that instinct feels like it would fit.
“I read the Kantar lawsuit announcement and thought: that's a company that believes in what it's built. That's the kind of team I want to be part of building something with.”
— Jasim Ameen
One more thing
Researching Remesh wasn't manual.
It was a pipeline.
→ 500+ sources
→ Core product history
→ Strategic signals surfaced
→ Worth building toward
I don't apply to companies I haven't properly understood. It wastes everyone's time — most of all mine. Working on a product you don't believe in is just slow damage.
Most people skim the website, read a few LinkedIn posts, and call it research. I built an agent that pulled from 500+ sources, structured the findings, and handed off to a second system that extracted the signal — product history, competitive positioning, where the team is actually heading. Then I made a human judgment call on whether this was worth building toward.
It was.
This is also how I'd work on the inside. Not manually. Not slowly. Understanding users, markets, and problems using the best available tools — then applying judgment to what it means. The research process above isn't something I did for the application. It's just how I think.