Founding Engineer - AI & Full-Stack
under About the role or maybe not needed as heading. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with location, employment type, experience, openings. We need to preserve all substantive information. So we must include details: early-stage AI startup building intelligent software automating workflows across voice, SMS, email. Founding-level engineering opportunity. etc. We need to output only HTML fragment, no markdown fences. Let's structure:
Location: San Francisco, CA (onsite). Employment: Full-Time. Experience: 0-6 years. Openings: 3.
ThenAbout the role
with paragraphs describing the startup, founding-level opportunity, etc. ThenResponsibilities
with- items from "What You'll Do:" list.
Then
Requirements
with- for Required items and maybe Strongly Preferred? Could separate into Requirements and Preferred but we only have Requirements heading; we could include both required and strongly preferred under Requirements, but maybe better to have Qualifications for preferred. However we have Qualifications heading available. We could put Required under Requirements, and Strongly Preferred under Qualifications. That seems reasonable.
Thus:
Requirements
with Required list.Qualifications
with Strongly Preferred list. ThenBenefits
with list: Comprehensive health, dental, and vision insurance; PTO; 401(k) retirement plan; High-ownership environment with direct access to leadership; Opportunity to make a significant impact at an early-stage AI startup. ThenPay
with paragraph: $170K-$250K base salary + Equity 0.5%-1.5%. ThenSchedule
with paragraph: 6 days/week; Weekdays: 10 AM-9 PM; Sixth day: 12 PM-7 PM. We must not repeat job title as heading. No mention of job title. We must not include boilerplate like EEO etc. Not present. We must not include application instructions (the "Interested? If you're excited..." part). Must drop that. We must not include duplicated lines. Check that we preserve all substantive information: The description about startup, founding-level opportunity, etc. The responsibilities list fully captured. The required list fully captured. The strongly preferred list fully captured. Benefits list captured. Compensation and equity captured. Schedule captured. Location, employment type, experience, openings captured in opening paragraph. Check for any missing: "We're working with an early-stage AI startup building intelligent software that automates complex, high-volume customer workflows across voice, SMS, and email." That's in About the role. "This is a true founding-level engineering opportunity for someone who wants significant ownership, moves quickly, and enjoys solving problems where there isn't an established playbook." Also in About. "You'll work across the full stack while helping build and scale production AI agents, integrations, and workflow systems." Also. Also "What Makes This Role Different:" paragraph and "Ideal Background" etc. Those are substantive; we might include them under About the role or maybe a separate section like "What makes this role different". But we only have allowed headings list; we could add another heading like "About the role" and include all that prose. Could also add a heading "What makes this role different" but not in list; better to stick to allowed headings. So we can incorporate that content into About the role paragraph(s). Ensure we don't lose details: The "What Makes This Role Different:" paragraph describing expectation to figure things out, build, ship, break, fix, improve, ideal candidate can walk through something substantial they've built and explain... Also "Ideal Background - You might be a:" list. Also "Technology:" list. Also "Work Environment:" paragraph. All these are substantive. We need to preserve all. So we need to include them somewhere. Could add a section "About the role" with multiple paragraphs covering all that. Or we could add a section "What makes this role different" but not in allowed headings; maybe we can still usefor any heading, but instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Safer to stick to those. Thus we need to fit all content under those headings. We can put the "What Makes This Role Different:" and "Ideal Background" and "Technology" and "Work Environment" under About the role as additional paragraphs. Also the "Openings: 3" we already included in opening paragraph. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's craft:
Location: San Francisco, CA (onsite). Employment: Full-Time. Experience: 0-6 years. Openings: 3.
About the role
We're working with an early-stage AI startup building intelligent software that automates complex, high-volume customer workflows across voice, SMS, and email. This is a true founding-level engineering opportunity for someone who wants significant ownership, moves quickly, and enjoys solving problems where there isn't an established playbook. You'll work across the full stack while helping build and scale production AI agents, integrations, and workflow systems.
What makes this role different: This isn't a role where you'll simply receive tickets and implement predefined requirements. You'll be expected to figure things out, build, ship, break things, fix them, and improve them. The ideal candidate can walk through something substantial they've built and clearly explain: What was the problem? → What did you build? → What did you personally own? → What were the hardest technical decisions? → What broke? → How did you fix it? → How did you scale it? We're particularly interested in engineers who can demonstrate real-world impact, regardless of whether that experience came from a startup, previous employer, open-source project, or something they built independently.
Ideal background - you might be a:
- Founding or early engineer at a startup
- Engineer #1-10 at an early-stage company
- Full-stack engineer building AI-powered products
- New or recent CS graduate with exceptional technical projects
- Software engineer who has independently built and shipped products
- Engineer with experience integrating complex or difficult external systems
Technology: TypeScript, Python, AWS, Next.js, LLMs, AI Agents, APIs, Voice, SMS, Email, Full-Stack.
Work environment: This is an in-person, high-intensity startup environment in San Francisco. The team moves quickly, expects a high degree of ownership, and is looking for engineers who are excited by ambitious goals and a demanding pace.
Responsibilities
- Build and scale production AI agents across voice, SMS, and email
- Design systems that maintain context and consistency across multi-channel interactions
- Develop full-stack product experiences and internal tools
- Build complex API integrations and custom adapters
- Work with external systems that may have limited or inconsistent APIs
- Develop scheduling and workflow orchestration systems
- Build infrastructure for scaling LLM-powered applications
- Improve agent state, memory, personalization, and reasoning
- Own features from problem definition → design → implementation → deployment → iteration
- Troubleshoot production issues and make architectural decisions as the product evolves
- Work closely with the founding team to turn ambiguous problems into working products
Requirements
- 1-6 years of software engineering experience
- Strong TypeScript and Python experience
- Full-stack development experience
- Experience shipping real production software
- Strong software engineering and computer science fundamentals
- Experience owning projects or systems end-to-end
- Ability to make sound technical decisions with limited direction
- Comfortable working through ambiguous, technically challenging problems
- Strong understanding of the systems you've built and the architectural decisions behind them
- Demonstrated ability to learn quickly and take on new technologies
- Willingness to work in-person in San Francisco 6 days/week
- Comfortable working in a highly demanding, fast-paced startup environment
Qualifications
- Strongly Preferred: AI agents or production LLM applications
- LLM orchestration
- Voice AI
- SMS/email automation
- Conversational AI
- Agent state and memory
- Complex API integrations
- Reverse-engineering or integrating with legacy systems
- Scheduling or workflow systems
- Healthcare or other highly regulated industries
- High-volume communication platforms
- AWS
- Next.js
- TypeScript
- Python
- Open-source or significant personal projects
- Early-stage or founding startup experience
Benefits
- Comprehensive health, dental, and vision insurance
- PTO
- 401(k) retirement plan
- High-ownership environment with direct access to leadership
- Opportunity to make a significant impact at an early-stage AI startup
Pay
Compensation: $170K-$250K base salary + Equity: 0.5%-1.5%
Schedule
6 days/week; Weekdays: 10 AM-9 PM; Sixth day: 12 PM-7 PM
Check for any missing: The "Openings: 3" we included. Good. We didn't include
- for Required items and maybe Strongly Preferred? Could separate into Requirements and Preferred but we only have Requirements heading; we could include both required and strongly preferred under Requirements, but maybe better to have Qualifications for preferred. However we have Qualifications heading available. We could put Required under Requirements, and Strongly Preferred under Qualifications. That seems reasonable.
Thus: