5
12 Comments

Looking for a Founding Engineer

Hello there!

I’m a solo founder working on a peer-support web platform focused on real-life problems (personal growth, stress, career, everyday challenges). The idea and business plan are ready.

I’m looking for one engineer who will be 100% responsible for the app itself and the codebase.

What I offer:

-20% equity in the idea/app (equity-only, no salary)

-Full technical ownership of the product

-Clear responsibilities: you build and own the app, I handle product vision, marketing, business, cloud architecture, security and organization

What I’m looking for:

-Strong ASP.NET / .NET backend experience or the will to learn it

-React + TypeScript (or willingness to own the frontend)

-Ability to turn my vision and concepts into a working product

-Long-term mindset (not a freelancer / short-term gig)

There is no cash compensation — this is an equity-based role.
If this resonates or you have questions, feel free to DM me directly.

posted to Icon for group Looking to Partner Up
Looking to Partner Up
on January 20, 2026
  1. 1

    I would be glad to explore the opportunity to work with you. We can connect via email at [email protected]
    Additionally, could you please share your LinkedIn profile?
    I look forward to discussing this further.

  2. 1

    Validate problem-solution fit before heavy build
    Research: Lean Startup experiments (Ries, 2011) + startup hypothesis testing evidence (Camuffo et al., 2020).
    Action: Define 5 core hypotheses (need frequency, willingness to engage weekly, trust in peer support, retention intent, referral intent) and run concierge tests with pass/fail thresholds.
    Use evidence-based cofounder selection
    Research: Structured selection predicts performance better than intuition (Schmidt & Hunter, 1998).
    Action: Keep equity offer, but add a scored 2-week trial rubric: delivery speed, code quality, communication, ownership, learning velocity, value alignment.
    Design for psychological safety and trust
    Research: Online trust/reputation systems improve participation (Resnick et al., 2000); social support quality affects outcomes.
    Action: Test trust features early: moderated onboarding, clear community rules, lightweight reputation signals, response quality scoring.
    Run controlled product experiments
    Research: Controlled web experiments are the best causal method (Kohavi et al., 2009).
    Action: Weekly A/B tests on activation and retention drivers (first post prompt, matching flow, reminder cadence), with one primary KPI per test.
    Strengthen the engineer pitch with uncertainty reduction
    Research: High uncertainty lowers venture commitment; clearer role/roadmap improves commitment signals.
    Action: Add a 90-day technical roadmap, architecture boundaries, and explicit decision rights so candidates can evaluate risk objectively.

  3. 1

    the 20% equity-only offer from Filip caught my eye since I've been in similar equity-only situations

    spent 8 months building a SaaS with 0 paying customers, mostly because i didnt validate demand before committing full time, so i get how tricky it is to find a tech partner willing to bet on equity alone

    • try to be super clear about the vision and potential upside to attract someone passionate rather than just looking for a paycheck
    • consider small initial milestones or vesting schedules to build trust and show progress
    • dont rush into commitments without a clear agreement on responsibilities and long-term goals

    how are you planning to keep the engineer motivated without salary during the crucial early phase?

    1. 1

      I'm really interested in the answers for the questions. Can you share it with me when you get answers?

      1. 1

        great question — honestly this is THE make-or-break challenge for equity-only
        partnerships. here's what i've learned (some from getting it wrong):

        1. make progress visible and fast
        • ship something in the first 2-4 weeks, even if it's ugly. nothing kills
          motivation faster than months of "building" with nothing to show
        • weekly demos, even internal ones, create a rhythm of wins
        1. validate demand before writing serious code
        • this is where i messed up personally. building for 8 months without paying
          customers meant my engineer partner lost faith
        • run landing page tests, collect waitlist signups, do customer interviews FIRST.
          when the engineer sees real people wanting the thing, equity suddenly feels more
          real
        1. structure equity to protect both sides
        • 4-year vesting with 1-year cliff is standard for a reason
        • tie milestones to vesting acceleration (e.g., hit 100 users = accelerate 6
          months of vesting)
        • put it in writing from day one. no handshake deals
        1. reduce the engineer's risk
        • let them keep a part-time job or freelance gigs at the start
        • define "minimum viable commitment" — maybe 15-20 hrs/week until there's
          traction, then ramp up
        • forcing full-time with no income just breeds resentment
        1. share the unglamorous work
        • if the engineer sees you doing sales calls, writing content, handling support —
          they stay motivated. if they feel like they're the only one grinding, they'll
          leave
        • weekly sync where you both show what you did that week keeps accountability
          equal
        1. set a "go/no-go" checkpoint
        • agree upfront: "in 3 months, if we don't have X (waitlist of 500, 10 paying
          users, whatever), we reassess honestly"
        • this actually increases commitment because it removes the fear of being stuck
          forever

        the honest truth: the best way to keep an equity-only engineer motivated is to
        prove the idea has legs as fast as possible. everything else is a band-aid.

        1. 1

          Thank you so much sharing the answers.
          How can I follow you in indiehackers.com? No following?

          1. 1

            "Hey! Unfortunately, IH doesn't have a follow feature, but feel free to connect with me on LinkedIn for discussions. If you're interested in what I'm building, you can join the waitlist at dontbuildyet.com 🚀"

  4. 1

    Hi!

    Quick question first — are you still looking for someone for this, or have you already found a technical partner?

    I came across your post and find the idea interesting. For me, this would be something I’d do alongside my regular work. Equity-based collaboration is new to me, and financial aspects are not my primary motivation right now.

    I’m currently looking for a project where I can actually build and develop. I’m professionally rooted in software development, have several years of hands-on experience building applications, and I’m familiar with DevOps environments as well. For the past few years I’ve been working as an Agile Coach, but I come clearly from a technical background. Development is the main focus for me here — coaching is more of an additional background and a personal interest.

    If you’re open to an initial, low-pressure conversation to see whether this could be a fit, I’d be happy to connect.

  5. 1

    AI and robotics are reshaping industries by improving efficiency and reducing costs, while simultaneously forcing companies to rethink roles, skills, and workforce structures. Need to adjust with AI-Vive era.
    However, we are open to partnerships for building AI Agents, AI Receptionist, AI Automation systems, and Custom SaaS solutions powered by Python, Django, FastAPI, and Node.js.
    ✔ Up to 50% profit sharing
    ✔ 25–75% cost advantage compared to others
    ✔ Secure, scalable, and production-ready architecture
    ✔ Long-term collaboration potential
    If you or anyone you know is interested in partnering on innovative AI and SaaS projects, feel free to message me to discuss the details.

  6. 1

    Hi
    I’m a Full-Stack Engineer with strong backend experience in Java and Python, and frontend ownership with React + TypeScript. I’ve owned production systems end-to-end (architecture, codebase, cloud).
    I’m looking for a long-term, equity-based role with full technical ownership. While not .NET-first, I learn fast and can fully own the stack. Your vision resonates with me — happy to chat.
    linkedin/in/elmanhou/

  7. 1

    Hey, this resonates with me. I’m a software engineer interested in owning a product end to end and working long term on something meaningful.

    I’m willing and motivated to learn the backend stack you’re using and take full ownership of it. I’m also comfortable owning the frontend side.

    The clear split of responsibilities and long-term, equity-based mindset is exactly what I’m looking for. I’d love to hear more about your idea and vision and see if there’s a strong fit.

    1. 1

      sound great!

      Let's connect and talk about it! :)

      You can add me directly on LinkedIn:
      https://www.linkedin.com/in/filip-rogoza/

Trending on Indie Hackers
I'm a lawyer who launched an AI contract tool on Product Hunt today — here's what building it as a non-technical founder actually felt like User Avatar 142 comments “This contract looked normal - but could cost millions” User Avatar 54 comments A simple way to keep AI automations from making bad decisions User Avatar 53 comments Never hire an SEO Agency for your Saas Startup User Avatar 42 comments 👉 The most expensive contract mistakes don’t feel risky User Avatar 41 comments The indie maker's dilemma: 2 months in, 700 downloads, and I'm stuck User Avatar 40 comments