QualGent answers the question every mobile team asks before they ship: "What's wrong with my app that I don't know about yet?"

We're an ex-Google, YC-backed team of 10 building the verification layer for mobile apps. As coding agents write more of the app, someone still has to catch what they miss before users do. We combine AI with expert testers, automate more of the loop every month, and use our own product every day.

The most trusted voice in a room of mobile engineers is another mobile engineer. So we're hiring one to lead how QualGent reaches mobile teams.

Most engineers never see how software gets bought: who decides, why, and what earns a team's trust with their release. This is a new role for a mobile engineer who wants to go beyond engineering. You'll bring in customers, set pricing with our CEO, and take what you hear straight into the product.

It's the closest thing to being a founder without starting a company. If you do want to start one someday, this is the half of the job most technical founders learn the hard way.

"I'm looking for someone who wants to build the go-to-market motion with me, not execute one I've already figured out." — Shivam, Co-Founder & CEO

• Bring mobile teams to the table. Start with your own network, then build the channels that reach past it: communities, conferences, content, and direct outreach to engineers like you.
• Qualify, then hand off to close. Run first conversations, find the real release pain, and bring qualified teams to our CEO to close. As you prove it out, you'll take more of the deal yourself.
• Get new customers to a first win. Join trial kickoffs for the teams you bring in, so the engineers who trusted you get value fast.
• Shape pricing, packaging, and product. Work with our CEO on how we package and price QualGent. Bring evidence from the market into product decisions, and help decide what we automate next.
• Own how we show up to mobile engineers. Website, positioning, talks, posts, and case studies, written by someone who has shipped a mobile app.

Your north star is qualified meetings with mobile teams that turn into signed contracts.

A qualified meeting is with someone who can influence the buying decision, on a team that ships on a regular cadence and has a named QA pain. Talks, posts, and community work count because they fill that pipeline, not on their own.

• You've shipped mobile apps. You know iOS or Android release pipelines firsthand: CI/CD, TestFlight or Firebase App Distribution, device fragmentation, and at least one testing framework (XCUITest, Espresso, Maestro, Detox, or Appium).
• You know people who build mobile apps. Former teammates, managers, meetup friends, people you've met at conferences. You can name the mobile leads who'd take your call.
• You've started conversations with strangers before. A side project with real users, a talk, a meetup you ran, an open source project you supported, or client-facing agency work.
• You ask before you pitch. You find what's actually breaking a team's releases before you mention a product.
• You're comfortable talking about money. Pricing, pushback, and asking for the decision.
• You want founder-level ownership. No playbook is waiting. You're helping build it.

Bonus: experience in developer relations, solutions engineering, or a forward-deployed role; mobile agency or consulting work; conference talks; a company you started.

This is a customer-facing role with a pipeline number, not a coding role. Some messages will go unanswered and some teams will say no. For your first months, bringing in qualified meetings comes before building tools.

In return, you'll see exactly how QualGent works under the hood, and your customer evidence will change what we build.

Compensation: 90K - 130K base, plus variable pay tied to signed contracts (on-target earnings: $170K - $200K), plus equity sized for a founding hire. You'll report directly to our CEO.

Location: NYC or SF, the two hubs for the mobile teams we sell to. SF-based candidates also cover Las Vegas and LA.

To apply: apply through LinkedIn. Include a short note answering one question: how many mobile leads could you get a 30-minute conversation with next month, and how do you know them?