Emergency Credentialed Veterinary Technician - Hoboken, NJ

We need to output HTML fragment with sections: About the role? Actually we have sections: ABOUT VEG (company description), THE JOB (role description), WHAT YOU'LL DO (responsibilities), WHAT YOU NEED (requirements), WHO YOU ARE (qualities/skills?), HOW WE INVEST IN YOU (benefits/pay), DEI (maybe not needed unless specific content). We must not repeat job title as heading. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings appropriately. We should include only sections with real specific content. We have: - About VEG: company overview. Could map to "About the role"? Actually "About the role" is about the job, not company. But we have "THE JOB" which describes role. Could use "About the role" heading for THE JOB content. Or we could use "About VEG" as a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. We should stick to those. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include if posting has real specific content. Let's extract: About the role: THE JOB description: "As an Emergency Credentialed Veterinary Technician, you're part of a team..." That's role description. So we can put that under

About the role

with

. Responsibilities: WHAT YOU'LL DO list. Use

• . Requirements: WHAT YOU NEED list (education, credential, experience, skills, physical). Use
  • . Qualifications: maybe WHO YOU ARE (personal attributes). Could be Qualifications. Use
    • or

      . The instruction says use

      • for any list of duties/requirements/benefits, and

        for prose. WHO YOU ARE is a list of traits; could be a list. We'll treat as

        • . Skills: maybe not separate; we could combine with Qualifications. But we could have Skills section if there are specific skills listed (e.g., fine motor skills, ability to stand, lift, etc.) Those are in WHAT YOU NEED. Might be better to put those under Requirements. We'll keep Requirements covering education, credential, experience, skills, physical. Then Qualifications for personal attributes. Benefits: HOW WE INVEST IN YOU includes compensation, 401k match, health benefits, equity eligibility, learning stipend, travel stipend, loan repayment, parental leave, flexible schedules, referral program, scrubs, swag, food. That's benefits. Use
          • . Pay: The posting includes "Competitive compensation, including base and 401K match ($25/hr-$44/hr)". That's pay range. So we need a Pay section with that info. Could be separate

            Pay

            with

            stating the range. Schedule: The posting includes "Availability to work nights, weekends, and holidays on a rotating or as needed basis based on hospital needs". Also maybe flexible work schedules mentioned under benefits. So we can have Schedule section with that info. We must not include headings with filler text. Ensure we have substantive content. We must not include boilerplate like DEI? The DEI section is present; but we could include as a section? Not in the list of allowed headings. Could we add a DEI section? The instruction says use

            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, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Safer to stick to those. DEI content could be omitted? But we must preserve ALL substantive information; do not invent or summarize away detail. If we omit DEI, we lose substantive info. However maybe we can incorporate DEI content into About the role or Benefits? It's about company culture; could be part of About the role? But About the role is about the job. Could we add a separate section like "Culture" but not in list? Might be risky. Perhaps we can include DEI as a

            under About the role or Benefits? The instruction says preserve ALL substantive information. So we need to include DEI info somewhere. We could add a

            About the role

            and after that include a

            covering DEI? But that mixes. Better to add a separate section like "Culture" but not in the prescribed list; risk of being considered not following instruction. However the instruction says "Use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can use other headings as long as they are

            . Probably safe to add a DEI section. But we must not create sections with filler text. DEI has substantive content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, DEI (or Culture). We'll use DEI. Now we need to extract content precisely. Let's parse each section. ABOUT VEG: This is company overview. Could be placed under About the role? Actually About the role is about the job; but we have THE JOB separate. Maybe we put ABOUT VEG under About the role? Might be weird. Better to have About the role = THE JOB description. And we could add a brief company overview as a paragraph before that? But instruction says 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 company overview is not minor metadata; it's substantive. Could we put it under About the role as a preamble? Might be okay. Alternatively, we could treat About the role as the combination of ABOUT VEG + THE JOB. But that might be too much. Let's decide: We'll have:

            About the role

            [THE JOB description]

            Then maybe we need a separate section for company overview? Not in list. Could incorporate into Benefits? No. Maybe we can add a section "About VEG" as

            About VEG

            . Not in list but allowed as example? The instruction says use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings. So we can add About VEG. Thus we will have:

            About VEG

            [ABOUT VEG content]

            About the role

            [THE JOB content]

            Then Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, DEI. Now extract content. 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®." We'll keep that as

            . THE JOB: "As an Emergency Credentialed Veterinary Technician, you're part of a team that thrives on the front lines of emergency veterinary care where every second counts. You'll handle a wide range of cases, from minor to complex emergencies, collaborating with our doctors and team in delivering gold standard, emotionally intelligent care. You'll jump into triage, treatments, diagnostics, anesthesia, monitoring, and critical care nursing, all while being a steady, compassionate presence for pet parents in their most stressful moments. This role is for someone who wants to do the work they were trained to do (and more), continue growing their skills, and help people and their pets when they need it most." We'll put that as

            . WHAT YOU'LL DO: list items: - Treat every patient and person like they matter—because they do! You keep people and pets together and stay by their side through tests, treatments, and everything in between - Jump into action, delivering nursing care, treatments, and emotional support in the most critical moments, from triage to discharge - Bring the meds, the monitoring, and the mastery—from IVs and CRIs to blood transfusions and beyond - Communicate like a teammate and think like a leader, helping shape plans and keep care flowing - Be ready to perform CPR like the trained RECOVER rockstar you are (not only do we offer training, we have the highest number of RECOVER CPR professionals and instructors in the industry!) - All the techy stuff—from diagnostics and imaging to sample collection and placing tubes - Anesthesia, even for our most fragile patients? You've got it. - Use all the advanced techniques in your toolkit: central lines, endoscopy, ultrasounds, and more We'll make

            • for each. WHAT YOU NEED: list items: - High school diploma or equivalent required; associate's degree or higher in veterinary technology from an AVMA accredited program strongly preferred - Credentialed as a Veterinary Technician (CVT, RVT, LVT, LVMT) in the state the VEG practice is located is required; VTS in ECC, internal medicine or anesthesia/analgesia is a plus and will lead to extra considerations in compensation - 1+ years of experience in a veterinary technician role; experience in emergency or specialty medicine preferred - Basic computer skills and a comprehension of practice management software and electronic medical record keeping - Excellent communicator and calm under pressure; ready to lend a hand to support those around you - 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 We'll make
              • . WHO YOU ARE: list items: