Technical Co-founder (CTO) - AI for Automotive Retail
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to parse the posting.
We need to extract sections: The posting includes:
- The Opportunity (intro paragraph)
- The Venture Atrium (description)
- The Partnership (co-founder role description)
- What You'll Own As Co-Founder & CTO (list of responsibilities)
- Co-Founder Profile Must Have (list of requirements)
- Good to have (list)
- Great to Have (list)
- How to Apply (application instructions) – we must remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should not include How to Apply.
Also need to include Pay, Schedule, Benefits only if present. Not present. So we omit those sections.
We need to 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 title given explicitly; but we can ignore.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all content except boilerplate and application instructions.
We need to decide sections: Possibly "About the role" (intro), "Responsibilities" (What You'll Own...), "Requirements" (Co-Founder Profile Must Have), "Qualifications" maybe combine Good to have and Great to Have? Could treat them as "Preferred Qualifications" or "Skills". But we need to follow allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can map:
- About the role: The Opportunity + The Venture Atrium + The Partnership (intro paragraphs)
- Responsibilities: What You'll Own As Co-Founder & CTO (list)
- Requirements: Co-Founder Profile Must Have (list)
- Qualifications: Good to have (list) maybe
- Skills: Great to Have (list) maybe
But we need to ensure we don't create sections with filler. All have content.
We must not include duplicated lines. Need to check for duplication: The text seems not duplicated.
We need to output only HTML fragment, no markdown fences.
Let's craft.
First, About the role: combine paragraphs:
"The Opportunity Every used-car dealer's profit is made or lost the moment they buy the car — not when they sell it. That decision runs on gut feel, spreadsheets, and whoever has a spare hour, inside a $500B+ industry that hasn't meaningfully modernized how it buys. We think that's an AI-native category waiting to be built, and we're going first. The problem and solution are validated with a domain co-founder who lives this daily and has already hand The Venture Atrium is an always-on AI workforce, not a dashboard — agents that watch, learn, and earn the right to act on their own, deployed inside dealer groups' existing workflows. The same decision logic has to show up everywhere the work already happens — web, desktop, our own browser, mobile — so the workforce follows the person, not the other way around. One brain, every surface. This isn't a weekend's worth of CRUD. Think dozens of specialist agents organized into a handful of coordinated workflows, sharing one memory, each one earning the right to act on its own track record — across four surfaces at once. If that sounds like a fun problem rather than a scary one, keep reading. A real technical moat if built right, and a wide-open field — no dominant AI-native player has claimed this category yet. Specifics on the product, the model, and where we stand commercially are best shared in conversation; we're early and staying deliberately quiet in the market. The Partnership CEO and domain co-founder are in place; the problem is validated. We're looking for a technical co-founder to own product and engineering from the first commit — full authority, founder equity, a real seat at the table on every major call. This is a co-founder role, not a CTO hire. In return for that level of commitment, you receive founder-level equity, founder-level authority with co-decision rights on product, technology, hiring, fundraising, and strategy, and a genuine partnership with the CEO on every material decision."
We need to ensure no stray incomplete sentence: "has already hand" seems truncated; but we must preserve as is. It's part of posting. We'll keep.
Now Responsibilities: list from "What You'll Own As Co-Founder & CTO, you will take over the production code and continue building the product (the first lines of production code), set the technical direction, and lead execution end-to-end. Own the core architecture decision that shapes everything else — how the agents actually see and act in a dealer's world, and how one system stays coherent across a web app, a desktop app, our own browser, and mobile, without four separate products drifting apartDesign the autonomy model: how an agent earns the right to act alone, and how that trust is never assumedBuild the integration layer into a data ecosystem that won't always cooperateBuild partnerships with ecosystem data providers and third-party systems to land unconventional integrations no standard API gets youOwn unit economics as an architecture problem, not an afterthought — this many agents, across this many surfaces, has to add upOwn the design and layering of the system for the dev team, and keep the build matched to what the business and sales side actually needBe the technical voice with dealers, design partners, and investorsHire and lead the founding engineering team"
We need to split into list items. The original text seems to have missing punctuation; but we can treat each sentence as a bullet. Let's parse:
- Take over the production code and continue building the product (the first lines of production code), set the technical direction, and lead execution end-to-end.
- Own the core architecture decision that shapes everything else — how the agents actually see and act in a dealer's world, and how one system stays coherent across a web app, a desktop app, our own browser, and mobile, without four separate products drifting apart.
- Design the autonomy model: how an agent earns the right to act alone, and how that trust is never assumed.
- Build the integration layer into a data ecosystem that won't always cooperate.
- Build partnerships with ecosystem data providers and third-party systems to land unconventional integrations no standard API gets you.
- Own unit economics as an architecture problem, not an afterthought — this many agents, across this many surfaces, has to add up.
- Own the design and layering of the system for the dev team, and keep the build matched to what the business and sales side actually need.
- Be the technical voice with dealers, design partners, and investors.
- Hire and lead the founding engineering team.
We'll output as
- ... etc.
Now Requirements: Co-Founder Profile Must Have list:
- Has shipped agentic or LLM systems into production where being wrong actually costs something
- Has shipped desktop and mobile apps connected to a larger web platform — comfortable with one product living across multiple facets and surfaces, not just a single app
- Has shipped LLM-based products, but also worked with SLMs and SLM fine-tuning
- Has dealt with the real nuances of web scraping — anti-bot defences, rate limits, brittle DOMs, the gap between "works in a demo" and "works at scale against a site that doesn't want you there"
- Has built complex, modelled data graph layers for intelligence — not just a data pipeline, but a structure that reasoning can actually run on
- Comfortable owning infra, data, and product alone — then hiring past yourself
- Treats guardrails and reversibility as core product, not overhead
Now Good to have: list:
- edge computing and power-constrained systems
- high-frequency distributed computing infrastructure
Now Great to Have: list:
- Experience building against locked-down or adversarial third-party data
- Vertical/operational domain grit (Automotive)
- Pragmatic and creative — a solution finder who gets to "working" fast and iterates from there
- Co-operative, strategic, and hands-on in equal measure
We need to decide which heading to use for each list. According to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can map:
- About the role: intro paragraphs.
- Responsibilities: What You'll Own...
- Requirements: Co-Founder Profile Must Have
- Qualifications: Good to have
- Skills: Great to Have
We must not create sections with filler; all have content.
Now output HTML fragment:
About the role
...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Skills
...
No Benefits/Pay/Schedule.
Make sure to preserve all content exactly as in posting, but we may need to adjust punctuation for readability but not change meaning. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must not omit any detail. Changing punctuation is okay as long as meaning unchanged. We'll keep the content.
We need to be careful not to introduce new info.
Let's craft the About the role paragraph exactly as given, but we can combine sentences. The original had some run-on sentences; we can keep them as is.
Original About the role text (from start to before "What You'll Own"):
"The Opportunity Every used-car dealer's profit is made or lost the moment they buy the car — not when they sell it. That decision runs on gut feel, spreadsheets, and whoever has a spare hour, inside a $500B+ industry that hasn't meaningfully modernized how it buys. We think that's an AI-native category waiting to be built, and we're going first. The problem and solution are validated with a domain co-founder who lives this daily and has already hand The Venture Atrium is an always-on AI workforce, not a dashboard — agents that watch, learn, and earn the right to act on their own, deployed inside dealer groups' existing workflows. The same decision logic has to show up everywhere the work already happens — web, desktop, our own browser, mobile — so the workforce follows the person, not the other way around. One brain, every surface. This isn't a weekend's worth of CRUD. Think dozens of specialist agents organized into a handful of coordinated workflows, sharing one memory, each one earning the right to act on its own track record — across four surfaces at once. If that sounds like a fun problem rather than a scary one, keep reading. A real technical moat if built right, and a wide-open field — no dominant AI-native player has claimed this category yet. Specifics on the product, the model, and where we stand commercially are best shared in conversation; we're early and staying deliberately quiet in the market. The Partnership CEO and domain co-founder are in place; the problem is validated. We're looking for a technical co-founder to own product and engineering from the first commit — full authority, founder equity, a real seat at the table on every major call. This is a co-founder role, not a CTO hire. In return for that level of commitment, you receive founder-level equity, founder-level authority with co-decision rights on product, technology, hiring, fundraising, and strategy, and a genuine partnership with the CEO on every material decision."
We need to ensure we didn't miss any text. There's a weird phrase "has already hand The Venture Atrium". It's likely a typo but we must keep.
Now Responsibilities list: we need to ensure we captured all bullet points from that paragraph. Let's extract each distinct responsibility:
Original sentence: "What You'll Own As Co-Founder & CTO, you will take over the production code and continue building the product (the first lines of production
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. No job title given explicitly; but we can ignore. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all content except boilerplate and application instructions. We need to decide sections: Possibly "About the role" (intro), "Responsibilities" (What You'll Own...), "Requirements" (Co-Founder Profile Must Have), "Qualifications" maybe combine Good to have and Great to Have? Could treat them as "Preferred Qualifications" or "Skills". But we need to follow allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: The Opportunity + The Venture Atrium + The Partnership (intro paragraphs) - Responsibilities: What You'll Own As Co-Founder & CTO (list) - Requirements: Co-Founder Profile Must Have (list) - Qualifications: Good to have (list) maybe - Skills: Great to Have (list) maybe But we need to ensure we don't create sections with filler. All have content. We must not include duplicated lines. Need to check for duplication: The text seems not duplicated. We need to output only HTML fragment, no markdown fences. Let's craft. First, About the role: combine paragraphs: "The Opportunity Every used-car dealer's profit is made or lost the moment they buy the car — not when they sell it. That decision runs on gut feel, spreadsheets, and whoever has a spare hour, inside a $500B+ industry that hasn't meaningfully modernized how it buys. We think that's an AI-native category waiting to be built, and we're going first. The problem and solution are validated with a domain co-founder who lives this daily and has already hand The Venture Atrium is an always-on AI workforce, not a dashboard — agents that watch, learn, and earn the right to act on their own, deployed inside dealer groups' existing workflows. The same decision logic has to show up everywhere the work already happens — web, desktop, our own browser, mobile — so the workforce follows the person, not the other way around. One brain, every surface. This isn't a weekend's worth of CRUD. Think dozens of specialist agents organized into a handful of coordinated workflows, sharing one memory, each one earning the right to act on its own track record — across four surfaces at once. If that sounds like a fun problem rather than a scary one, keep reading. A real technical moat if built right, and a wide-open field — no dominant AI-native player has claimed this category yet. Specifics on the product, the model, and where we stand commercially are best shared in conversation; we're early and staying deliberately quiet in the market. The Partnership CEO and domain co-founder are in place; the problem is validated. We're looking for a technical co-founder to own product and engineering from the first commit — full authority, founder equity, a real seat at the table on every major call. This is a co-founder role, not a CTO hire. In return for that level of commitment, you receive founder-level equity, founder-level authority with co-decision rights on product, technology, hiring, fundraising, and strategy, and a genuine partnership with the CEO on every material decision." We need to ensure no stray incomplete sentence: "has already hand" seems truncated; but we must preserve as is. It's part of posting. We'll keep. Now Responsibilities: list from "What You'll Own As Co-Founder & CTO, you will take over the production code and continue building the product (the first lines of production code), set the technical direction, and lead execution end-to-end. Own the core architecture decision that shapes everything else — how the agents actually see and act in a dealer's world, and how one system stays coherent across a web app, a desktop app, our own browser, and mobile, without four separate products drifting apartDesign the autonomy model: how an agent earns the right to act alone, and how that trust is never assumedBuild the integration layer into a data ecosystem that won't always cooperateBuild partnerships with ecosystem data providers and third-party systems to land unconventional integrations no standard API gets youOwn unit economics as an architecture problem, not an afterthought — this many agents, across this many surfaces, has to add upOwn the design and layering of the system for the dev team, and keep the build matched to what the business and sales side actually needBe the technical voice with dealers, design partners, and investorsHire and lead the founding engineering team" We need to split into list items. The original text seems to have missing punctuation; but we can treat each sentence as a bullet. Let's parse: - Take over the production code and continue building the product (the first lines of production code), set the technical direction, and lead execution end-to-end. - Own the core architecture decision that shapes everything else — how the agents actually see and act in a dealer's world, and how one system stays coherent across a web app, a desktop app, our own browser, and mobile, without four separate products drifting apart. - Design the autonomy model: how an agent earns the right to act alone, and how that trust is never assumed. - Build the integration layer into a data ecosystem that won't always cooperate. - Build partnerships with ecosystem data providers and third-party systems to land unconventional integrations no standard API gets you. - Own unit economics as an architecture problem, not an afterthought — this many agents, across this many surfaces, has to add up. - Own the design and layering of the system for the dev team, and keep the build matched to what the business and sales side actually need. - Be the technical voice with dealers, design partners, and investors. - Hire and lead the founding engineering team. We'll output as
- ... etc.
Now Requirements: Co-Founder Profile Must Have list:
- Has shipped agentic or LLM systems into production where being wrong actually costs something
- Has shipped desktop and mobile apps connected to a larger web platform — comfortable with one product living across multiple facets and surfaces, not just a single app
- Has shipped LLM-based products, but also worked with SLMs and SLM fine-tuning
- Has dealt with the real nuances of web scraping — anti-bot defences, rate limits, brittle DOMs, the gap between "works in a demo" and "works at scale against a site that doesn't want you there"
- Has built complex, modelled data graph layers for intelligence — not just a data pipeline, but a structure that reasoning can actually run on
- Comfortable owning infra, data, and product alone — then hiring past yourself
- Treats guardrails and reversibility as core product, not overhead
Now Good to have: list:
- edge computing and power-constrained systems
- high-frequency distributed computing infrastructure
Now Great to Have: list:
- Experience building against locked-down or adversarial third-party data
- Vertical/operational domain grit (Automotive)
- Pragmatic and creative — a solution finder who gets to "working" fast and iterates from there
- Co-operative, strategic, and hands-on in equal measure
We need to decide which heading to use for each list. According to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can map:
- About the role: intro paragraphs.
- Responsibilities: What You'll Own...
- Requirements: Co-Founder Profile Must Have
- Qualifications: Good to have
- Skills: Great to Have
We must not create sections with filler; all have content.
Now output HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
- ... etc.
Now Requirements: Co-Founder Profile Must Have list:
- Has shipped agentic or LLM systems into production where being wrong actually costs something
- Has shipped desktop and mobile apps connected to a larger web platform — comfortable with one product living across multiple facets and surfaces, not just a single app
- Has shipped LLM-based products, but also worked with SLMs and SLM fine-tuning
- Has dealt with the real nuances of web scraping — anti-bot defences, rate limits, brittle DOMs, the gap between "works in a demo" and "works at scale against a site that doesn't want you there"
- Has built complex, modelled data graph layers for intelligence — not just a data pipeline, but a structure that reasoning can actually run on
- Comfortable owning infra, data, and product alone — then hiring past yourself
- Treats guardrails and reversibility as core product, not overhead
Now Good to have: list:
- edge computing and power-constrained systems
- high-frequency distributed computing infrastructure
Now Great to Have: list:
- Experience building against locked-down or adversarial third-party data
- Vertical/operational domain grit (Automotive)
- Pragmatic and creative — a solution finder who gets to "working" fast and iterates from there
- Co-operative, strategic, and hands-on in equal measure
We need to decide which heading to use for each list. According to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can map:
- About the role: intro paragraphs.
- Responsibilities: What You'll Own...
- Requirements: Co-Founder Profile Must Have
- Qualifications: Good to have
- Skills: Great to Have
We must not create sections with filler; all have content.
Now output HTML fragment: