Emergency Veterinarian - Rancho Cucamonga, CA
for section headings. Only include sections when posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also we should not repeat job title as heading. No Job ID etc.
We need to decide which sections correspond.
- About the role: could be "ABOUT VEG" and "THE JOB" combined? Actually "ABOUT VEG" is company overview, not role. "THE JOB" describes role. We could put About the role as summary of role (maybe from THE JOB). But we need to preserve content. Could create About the role section with content from THE JOB (the paragraph describing role). That seems appropriate.
- Responsibilities: from "WHAT YOU'LL DO". That's a list of duties. Use - .
- Requirements: from "WHAT YOU NEED". That's list of requirements (degree, experience, physical ability, availability). Use
- .
- Qualifications: maybe from "WHO YOU ARE" (personal attributes). Could be Qualifications or Skills. The spec includes Qualifications, Skills sections. We need to decide where to put "WHO YOU ARE". It describes personal traits: empathetic, humility, ownership, curious. Could be Qualifications or Skills. Since they are more like personal qualities, maybe Qualifications. We'll put Qualifications.
- Skills: maybe we could extract from WHAT YOU NEED includes specific skills like emergency surgery, endoscopy, etc. But those are already in Requirements. Could also put Skills separate but risk duplication. Better to have few substantive sections. We could combine Requirements and Skills? But spec says prefer few substantive sections over many thin ones. We have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Schedule if mentioned. The posting mentions availability to work nights, weekends, holidays on rotating basis; that's schedule info. Could be Schedule section. But we could include that in Requirements (availability). However spec says include Schedule section only if posting actually states them. It does state availability to work nights, weekends, holidays. So we could create Schedule section with that detail. But then we would duplicate availability info if also in Requirements. Better to put schedule info in Schedule section and remove from Requirements? But we must preserve ALL substantive information; we can't remove it. We could keep it in both places? That would be duplication, but spec says remove duplicated lines. So we should not duplicate. So we need to decide where to place schedule info. Since schedule is a specific aspect, we could put it in Schedule section and not include it in Requirements. But Requirements also includes other things like degree, ability to lift, etc. So we can move schedule to Schedule and keep other requirements in Requirements.
- Benefits: from "HOW WE INVEST IN YOU". That includes compensation, health benefits, equity, learning, travel stipend, loan repayment, parental leave, flexible schedules, referral program, scrubs, swag, food. Also includes Pay info (wage range). Pay section separate. So Benefits section should include non-pay benefits: health and wellness, equity, learning, travel stipend, loan repayment, parental leave, flexible schedules, referral program, scrubs, swag, food. Also maybe mention QPR training, free therapy.
- Pay: from "Competitive compensation, including base and 401K match: The wage range for this role is $140,000.00 – $350,000.00 salary per year, inclusive of base salary and discretionary production bonus target. The expected base salary for this role is between $180,000.00 – $200,000.00 of this wage range." Also mention 401K match. So Pay section includes that.
- Schedule: from availability to work nights, weekends, holidays on rotating or as needed basis. Also maybe flexible work schedules mentioned in Benefits? Actually flexible work schedules is a benefit. So schedule info about required shifts (nights, weekends, holidays) goes to Schedule. Flexible work schedules benefit goes to Benefits.
- Also note "Full-time credentialed VEGgies receive a $2,500/year travel stipend. Full-time uncredentialed VEGgies receive a $1,000/year travel stipend." That's benefit.
- "Clinical student loan repayment" benefit.
- "Paid parental leave, up to 12 weeks at 100% of regular salary and inclusive fertility and family-building care for all types of families" benefit.
- "Flexible work schedules to support your life outside of work" benefit.
- "Generous employee referral program" benefit.
- "And the little (big) things, like comfy scrubs, cool VEG swag, and food in the fridge for when you're hungry" benefit.
- Also "Based on your role, you may be eligible for equity after one year of full time, active employment with VEG" benefit.
- "A BIG focus on learning and growth, from VEG-created clinical and leadership programs to unlimited ER CE + travel stipend (no really!)." benefit.
- "Comprehensive health and wellness benefits that start on day one, including QPR training and access to free therapy or counseling" benefit.
Now we need to output HTML fragment with
headings and appropriate
or
- . Ensure we don't include boilerplate like "DEI" section? The spec says include section only when posting has real specific content. DEI section is present: "DEI At VEG, diversity is not just a word..." That's substantive. Should we include as a section? The allowed headings list does not include DEI. But we could map DEI to maybe "About the role"? Not appropriate. The spec says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g. About the role, ...). Likely they expect only those headings. DEI content could be placed under About the role or Benefits? It's about culture, could be About the role? But About the role is about the job. Could create a separate section but not in list; risk being considered not following instruction. Safer to incorporate DEI content into About the role or Benefits? It's about company culture, maybe About the role includes some of that? The About VEG paragraph already covers mission and culture. DEI adds more detail about diversity. Could merge into About the role section. We'll incorporate DEI content into About the role paragraph.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. We must not omit any detail. Let's list each piece.
About the role: Should include content from "ABOUT VEG" and "THE JOB" and DEI. Let's combine.
ABOUT VEG paragraph: "In 2014, VEG was born with a mission to help people and their pets when they need it most. This meant challenging the status quo and fixing everything that was wrong with the ER experience. Since then, we've expanded rapidly, with hospitals nationwide open 24/7, 365 days a year, and created a better emergency experience—not only for people and their pets, but also for everyone who works here—our VEGgies! At VEG we find a way to say yes to the career you want in veterinary emergency medicine. This means transforming how ER works, from our open-concept hospitals, where you can handle emergency cases of every kind (even exotics!) to our immersive, customer-focused experience, which helps us give people and their pets the care they deserve. This also means saying yes to creating the greatest experience possible for our VEGgies. Yes to working in an environment where you can find your place and feel valued for the amazing work you do. Yes to having unparalleled opportunities for learning and mentorship so you can grow where you want to go in your career. And yes to making an impact here in ways you never thought possible. VEG is a 2025 and 2026 certified Great Place to Work®."
THE JOB paragraph: "As an Emergency Veterinarian, you're more than just passionate about helping people and their pets; you thrive on it, especially when they need you most. At VEG, we find a way to say yes to supporting you, so you can be the best, most confident ER professional possible and grow your career in unexpected directions. With a culture rooted in mentorship and continuous learning—from on-the-floor guidance to VEG Education programs and unlimited ER-focused CE—you'll never stop learning. You'll handle any emergency that comes through the door, from routine cases to complex surgeries, and treat every kind of pet, including exotics! As a leader on the hospital floor, you'll have the chance to be a superhero for your customers, backed by a team and resources that empower you to take your career further than you ever imagined."
DEI paragraph: "At VEG, diversity is not just a word—it's a strength that fuels innovation and kindness. Our mission is 'Helping people and their pets when they need it most.' And we do that better when our VEGgies (employees) feel valued, respected, and empowered to bring their authentic selves to work. That's why we're devoted to creating an environment that reflects the diverse communities we serve—where different perspectives are not only welcomed but celebrated. We are focused on providing equitable opportunities for growth, promoting inclusive decision-making, and ensuring that everyone's perspective is considered. Saying yes to VEG means helping us build a culture where your unique experiences and background contribute to a shared vision: being the world's veterinary emergency company."
We'll combine these into About the role section, preserving all info. Use
for prose; could be multiple paragraphs.
Responsibilities: list from WHAT YOU'LL DO. Let's extract each bullet:
- Answer medical questions over the phone
- See patients right away as part of the VEG Triage and VEG Spikes, our unique, customer-centered way of doing things—like ensuring people see a doctor right away and allowing families to stay with their pets
- Gather the signalment, presenting complaint, vitals, and physical exam
- Conduct physical examinations of animals, along with other required investigatory measures such as ultrasounds, X-rays, bloodwork, and biopsies
- Complete a diagnosis of each pet's condition to create a diagnostic and therapeutic plan
- Communicate diagnosis and treatment options directly with customers
- Prepare estimates and present them to customers
- Create and review medical records to ensure accuracy
- Demonstrate the value of tests and treatments performed by speaking with the customer and addressing their concerns
- Perform minor and major emergency surgeries
- Perform endoscopic procedures
- Educate customers on after care and preventative measures where appropriate
We need to keep exact phrasing. Ensure no extra or missing.
Requirements: from WHAT YOU NEED. List:
- A DVM or equivalent degree
- Live and breathe emergency medicine, including emergency surgery (the soft tissue kind!) and endoscopy
- Thrive in team-oriented environments (think hospital retreats, team dinners, happy hours, and more)
- Ability to stand for prolonged hours, kneel, and work on the floor as well as ability to lift up to 25 kg on own and able to support up to 40 kg with assistance
- Must be willing to work in a noisy environment with strong or unpleasant odors
-
- .
- Qualifications: maybe from "WHO YOU ARE" (personal attributes). Could be Qualifications or Skills. The spec includes Qualifications, Skills sections. We need to decide where to put "WHO YOU ARE". It describes personal traits: empathetic, humility, ownership, curious. Could be Qualifications or Skills. Since they are more like personal qualities, maybe Qualifications. We'll put Qualifications.
- Skills: maybe we could extract from WHAT YOU NEED includes specific skills like emergency surgery, endoscopy, etc. But those are already in Requirements. Could also put Skills separate but risk duplication. Better to have few substantive sections. We could combine Requirements and Skills? But spec says prefer few substantive sections over many thin ones. We have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Schedule if mentioned. The posting mentions availability to work nights, weekends, holidays on rotating basis; that's schedule info. Could be Schedule section. But we could include that in Requirements (availability). However spec says include Schedule section only if posting actually states them. It does state availability to work nights, weekends, holidays. So we could create Schedule section with that detail. But then we would duplicate availability info if also in Requirements. Better to put schedule info in Schedule section and remove from Requirements? But we must preserve ALL substantive information; we can't remove it. We could keep it in both places? That would be duplication, but spec says remove duplicated lines. So we should not duplicate. So we need to decide where to place schedule info. Since schedule is a specific aspect, we could put it in Schedule section and not include it in Requirements. But Requirements also includes other things like degree, ability to lift, etc. So we can move schedule to Schedule and keep other requirements in Requirements.
- Benefits: from "HOW WE INVEST IN YOU". That includes compensation, health benefits, equity, learning, travel stipend, loan repayment, parental leave, flexible schedules, referral program, scrubs, swag, food. Also includes Pay info (wage range). Pay section separate. So Benefits section should include non-pay benefits: health and wellness, equity, learning, travel stipend, loan repayment, parental leave, flexible schedules, referral program, scrubs, swag, food. Also maybe mention QPR training, free therapy.
- Pay: from "Competitive compensation, including base and 401K match: The wage range for this role is $140,000.00 – $350,000.00 salary per year, inclusive of base salary and discretionary production bonus target. The expected base salary for this role is between $180,000.00 – $200,000.00 of this wage range." Also mention 401K match. So Pay section includes that.
- Schedule: from availability to work nights, weekends, holidays on rotating or as needed basis. Also maybe flexible work schedules mentioned in Benefits? Actually flexible work schedules is a benefit. So schedule info about required shifts (nights, weekends, holidays) goes to Schedule. Flexible work schedules benefit goes to Benefits.
- Also note "Full-time credentialed VEGgies receive a $2,500/year travel stipend. Full-time uncredentialed VEGgies receive a $1,000/year travel stipend." That's benefit.
- "Clinical student loan repayment" benefit.
- "Paid parental leave, up to 12 weeks at 100% of regular salary and inclusive fertility and family-building care for all types of families" benefit.
- "Flexible work schedules to support your life outside of work" benefit.
- "Generous employee referral program" benefit.
- "And the little (big) things, like comfy scrubs, cool VEG swag, and food in the fridge for when you're hungry" benefit.
- Also "Based on your role, you may be eligible for equity after one year of full time, active employment with VEG" benefit.
- "A BIG focus on learning and growth, from VEG-created clinical and leadership programs to unlimited ER CE + travel stipend (no really!)." benefit.
- "Comprehensive health and wellness benefits that start on day one, including QPR training and access to free therapy or counseling" benefit.
Now we need to output HTML fragment with
headings and appropriate
or
- . Ensure we don't include boilerplate like "DEI" section? The spec says include section only when posting has real specific content. DEI section is present: "DEI At VEG, diversity is not just a word..." That's substantive. Should we include as a section? The allowed headings list does not include DEI. But we could map DEI to maybe "About the role"? Not appropriate. The spec says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g. About the role, ...). Likely they expect only those headings. DEI content could be placed under About the role or Benefits? It's about culture, could be About the role? But About the role is about the job. Could create a separate section but not in list; risk being considered not following instruction. Safer to incorporate DEI content into About the role or Benefits? It's about company culture, maybe About the role includes some of that? The About VEG paragraph already covers mission and culture. DEI adds more detail about diversity. Could merge into About the role section. We'll incorporate DEI content into About the role paragraph. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. We must not omit any detail. Let's list each piece. About the role: Should include content from "ABOUT VEG" and "THE JOB" and DEI. Let's combine. ABOUT VEG paragraph: "In 2014, VEG was born with a mission to help people and their pets when they need it most. This meant challenging the status quo and fixing everything that was wrong with the ER experience. Since then, we've expanded rapidly, with hospitals nationwide open 24/7, 365 days a year, and created a better emergency experience—not only for people and their pets, but also for everyone who works here—our VEGgies! At VEG we find a way to say yes to the career you want in veterinary emergency medicine. This means transforming how ER works, from our open-concept hospitals, where you can handle emergency cases of every kind (even exotics!) to our immersive, customer-focused experience, which helps us give people and their pets the care they deserve. This also means saying yes to creating the greatest experience possible for our VEGgies. Yes to working in an environment where you can find your place and feel valued for the amazing work you do. Yes to having unparalleled opportunities for learning and mentorship so you can grow where you want to go in your career. And yes to making an impact here in ways you never thought possible. VEG is a 2025 and 2026 certified Great Place to Work®." THE JOB paragraph: "As an Emergency Veterinarian, you're more than just passionate about helping people and their pets; you thrive on it, especially when they need you most. At VEG, we find a way to say yes to supporting you, so you can be the best, most confident ER professional possible and grow your career in unexpected directions. With a culture rooted in mentorship and continuous learning—from on-the-floor guidance to VEG Education programs and unlimited ER-focused CE—you'll never stop learning. You'll handle any emergency that comes through the door, from routine cases to complex surgeries, and treat every kind of pet, including exotics! As a leader on the hospital floor, you'll have the chance to be a superhero for your customers, backed by a team and resources that empower you to take your career further than you ever imagined." DEI paragraph: "At VEG, diversity is not just a word—it's a strength that fuels innovation and kindness. Our mission is 'Helping people and their pets when they need it most.' And we do that better when our VEGgies (employees) feel valued, respected, and empowered to bring their authentic selves to work. That's why we're devoted to creating an environment that reflects the diverse communities we serve—where different perspectives are not only welcomed but celebrated. We are focused on providing equitable opportunities for growth, promoting inclusive decision-making, and ensuring that everyone's perspective is considered. Saying yes to VEG means helping us build a culture where your unique experiences and background contribute to a shared vision: being the world's veterinary emergency company." We'll combine these into About the role section, preserving all info. Use
for prose; could be multiple paragraphs. Responsibilities: list from WHAT YOU'LL DO. Let's extract each bullet: - Answer medical questions over the phone - See patients right away as part of the VEG Triage and VEG Spikes, our unique, customer-centered way of doing things—like ensuring people see a doctor right away and allowing families to stay with their pets - Gather the signalment, presenting complaint, vitals, and physical exam - Conduct physical examinations of animals, along with other required investigatory measures such as ultrasounds, X-rays, bloodwork, and biopsies - Complete a diagnosis of each pet's condition to create a diagnostic and therapeutic plan - Communicate diagnosis and treatment options directly with customers - Prepare estimates and present them to customers - Create and review medical records to ensure accuracy - Demonstrate the value of tests and treatments performed by speaking with the customer and addressing their concerns - Perform minor and major emergency surgeries - Perform endoscopic procedures - Educate customers on after care and preventative measures where appropriate We need to keep exact phrasing. Ensure no extra or missing. Requirements: from WHAT YOU NEED. List: - A DVM or equivalent degree - Live and breathe emergency medicine, including emergency surgery (the soft tissue kind!) and endoscopy - Thrive in team-oriented environments (think hospital retreats, team dinners, happy hours, and more) - Ability to stand for prolonged hours, kneel, and work on the floor as well as ability to lift up to 25 kg on own and able to support up to 40 kg with assistance - Must be willing to work in a noisy environment with strong or unpleasant odors -
- . Ensure we don't include boilerplate like "DEI" section? The spec says include section only when posting has real specific content. DEI section is present: "DEI At VEG, diversity is not just a word..." That's substantive. Should we include as a section? The allowed headings list does not include DEI. But we could map DEI to maybe "About the role"? Not appropriate. The spec says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use