Emergency Veterinary Assistant (Part Time) - Leesburg, VA
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
Given posting includes: ABOUT VEG (company description) – not a job section; we can maybe put under About the role? Actually "About the role" is typical heading for description of role. The posting includes "THE JOB" description: "At VEG, we don't just hire assistants—we grow future emergency rockstars..." That's about the role. So we can put that under About the role
with paragraphs.
Responsibilities: list under "WHAT YOU'LL DO*". Use - .
Requirements: maybe "WHAT YOU NEED". That's requirements. Use
- .
Qualifications: maybe "WHO YOU ARE" (personal attributes). Could be Qualifications or Skills. We'll decide: Qualifications could be education/experience; Skills could be personal traits. But we need to avoid thin sections. Let's see content:
WHAT YOU NEED: includes high school diploma, enrolled in AVMA-accredited program a plus, 1+ years experience, basic computer skills, excellent communicator, fine motor skills, ability to stand, lift, willingness to work nights, etc. That's qualifications/requirements.
WHO YOU ARE: empathetic, humility, ownership, curious. Those are more like Skills/attributes.
We could combine Requirements and Qualifications? But we need headings only if real content. We could have:
- About the role (from THE JOB)
- Responsibilities (WHAT YOU'LL DO)
- Requirements (WHAT YOU NEED)
- Skills (WHO YOU ARE)
- Benefits (HOW WE INVEST IN YOU) includes compensation, learning, travel stipend, flexible schedules, referral program, scrubs, swag, food.
Pay: Not explicitly stated; only mentions competitive compensation but no numbers. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. "Competitive compensation" is vague but it's stating compensation exists. However "competitive compensation" is not a specific number; but it's still stating compensation. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". That's a statement about pay, albeit not specific. Should we include Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive compensation, so we could include Pay with that sentence. However also they say "Prefer a few substantive sections over many thin ones." Might be better to fold compensation into Benefits? But Benefits section already includes many items; we could include compensation there. However they specifically have a Benefits heading; we could put compensation under Benefits. But they also have a separate Pay heading. We need to decide.
Given they said "Competitive compensation" and also travel stipend etc. I'd include a Benefits section that includes compensation, learning, stipend, flexible schedule, referral program, scrubs, swag, food. Pay section maybe not needed if we put compensation in Benefits. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state compensation, we could create Pay section with that line. However they also state flexible work schedules (Schedule). So we could create Schedule section with that line. But they also say "Prefer a few substantive sections over many thin ones." So maybe better to combine compensation and schedule into Benefits? But Benefits already includes flexible work schedules. So we could have Benefits section covering compensation, learning, stipend, flexible schedule, referral program, scrubs, swag, food. Then we don't need separate Pay or Schedule sections.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Check if any other sections like Qualifications: we have Requirements (WHAT YOU NEED) and Skills (WHO YOU ARE). That's fine.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details like "As permitted by state law" etc. Must keep that.
We need to remove boilerplate: ABOUT VEG description? That's company info, not job-specific. Should we include? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The ABOUT VEG is not metadata; it's about company. Could be considered boilerplate? It's not navigation/legal/EEO etc. It's about the company mission. Might be relevant to role? Usually we could include as part of About the role? But they said preserve ALL substantive information; do NOT invent or summarize away detail. The ABOUT VEG is substantive about the company. Should we include it? The instruction about sections: use headings for specific sections; we could include a short paragraph under About the role that includes company mission? But About the role is supposed to be about the role. However we could treat the initial ABOUT VEG as a general description; maybe we can include it as a
before any headings? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid having introductory paragraphs before headings. So we could include a
with the ABOUT VEG content, then headings.
But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ABOUT VEG is not those.
Thus we can start with a
containing the ABOUT VEG text (maybe trimmed). Then headings.
Let's extract ABOUT VEG text:
"ABOUT VEG 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®."
We need to preserve all that. Might be long but okay.
Now THE JOB section: "THE JOB At VEG, we don't just hire assistants—we grow future emergency rockstars. As a part-time Emergency Veterinary Assistant, you'll be in the heart of the action from day one, supporting your team, comforting pet parents, and learning the ropes in real time. You'll be there for everything—the triage, the treatments, and the tail wags. You're embarking on a path where careers start, grow, and thrive. Whether you're on your way to becoming a credentialed technician or exploring where your passion can take you, we'll say yes to your growth every step of the way."
We'll put that under
About the role
as paragraphs.
Now WHAT YOU'DO* list:
- Be the first warm welcome and a steady support, triaging incoming patients and helping guide them toward care
- Assist with treatments, nursing care, and diagnostics, from bloodwork and imaging to catheter placement and oxygen support
- Work alongside our credentialed veterinary technicians and veterinarians to set up and monitor anesthesia and sedation cases
- Set up and manage IV fluids, blood transfusions, and medication administration
- Assist during every moment of care: outpatient or inpatient, exam room to treatment area.
- Join patient rounds and stay close to the clinical picture to ensure continuity of care.
- Learn how to perform CPR and become a RECOVER Certified Rescuer (training provided!)
- Grow into more advanced responsibilities, such as anesthesia support, ultrasound, and catheterization through guided training pathways
- As permitted by state law
Note the last bullet: "As permitted by state law". Keep it.
Now WHAT YOU NEED:
- High school diploma or equivalent required
- Enrolled in an AVMA-accredited veterinary technology program a plus
- 1+ years in a veterinary assistant role (emergency or specialty experience is a bonus!)
- Basic computer skills and an understanding of practice management software and electronic medical record keeping
- Excellent communicator when collaborating with pet parents and your team
- Fine motor skills for handling patients and medical equipment
- 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
- Availability to work nights, weekends, and holidays on a rotating or as needed basis based on hospital needs
- Work well in a fast-paced environment with people from all backgrounds and different personality types
Now WHO YOU ARE:
- Empathetic, instinctively taking a people-centric approach, whether supporting your colleagues or making an effort to understand different perspectives
- Have a sense of humility; acknowledging mistakes, sharing credit with others, and lifting up your team's' accomplishments (note typo team's' but keep)
- Feel a strong sense of ownership over your work, taking responsibility for outcomes and staying committed to achieving long-term, impactful results
- Curious by nature; you ask insightful questions and continuously seek out opportunities to learn and grow your skills and knowledge
Now HOW WE INVEST IN YOU:
- Competitive compensation
- A BIG focus on learning and growth from VEG-created clinical and leadership programs to Unlimited ER CE + travel stipend (No really!).
- Part-time credentialed VEGgies receive a $1,000/year travel stipend.
- Part-time uncredentialed VEGgies receive a $400/year travel stipend.
- Flexible work schedules to support your life outside of work
- Generous employee referral program, so our awesome people can bring in more awesome people
- And the little (big) things, like comfy scrubs, cool VEG swag, and food in the fridge for when you're hungry
We need to preserve the parentheses and exclamation.
Now DEI section: It's about diversity, equity, inclusion. Should we include? It's substantive. Could be a section but we don't have a heading for DEI; we could maybe put under Benefits? But it's not benefits. Could be own section but we don't have a predefined heading; we could add a DEI
but not in allowed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings; but we could also use other headings if needed? The examples are just examples; but they say "use for section headings (e.g. ...)" meaning we should use h3 for any section headings. It's okay to use other headings like DEI. However they also say "Pre
- .
Qualifications: maybe "WHO YOU ARE" (personal attributes). Could be Qualifications or Skills. We'll decide: Qualifications could be education/experience; Skills could be personal traits. But we need to avoid thin sections. Let's see content:
WHAT YOU NEED: includes high school diploma, enrolled in AVMA-accredited program a plus, 1+ years experience, basic computer skills, excellent communicator, fine motor skills, ability to stand, lift, willingness to work nights, etc. That's qualifications/requirements.
WHO YOU ARE: empathetic, humility, ownership, curious. Those are more like Skills/attributes.
We could combine Requirements and Qualifications? But we need headings only if real content. We could have:
- About the role (from THE JOB)
- Responsibilities (WHAT YOU'LL DO)
- Requirements (WHAT YOU NEED)
- Skills (WHO YOU ARE)
- Benefits (HOW WE INVEST IN YOU) includes compensation, learning, travel stipend, flexible schedules, referral program, scrubs, swag, food.
Pay: Not explicitly stated; only mentions competitive compensation but no numbers. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. "Competitive compensation" is vague but it's stating compensation exists. However "competitive compensation" is not a specific number; but it's still stating compensation. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". That's a statement about pay, albeit not specific. Should we include Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive compensation, so we could include Pay with that sentence. However also they say "Prefer a few substantive sections over many thin ones." Might be better to fold compensation into Benefits? But Benefits section already includes many items; we could include compensation there. However they specifically have a Benefits heading; we could put compensation under Benefits. But they also have a separate Pay heading. We need to decide.
Given they said "Competitive compensation" and also travel stipend etc. I'd include a Benefits section that includes compensation, learning, stipend, flexible schedule, referral program, scrubs, swag, food. Pay section maybe not needed if we put compensation in Benefits. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state compensation, we could create Pay section with that line. However they also state flexible work schedules (Schedule). So we could create Schedule section with that line. But they also say "Prefer a few substantive sections over many thin ones." So maybe better to combine compensation and schedule into Benefits? But Benefits already includes flexible work schedules. So we could have Benefits section covering compensation, learning, stipend, flexible schedule, referral program, scrubs, swag, food. Then we don't need separate Pay or Schedule sections.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Check if any other sections like Qualifications: we have Requirements (WHAT YOU NEED) and Skills (WHO YOU ARE). That's fine.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details like "As permitted by state law" etc. Must keep that.
We need to remove boilerplate: ABOUT VEG description? That's company info, not job-specific. Should we include? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The ABOUT VEG is not metadata; it's about company. Could be considered boilerplate? It's not navigation/legal/EEO etc. It's about the company mission. Might be relevant to role? Usually we could include as part of About the role? But they said preserve ALL substantive information; do NOT invent or summarize away detail. The ABOUT VEG is substantive about the company. Should we include it? The instruction about sections: use headings for specific sections; we could include a short paragraph under About the role that includes company mission? But About the role is supposed to be about the role. However we could treat the initial ABOUT VEG as a general description; maybe we can include it as a
before any headings? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid having introductory paragraphs before headings. So we could include a
with the ABOUT VEG content, then headings. But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ABOUT VEG is not those. Thus we can start with a
containing the ABOUT VEG text (maybe trimmed). Then headings. Let's extract ABOUT VEG text: "ABOUT VEG 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®." We need to preserve all that. Might be long but okay. Now THE JOB section: "THE JOB At VEG, we don't just hire assistants—we grow future emergency rockstars. As a part-time Emergency Veterinary Assistant, you'll be in the heart of the action from day one, supporting your team, comforting pet parents, and learning the ropes in real time. You'll be there for everything—the triage, the treatments, and the tail wags. You're embarking on a path where careers start, grow, and thrive. Whether you're on your way to becoming a credentialed technician or exploring where your passion can take you, we'll say yes to your growth every step of the way." We'll put that under
About the role
as paragraphs. Now WHAT YOU'DO* list: - Be the first warm welcome and a steady support, triaging incoming patients and helping guide them toward care - Assist with treatments, nursing care, and diagnostics, from bloodwork and imaging to catheter placement and oxygen support - Work alongside our credentialed veterinary technicians and veterinarians to set up and monitor anesthesia and sedation cases - Set up and manage IV fluids, blood transfusions, and medication administration - Assist during every moment of care: outpatient or inpatient, exam room to treatment area. - Join patient rounds and stay close to the clinical picture to ensure continuity of care. - Learn how to perform CPR and become a RECOVER Certified Rescuer (training provided!) - Grow into more advanced responsibilities, such as anesthesia support, ultrasound, and catheterization through guided training pathways - As permitted by state law Note the last bullet: "As permitted by state law". Keep it. Now WHAT YOU NEED: - High school diploma or equivalent required - Enrolled in an AVMA-accredited veterinary technology program a plus - 1+ years in a veterinary assistant role (emergency or specialty experience is a bonus!) - Basic computer skills and an understanding of practice management software and electronic medical record keeping - Excellent communicator when collaborating with pet parents and your team - Fine motor skills for handling patients and medical equipment - 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 - Availability to work nights, weekends, and holidays on a rotating or as needed basis based on hospital needs - Work well in a fast-paced environment with people from all backgrounds and different personality types Now WHO YOU ARE: - Empathetic, instinctively taking a people-centric approach, whether supporting your colleagues or making an effort to understand different perspectives - Have a sense of humility; acknowledging mistakes, sharing credit with others, and lifting up your team's' accomplishments (note typo team's' but keep) - Feel a strong sense of ownership over your work, taking responsibility for outcomes and staying committed to achieving long-term, impactful results - Curious by nature; you ask insightful questions and continuously seek out opportunities to learn and grow your skills and knowledge Now HOW WE INVEST IN YOU: - Competitive compensation - A BIG focus on learning and growth from VEG-created clinical and leadership programs to Unlimited ER CE + travel stipend (No really!). - Part-time credentialed VEGgies receive a $1,000/year travel stipend. - Part-time uncredentialed VEGgies receive a $400/year travel stipend. - Flexible work schedules to support your life outside of work - Generous employee referral program, so our awesome people can bring in more awesome people - And the little (big) things, like comfy scrubs, cool VEG swag, and food in the fridge for when you're hungry We need to preserve the parentheses and exclamation. Now DEI section: It's about diversity, equity, inclusion. Should we include? It's substantive. Could be a section but we don't have a heading for DEI; we could maybe put under Benefits? But it's not benefits. Could be own section but we don't have a predefined heading; we could add aDEI
but not in allowed list? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings; but we could also use other headings if needed? The examples are just examples; but they say "use
for section headings (e.g. ...)" meaning we should use h3 for any section headings. It's okay to use other headings like DEI. However they also say "Pre