Jobs · Business Development · Washington

Technical Co-founder (CTO)

FutureSight · Seattle, WA · 1 mo ago
Business Development$100/hrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: The Opportunity, About FutureSight, The Partnership, What you'll own, Co-Founder Profile. Also maybe Benefits, Pay, Schedule, Pay not present. So we include only sections with real content. We must use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate like How to Apply? Actually "How to Apply" is application instructions, which we must remove. Also diversity statement etc. Remove. We must preserve all substantive information. So we need to include content from sections: The Opportunity, About FutureSight, The Partnership, What you'll own, Co-Founder Profile. We need to format them with headings: maybe "About the role" corresponds to The Opportunity? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The posting does not have explicit "Responsibilities" list but we have "What you'll own" which enumerates responsibilities. Could map that to Responsibilities. Also "Co-Founder Profile" could be Requirements/Qualifications/Skills. We need to decide. We should follow instruction: use those headings when appropriate. For example, we could have:

    About the role

    with content from The Opportunity and About FutureSight? Actually About the role could be a summary of the role. The Opportunity section describes the role. So we can put that under About the role. Then

    Responsibilities

    with content from What you'll own (list). Use
    • . Then

      Requirements

      or

      Qualifications

      or

      Skills

      for Co-Founder Profile. Could combine into Requirements. But we need to avoid thin sections. Perhaps combine into one

      Requirements

      with list. Also we have

      The Partnership

      maybe not in list but we could treat as About the company? Actually there is no heading for partnership in prescribed list, but we could still include a heading if content exists? Instruction: use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But they also say "include a section ONLY when the posting has real, specific content for it". So we can use those headings if content matches. If not, we shouldn't create other headings. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements (or Qualifications/Skills). Possibly Benefits, Pay, Schedule not present, so omit. We also have info about FutureSight team and partnership details. That could be part of About the role? Or maybe we could put under About the role as description of the venture builder. The Partnership section could be considered part of About the role (details about partnership). So we can incorporate that into About the role prose. Thus:

      About the role

      ... combine The Opportunity, About FutureSight, The Partnership ...

      Responsibilities

      • ... items from What you'll own ...

      Requirements

      • ... items from Co-Founder Profile ...
      We must not include How to Apply, diversity statement. Now we need to preserve all substantive information. Let's extract. The Opportunity paragraph: "The Opportunity FutureSight is seeking an applied AI builder to co-found and lead the technical direction of a new B2B AI venture from the ground up. This is a co-founder partnership with founder-level equity and founder-level authority, not a salaried executive role. We are not looking for someone who manages engineers from a distance or adds AI language to a traditional CTO resume. We are looking for someone who can take a vague problem, frame it clearly, design the right system, and turn it into something customers actually use and trust. If you've gone from ambiguity to working product before — and you want to do it again with the backing of an experienced venture building team — this is the opportunity. This is a full-time, exclusive commitment to building and owning a single B2B AI venture from the ground up." About FutureSight: "FutureSight is a leading venture builder that co-creates world-class software companies with values-driven entrepreneurs from inception to exit. We are a team of founders, operators and designers with experience successfully bringing software to market at scale. You'll Co-create With a Proven Venture Building Team, Including John Carbrey – 4x founder, bootstrapped to $100M ARRJoshua Auslander – Seasoned CFO and strategic advisor with $200M aggregate exitsAlan Smith – Globally recognized early stage validation expert, 24 products launched, an exit, 5M+ books soldPrathna Ramesh – Early-stage investor and capital strategy advisor" The Partnership: "Founder-level equity with meaningful ownership from inception, aligned across funding roundsFounder-level authority, including co-decision rights on product, technology, hiring, fundraising, and strategyPre-seed capital committed by FutureSight for early hires and MVP development, with potential for follow-on fundingA proven process and playbook for taking ventures from 0 to 1, informed by our team's prior experience and mistakesVenture building and scaling resources, including embedded design, engineering, growth, and fundraising support from day oneInvestor and advisor network across B2B AI and early-stage capital marketsA true co-creation model in which you operate as CTO with FutureSight's cross-functional team as your partner — building alongside you." What you'll own (responsibilities): "As Co-Founder & CTO, you will set the venture's technical direction and lead its execution. This is a co-founder role, not a CTO hire. Technical Direction — Own problem framing, architecture, system design, and product judgment from day one, translating rough product intent into structure, context, and specs that both humans and AI systems can execute againstBuild — Use modern tools and frontier models to move fast without sacrificing quality or maintainability, designing agentic systems with first-principles thinking and knowing when orchestration adds genuine leverage versus when simplicity is the better callCustomer & Market — Be the primary technical voice in early customer conversations, understanding real workflows and shaping the right product rather than just shipping quicklyTraction Before Scale — Prove there is something worth scaling before thinking about scaling it, focusing on traction first and team-building secondCapital — Contribute to fundraising, from investor conversations to due diligenceTeam — Recruit and grow a technical team when the time is right, and establish the cultural foundation of the company" Co-Founder Profile: "Proven track record of shipping AI products to real users under real-world constraints — not research, experiments, or prototypesDeep practical experience with frontier models, LLM-based systems, and agentic architectures, with strong system design instincts and a bias for simplicity and maintainabilityStrong translation layer skills — able to turn messy product intent into clear structure, constraints, and specs that both humans and AI systems can act onClose to the customer, comfortable in customer conversations, and able to let real workflows shape what you buildRigorous about verification — feedback loops, evaluation, and systems that can be trustedPrior experience as a technical co-founder or early engineering leader, with fundraising experience a strong plusFounder at heart — energized by ambiguity, able to go far alone, and ready to commit fully" Now we need to format as HTML. We'll produce:

      About the role

      FutureSight is seeking an applied AI builder to co-found and lead the technical direction of a new B2B AI venture from the ground up. This is a co-founder partnership with founder-level equity and founder-level authority, not a salaried executive role. We are not looking for someone who manages engineers from a distance or adds AI language to a traditional CTO resume. We are looking for someone who can take a vague problem, frame it clearly, design the right system, and turn it into something customers actually use and trust. If you've gone from ambiguity to working product before — and you want to do it again with the backing of an experienced venture building team — this is the opportunity. This is a full-time, exclusive commitment to building and owning a single B2B AI venture from the ground up. FutureSight is a leading venture builder that co-creates world-class software companies with values-driven entrepreneurs from inception to exit. We are a team of founders, operators and designers with experience successfully bringing software to market at scale. You'll co-create with a proven venture building team, including John Carbrey – 4x founder, bootstrapped to $100M ARR; Joshua Auslander – seasoned CFO and strategic advisor with $200M aggregate exits; Alan Smith – globally recognized early stage validation expert, 24 products launched, an exit, 5M+ books sold; Prathna Ramesh – early-stage investor and capital strategy advisor. The partnership offers founder-level equity with meaningful ownership from inception, aligned across funding rounds; founder-level authority, including co-decision rights on product, technology, hiring, fundraising, and strategy; pre-seed capital committed by FutureSight for early hires and MVP development, with potential for follow-on funding; a proven process and playbook for taking ventures from 0 to 1, informed by our team's prior experience and mistakes; venture building and scaling resources, including embedded design, engineering, growth, and fundraising support from day one; investor and advisor network across B2B AI and early-stage capital markets; a true co-creation model in which you operate as CTO with FutureSight's cross-functional team as your partner — building alongside you.

      Responsibilities

      • Set the venture's technical direction and lead its execution as Co‑Founder & CTO (co‑founder role, not a CTO hire).
      • Own problem framing, architecture, system design, and product judgment from day one, translating rough product intent into structure, context, and specs that both humans and AI systems can execute against.
      • Use modern tools and frontier models to move fast without sacrificing quality or maintainability, designing agentic systems with first‑principles thinking and knowing when orchestration adds genuine leverage versus when simplicity is the better call.
      • Be the primary technical voice in early customer conversations, understanding real workflows and shaping the right product rather than just shipping quickly.
      • Prove there is something worth scaling before thinking about scaling it, focusing on traction first and team‑building second.
      • Contribute to fundraising, from investor conversations to due diligence.
      • Recruit and grow a technical team when the time is right, and establish the cultural foundation of the company.

      Requirements

      • Proven track record of shipping AI products to real users under real‑world constraints — not research, experiments, or prototypes.
      • Deep practical experience with frontier models, LLM‑based systems, and agentic architectures, with strong system design instincts and a bias for simplicity and maintainability.
      • Strong translation layer skills — able to turn messy product intent into clear structure, constraints, and specs that both humans and AI systems can act on.
      • Close to the customer, comfortable in customer conversations, and able to let real workflows shape what you build.
      • Rigorous about verification — feedback loops, evaluation, and systems that can be trusted.
      • Prior experience as a technical co‑found

Similar jobs