AI Product Engineer
Jerry · Austin, TX · 3 wk ago
HybridEngineering$240/hrFull-time
We need to output HTML fragment with 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. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Why You Should Join Us (intro) – could be "About the role"? Actually "Why You Should Join Us" is like company description. Could be "About the role" maybe includes description of role and company. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content.
We have:
- Description of company and mission: "Why You Should Join Us Jerry.ai is a profitable, Series C, YC-backed tech startup..." That's about the company, could go under "About the role" or maybe separate "About Jerry.ai" later. There's also a later "About Jerry.ai" section near the end.
- "The Technical Challenge" – describes what the team does, could be responsibilities.
- "What You’ll Own" – responsibilities.
- "Who You Are" – qualifications/requirements.
- "Our tech stack:" – skills.
- "While we appreciate your interest..." – application instructions (to remove).
- "Please note: Jerry.ai is only able to hire full-time salaried employees who currently reside in AZ, CA, CO, FL, GA, IL, MA, NC, NJ, NV, NY, OR, TN, TX, UT, VA, or Ontario, Canada, and full-time hourly employees who currently reside in AZ, FL, GA, NV, NY, NC, TN, TX, UT, or VA." – location restrictions (could be part of Requirements? Might be considered a requirement). We'll include maybe under Requirements.
- "Jerry.ai is proud to be an Equal Employment Opportunity employer..." – EEO boilerplate to remove.
- "Jerry.ai is committed to providing reasonable accommodations..." – accommodation statement (boilerplate? Might be considered EEO; remove.)
- "The successful candidate’s starting pay will fall within the pay range listed on this job posting..." – Pay info: we have no explicit range given. It says "starting pay will fall within the pay range listed on this job posting, determined based on job-related factors..." but no actual numbers. Since we should not include Pay section unless posting actually states them. It does not give numbers, just says range listed on posting (but we don't have it). So we should NOT include Pay section because no concrete range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: later: "In addition to base salary, the compensation may include opportunities for equity grants. We offer a comprehensive benefits package to regular employees, including health, dental, and vision coverage, paid time off, paid parental leave, 401(K) plan with employer matching, and wellness benefits, among others. Equity opportunities may also be part of your total rewards package. Part-time, contract, or freelance roles may not be eligible for certain benefits." That's benefits info. So we can include Benefits section.
- Schedule: not mentioned (no mention of full-time/part-time? It mentions full-time salaried employees and full-time hourly employees. Could infer schedule is full-time. But we should not create Schedule unless posting actually states them. It does state full-time salaried and full-time hourly employees. That implies schedule is full-time. Might be considered schedule info. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time (schedule). So we could include Schedule section with "Full-time". But we need to see if that's considered schedule. Probably yes. We'll include Schedule.
- About Jerry.ai section at end: could be part of About the role or separate About Jerry.ai. Since we have About the role heading, we can put company description there. The later About Jerry.ai repeats some info; we can merge.
We must not repeat job title as heading. No job title given explicitly; but we can ignore.
We must output only HTML fragment, no markdown fences.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content.
We have:
- Description of company and mission: "Why You Should Join Us Jerry.ai is a profitable, Series C, YC-backed tech startup..." That's about the company, could go under "About the role" or maybe separate "About Jerry.ai" later. There's also a later "About Jerry.ai" section near the end.
- "The Technical Challenge" – describes what the team does, could be responsibilities.
- "What You’ll Own" – responsibilities.
- "Who You Are" – qualifications/requirements.
- "Our tech stack:" – skills.
- "While we appreciate your interest..." – application instructions (to remove).
- "Please note: Jerry.ai is only able to hire full-time salaried employees who currently reside in AZ, CA, CO, FL, GA, IL, MA, NC, NJ, NV, NY, OR, TN, TX, UT, VA, or Ontario, Canada, and full-time hourly employees who currently reside in AZ, FL, GA, NV, NY, NC, TN, TX, UT, or VA." – location restrictions (could be part of Requirements? Might be considered a requirement). We'll include maybe under Requirements.
- "Jerry.ai is proud to be an Equal Employment Opportunity employer..." – EEO boilerplate to remove.
- "Jerry.ai is committed to providing reasonable accommodations..." – accommodation statement (boilerplate? Might be considered EEO; remove.)
- "The successful candidate’s starting pay will fall within the pay range listed on this job posting..." – Pay info: we have no explicit range given. It says "starting pay will fall within the pay range listed on this job posting, determined based on job-related factors..." but no actual numbers. Since we should not include Pay section unless posting actually states them. It does not give numbers, just says range listed on posting (but we don't have it). So we should NOT include Pay section because no concrete range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: later: "In addition to base salary, the compensation may include opportunities for equity grants. We offer a comprehensive benefits package to regular employees, including health, dental, and vision coverage, paid time off, paid parental leave, 401(K) plan with employer matching, and wellness benefits, among others. Equity opportunities may also be part of your total rewards package. Part-time, contract, or freelance roles may not be eligible for certain benefits." That's benefits info. So we can include Benefits section.
- Schedule: not mentioned (no mention of full-time/part-time? It mentions full-time salaried employees and full-time hourly employees. Could infer schedule is full-time. But we should not create Schedule unless posting actually states them. It does state full-time salaried and full-time hourly employees. That implies schedule is full-time. Might be considered schedule info. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time (schedule). So we could include Schedule section with "Full-time". But we need to see if that's considered schedule. Probably yes. We'll include Schedule.
- About Jerry.ai section at end: could be part of About the role or separate About Jerry.ai. Since we have About the role heading, we can put company description there. The later About Jerry.ai repeats some info; we can merge.
We must not repeat job title as heading. No job title given explicitly; but we can ignore.
We must output only HTML fragment, no markdown fences.
We need to use for each section heading, then content:
for prose,
- for lists.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract substantive content.
**About the role / Company description**:
From "Why You Should Join Us":
- Jerry.ai is a profitable, Series C, YC-backed tech startup with 5M+ customers and $240M in funding.
- Building the first AI-powered advisor to manage all your physical assets.
- Started with car insurance in 2019, now expanding into new verticals (home, motorcycle, RV, boat).
- Opportunity massive — car insurance alone is a $300B market in the U.S.
- Built supply (work with 100+ insurance carriers) and technical infrastructure (60% of policies sold automatically without human intervention, 90% of inbound customer inquiries resolved via AI and automation).
- Next chapter: accelerate growth — going from 5M to 50M customers by 2030.
From "About Jerry.ai" later:
- Jerry is building the first AI-powered advisor to manage all your physical assets.
- Car, home, motorcycle aren't just purchases, they're the physical embodiment of the life you've worked hard to build.
- Experience of owning them stuck in the 90s; every step fragmented, complicated, expensive.
- Imagine having a trusted friend in your pocket who takes care of everything: find right car/home at right price, lock in best insurance rate, remind before service appointment turns into expensive repair, help sell at best price.
- That friend is Jerry.
- Started with car insurance in 2019, became one of top 3 brokers in U.S., added driving insights, diagnostics, repair marketplace.
- Reached 5M+ customers, raised $240M+, profitable since 2024.
- Expanding into home, motorcycle, RV, and beyond.
- Led by serial entrepreneurs and backed by Y Combinator; team comprises talented leaders from Nvidia, Meta, Amazon, BCG, McKinsey, Bain, GEICO.
- Culture is #1 reason people join and stay — small and mighty team of competitive but kind people who think and act like owners, care deeply about quality and impact, relentless in pursuit of learning and mastery.
- Proud to consistently rank as one of Y Combinator's Top Companies, Forbes and Statista's Best Startup Employers, and other accolades in fintech and insurtech innovation, workplace culture, leadership.
- Remote-first company, but also have offices in Palo Alto, New York City, Chicago, Toronto.
We should combine but avoid duplication. We'll produce a concise but comprehensive paragraph(s) covering these points.
**Responsibilities** (What You’ll Own + The Technical Challenge maybe):
From "The Technical Challenge":
- AI & Automation team owns most critical part: automate entire insurance quoting experience for customers and orchestrate complex, multi-step transactions with external insurance provider systems to finalize policy purchases.
- Before off-the-shelf AI agents existed, built proprietary infrastructure to scale automated insurance purchases and customer support.
- Today, 60% of insurance policies sold automatically without human intervention, and 78% of inbound customer inquiries resolved via AI and automation, with 83% reporting a positive experience.
- System working but use cases rapidly growing as business expands beyond car insurance and AI models evolving.
- Need someone to lead charge in building “next generation” AI system, including building new automations for things like document validation (drivers’ licenses, proof of insurance, etc), voicebot expansion into stateful, phone-based interactions, and enable bots to have direct external system navigation to resolve complex issues more quickly and accurately than human agents.
From "What You’ll Own":
- Our AI agents and automation system, which has two components:
- Agentic/conversational front end — chatbot, voicebot, computer-use agents; shape what the prompt engineering team builds next and keep the architecture sound as it scales.
- Backend workflow automation — build new automations for things like document validation (ex. licenses, proof of insurance), record disputes, transaction orchestration with external carrier systems.
- Evaluate emerging AI technology (voicebot, computer use agents, and beyond), make the call on what we invest in next, build and ship to production.
- Partner with OpenAI to evaluate and deploy next-generation voice models and workflow automation.
We can combine into responsibilities list.
**Requirements / Qualifications** (Who You Are + location restrictions + maybe tech stack? Actually tech stack is skills.)
From "Who You Are":
- 5+ years in software engineering, ideally at an early-stage startup where you’ve owned outcomes end-to-end.
- You are a builder at heart. You don't need someone else to write the spec.
- You've tinkered with a new model within days of its release, and you can explain why one architecture or approach is superior to another.
- Experience putting LLM-based systems into production, including the unglamorous parts: evals, regressions, latency, cost, and failure-handling.
Location restrictions:
- Jerry.ai is only able to hire full-time salaried employees who currently reside in AZ, CA, CO, FL, GA, IL, MA, NC, NJ, NV, NY, OR, TN, TX, UT, VA, or Ontario, Canada, and full-time hourly employees who currently reside in AZ, FL, GA, NV, NY, NC, TN, TX, UT, or VA.
- Cannot accept applications from candidates residing elsewhere at this time.
We could treat location as a requirement.
**Skills** (Our tech stack):
- TypeScript (Nest.js, React), GraphQL, AWS (ECS/EKS, Lambda), LLM models (OpenAI, Anthropic Claude, Google Gemini)
**Benefits**:
- In addition to base salary, compensation may include opportunities for equity grants.
- Comprehensive benefits package to regular employees, including health, dental, and vision coverage, paid time off, paid parental leave, 401(K) plan with employer matching, and wellness benefits, among others.
- Equity opportunities may also be part of total rewards package.
- Part-time, contract, or freelance roles may not be eligible for certain benefits.
**Schedule**:
- Full-time salaried employees and full-time hourly employees (implies full-time). We can state "Full-time".
We should not include Pay section because no explicit range.
We must not include boilerplate like EEO, accommodation statement, application instructions, etc.
Now produce HTML.
Structure:
About the role
... combined description ...
Responsibilities
- ... each bullet ...
Requirements
- ... each bullet ...
Skills
- ... each bullet ...
Benefits
- ... each bullet ...
Schedule
Full-time
Check that we didn't miss any substantive info: The description of "The Technical Challenge" includes stats: 60% policies sold automatically, 78% inbound inquiries resolved via AI, 83% positive experience. Also mention that they built proprietary infrastructure before off-the-shelf AI agents. Also mention that they work with 100+ insurance carriers. Also mention that they have 5M+ customers, $240M funding, profitable since 2024, expanding into new verticals, goal 50M by 2030. Also mention that they are Series C, YC-backed. Also mention that they have offices in Palo Alto, NYC, Chicago, Toronto. Also mention that they are remote-first. We need to include all that in About the role.