Technical Co-founder (CTO)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions? The instruction says: remove application instructions. So we should not include "How to Apply" etc. Also remove diversity statement? That's EEO/equal-opportunity boilerplate, should be removed. So we need to extract content: The posting includes sections: The Opportunity (description), About FutureSight, The Partnership, What you'll own, Co-Founder Profile. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content fits which heading. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if we have content. We must not create sections with filler. So we need to see if we have content for each. We have description of role: "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. ... This is a full-time, exclusive commitment to building and owning a single B2B AI venture from the ground up." That could go under About the role. Responsibilities: "What you'll own As Co-Founder & CTO, you will set the venture's technical direction and lead its execution." Then bullet list: Technical Direction, Build, Customer & Market, Traction Before Scale, Capital, Team. Those are responsibilities. Requirements/Qualifications/Skills: The "Co-Founder Profile" lists required experience: Proven track record of shipping AI products to real users under real-world constraints, Deep practical experience with frontier models, LLM-based systems, agentic architectures, Strong translation layer skills, Close to the customer, Rigorous about verification, Prior experience as a technical co-founder or early engineering leader, with fundraising experience a strong plus, Founder at heart. Those could be Requirements or Qualifications or Skills. We need to decide distribution. Could put them under Requirements (or Qualifications). Since we have three possible headings, we could combine: Requirements (hard requirements), Qualifications (preferred), Skills (specific skills). But we must not create sections with filler. We have enough content to fill each maybe. Benefits, Pay, Schedule: The posting mentions founder-level equity, pre-seed capital committed, potential follow-on funding, venture building resources, investor network, etc. Those could be Benefits. Pay: not specified as salary; it's equity, not salary. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention founder-level equity, pre-seed capital committed, etc. That's compensation/benefits. So we can include Benefits section describing equity, capital, resources. Pay: not specified as salary; we could omit Pay section because no explicit salary. Schedule: mentions full-time, exclusive commitment. That's schedule info. So we can include Schedule section: full-time, exclusive commitment. Thus we will produce sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Schedule. Possibly also Qualifications if we split. But we need to avoid thin sections. Let's allocate: - About the role: description of opportunity, full-time exclusive commitment? Actually schedule separate. So About the role: description of role, co-founder partnership, etc. - Responsibilities: the bullet list under "What you'll own". - Requirements: maybe the mandatory items: Proven track record of shipping AI products to real users under real-world constraints, Deep practical experience with frontier models, LLM-based systems, agentic architectures, Strong translation layer skills, Close to the customer, Rigorous about verification, Prior experience as a technical co-founder or early engineering leader. - Qualifications: maybe fundraising experience a strong plus, Founder at heart (energized by ambiguity, able to go far alone, ready to commit fully). Could be qualifications. - Skills: maybe specific skills: system design instincts, bias for simplicity, ability to translate product intent, etc. But we might overlap. Could combine Requirements and Qualifications into one section? But we have to use headings only if we have real content. We could have just Requirements and Skills, and omit Qualifications if it's thin. However we have content for both. Better to follow typical pattern: Requirements (must-have), Qualifications (nice-to-have), Skills (specific abilities). Let's assign: Requirements: - Proven track record of shipping AI products to real users under real-world constraints. - Deep practical experience with frontier models, LLM-based systems, and agentic architectures. - 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-founder or early engineering leader. Qualifications: - Fundraising experience a strong plus. - Founder at heart — energized by ambiguity, able to go far alone, and ready to commit fully. Skills: - System design instincts and a bias for simplicity and maintainability. - Knowing when orchestration adds genuine leverage versus when simplicity is the better call. - Ability to design agentic systems with first-principles thinking. - Ability to build using modern tools and frontier models to move fast without sacrificing quality or maintainability. But some of these overlap with requirements. Might be okay. Benefits: - 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. - 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. - True co-creation model: operate as CTO with FutureSight's cross-functional team as your partner. Schedule: - Full-time, exclusive commitment to building and owning a single B2B AI venture from the ground up. We must not include application instructions, diversity statement, etc. Now produce HTML fragment: Use

for each section heading, then content: either

for prose or

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep the exact phrasing? We can keep close but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not omit details. We can rephrase slightly but must keep all info. Safer to copy the sentences exactly as they appear, maybe broken into list items. Let's extract exact sentences from the posting. From "The Opportunity": "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." We can split into About the role. About FutureSight paragraph: "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." Then list of team members: "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" But that's maybe part of About FutureSight; we could include in About the role or maybe not needed. The instruction: preserve all substantive information. So we should include that info somewhere. Could be part of About the role or Benefits? It's about the team you'll work with; could be part of Benefits (resources). But we already have Benefits section covering resources. Might be okay to include in Benefits as "Venture building and scaling resources, including embedded design, engineering, growth, and fundraising support from day one" already covers that. The specific team members could be part of that. But we need to preserve all detail; we could include them in Benefits as a list. The Partnership section: "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." That's basically Benefits. What you'll own: "What you'll own 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: "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