Founding Engineer - Equity-Only Compensation (Up to 10% Equity + 20% of Profit)
Offre en anglaisThe Founding Engineer will build the entire product surface, including the app shell, authentication, scan flows, and public scorecards. They will be responsible for the full deployment pipeline and actively participate in product strategy and pricing decisions.
- Télétravail
- New York, New York, United States, Pune, Maharashtra, India, San Francisco, California, United States, Texas, United States, Toronto, Ontario, Canada
- Publié 22 juill. 2026
- 1 poste
Résumé du poste
⚠️ EQUITY-ONLY COMPENSATION There is no salary. Not a reduced salary - none. You are paid in ownership: up to 10% equity and up to 20% of monthly profit, paid out every month. If that doesn't work for your situation, please stop reading here. No hard feelings and no wasted time on either side. There is a working product. There is no interface. That's the job. Point Seen in Search at a domain and, in about forty seconds, it asks ChatGPT, Perplexity, and Google AI Overviews what they actually say about that company, parses the verbatim answers, and scores the result deterministically. A real scan of stripe.com came back 80/100 - "Category Leader" - in 42 seconds across all three engines. Nobody can see any of it. The pipeline is a library and a queue worker. There is no first page, no scorecard, no export, no deploy pipeline. You would build all of it. About Seen in Search Every company spent twenty years learning to rank on Google. Now their buyers ask an AI instead, and most of them have no idea what it says back. Seen in Search answers that — and then fixes it. Not a checker. Not an advisor. An executor. Scan → Execute → Verify. On-page and technical work gets executed for the customer; off-site citation work is assisted. One rule shapes the whole product: we publish observations, not verdicts. Every claim carries its engine, its exact question, and its UTC date. "We asked ChatGPT X on 2026-07-16; here is its verbatim answer." Defensible forever. It's also a real design constraint - you'll feel it on every screen you build. Billed under FactoryJet Private Limited (India). Where things honestly stand Solo founder. No outside capital. No investors to answer to, and no runway from anyone else either. Pre-revenue. Zero customers today, which means zero profit share today. The engine works and is tested. Normalized Postgres schema, pg-boss queue and worker, a daily spend cap, 78 offline tests, verified against live engines. The marketing site is live. Next.js on Cloudflare Workers, auto-deploying. Everything between those two things is unbuilt. That's roughly six months of work, and it's yours. The deal - read this part twice No salary. Two forms of ownership instead. Equity - up to 10%. Four-year vest, one-year cliff. Real shares, papered properly, not a handshake. Profit share - up to 20%, paid every month. Not deferred to an exit. Not held until some funding round. The month we make money, you get paid that month. How profit is calculated - the whole formula Profit = what customers paid us this month − what it cost to serve them this month. The costs that come out are only the direct ones: AI engine and API costs (DataForSEO, Claude), servers and hosting, payment-gateway fees, software subscriptions, and any refunds. That's the list. No management fees, no allocated overhead, no invented line items. An example month (illustrative numbers, not a forecast): Collected from customers $10,000 − Expenses = $2000 = Profit $8,000 Your 20% share $1,600, paid that month You see the numbers. Every month, you get the same sheet I do - the revenue, the costs, the math. Nothing about your pay should ever be something you have to take on faith. Be clear-eyed about this: in a pre-revenue company, 20% of nothing is nothing. The profit share is genuinely uncapped and genuinely immediate, and it is also genuinely zero until we land customers. You need enough personal runway to survive the months before that happens. Please don't skip past this line. What you'll own The entire product surface. App shell, magic-link auth, the scan flow, live progress - the first screen a customer ever sees is one you design. Public scorecards at /score/, the methodology page, and OG images built to be screenshotted into a Slack channel and win the argument. Exports — Markdown, JSON, PDF — each one a publication that has to carry its own provenance. Ship and run it. Docker, Caddy, GitHub Actions, a Hetzner box. You deploy, you own the pager. Product calls. What gets built next, what gets cut, what the pricing is. You'll be in that conversation, not downstream of it. Your profit share means you have every reason to argue about pricing — good. Stack TypeScript · Next.js 16 · React 19 · Tailwind 4 · Prisma 7 + Postgres · pg-boss · Cloudflare Workers (OpenNext) · Docker + Caddy on Hetzner · DataForSEO · Claude. Strong opinions welcome. Nothing here is sacred except Postgres. What we're looking for Required You build with AI agents, seriously. Claude Code, Codex, Cursor, Kimi — whatever you've made work. Not "I've tried Copilot." We're two people doing the work of eight, and this is how. Fundamentals underneath the agents. You can read what your agent just wrote and know it's wrong — the N+1, the missing index, the race in the worker, the test that passes for the wrong reason. Agents amplify judgment; they don't replace it. You design. This is a product that sells trust, and trust is transmitted almost entirely through the interface. Send a portfolio or live URLs. This is the hardest filter and the one I'll weigh most. You've shipped to production and kept it up. Containers, a reverse proxy, CI/CD, a Linux box you're not afraid of. Product instinct. You've killed a feature you liked because the evidence said to. Personal runway to cover the months before revenue starts, and clear eyes about the risk. Preferred SEO, search, or martech background - you'll get the customer faster Worked on something where correctness was a selling point Shipped a product solo, start to finish, however small Not a fit if You want a spec handed to you. You need a team around you. You'd describe design as "not really my thing." Or you're looking for a side project - this is not a nights-and-weekends role. How to apply Message me on Wellfound with: Something you designed and built - URL preferred over a résumé. How you actually use AI agents. What's in your setup, and one specific thing you've caught them getting wrong. One sentence on what you'd change about seeninsearch.com after looking at it. I read every message and reply to all of them. First conversation is 30 minutes, no prep.
Ce que vous ferez
The Founding Engineer will build the entire product surface, including the app shell, authentication, scan flows, and public scorecards. They will be responsible for the full deployment pipeline and actively participate in product strategy and pricing decisions.
Exigences
Candidates must have a strong track record of shipping production-ready products and a high level of proficiency in using AI agents for development. A strong portfolio in design and the personal financial runway to work without a salary are mandatory.
Avantages
• Equity (Up to 10%) • Profit Sharing (Up to 20%)
Compétences indiquées
- PostgreSQLSouhaitée
- ReactSouhaitée
- TypeScriptSouhaitée
Autres compétences pertinentes
Relevées dans la description du poste. Confirmez les exigences importantes ci-dessus.
- TypeScript
- Next.js
- React
- Tailwind CSS
- Prisma
- Postgres
- Docker
- Caddy
- Cloudflare Workers
- AI Agent Development
- UI/UX Design
- CI/CD
- Linux Administration
- Product Design
- API Integration
Domaines d’emploi
- Software
- Technology
- Engineering
- Marketing
- Data & Analytics
Renseignements supplémentaires
- Expérience minimale
- 5+ ans
- Langue de l’offre
- anglais
- Heures de travail
- 40 heures par semaine
- Exigences de lieu
- Country, India
- Mode de candidature
- La candidature directe est offerte