Jobs · Finance · Oregon

Security Associate - 2nd Shift

Carvana · Eugene, OR · 3 wk ago
On-siteFinance$19/hrFull-time
We need to output HTML fragment with sections: Schedule, Pay Range, About Carvana (maybe as About the role?), About The Team And Position, What You’ll Be Doing, Key Metrics, What You Should Know/have, We’ll Offer In Return (Benefits), Other Requirements. Also maybe include "Pay" and "Benefits" sections. We must not repeat job title. Use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Legal stuff" etc. Also remove "Of course, we’ll make any reasonable accommodations..." maybe keep? It's part of Other Requirements? It's about accommodations; maybe keep as part of Other Requirements? It's not boilerplate? It's a statement about accommodations; could keep but it's not required? It's not EEO boilerplate? It's about accommodations; could keep as part of Other Requirements. But we can keep it. We must not include sections with placeholder text like "commensurate with experience". Not present. We need to include Schedule section: "Schedule (Open Availability Highly Preferred) Mon, Tues 5PM-1:30AM Fri-Sun 7:30PM-4AM". So heading

    Schedule

    then maybe a

    with that text. Pay Range: "Pay Range: $19 hourly". So

    Pay

    then

    Pay Range: $19 hourly

    . About Carvana: The paragraph starting "At Carvana, we believe buying a car the old-fashioned way sucks..." up to "Want the full story? Check it out here." That's about Carvana. Use heading

    About Carvana

    maybe "About the role"? But instructions: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should follow those examples. However we can also use other headings if needed? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. But we can also have other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings for sections. So we need to map content to those headings. We have: - About the role: could be About Carvana + About The Team And Position combined? Or we could split: About the role (overview) and Responsibilities (What You’ll Be Doing). Requirements/Qualifications/Skills (What You Should Know/have). Benefits (What We’ll Offer In Return). Pay (Pay Range). Schedule (Schedule). Also maybe Key Metrics could be under Responsibilities or a separate section? Not in list; maybe we can include under Responsibilities as a list. We must not create sections without real content. So we need to decide which headings to include. We have content for: - About the role: maybe a brief description of the role (the team and position). Could use "About the role" heading with paragraph about Safe & Secure team. - Responsibilities: list of duties (What You’ll Be Doing). Could also include Key Metrics as part of responsibilities? Might be separate but we can include as a list under Responsibilities. - Requirements: maybe "What You Should Know/have" (the bullet list). Could be Requirements. - Qualifications: maybe "Other Requirements" (the basic requirements). Could be Qualifications. - Skills: maybe the bullet list of "We’d love it if you also have" (preferred skills). Could be Skills. - Benefits: "What We’ll Offer In Return" (benefits list). Could be Benefits. - Pay: Pay Range. - Schedule: Schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Use

    for each. We must use
    • for any list of duties/requirements/benefits. So for Responsibilities (list of duties), Requirements (list of needed experience), Qualifications (list of basic requirements?), Skills (list of preferred), Benefits (list of offerings). We need to decide which items go where. Let's extract content: About Carvana paragraph: "At Carvana, we believe buying a car the old-fashioned way sucks — so we're rewriting the playbook. Yes, we're the vending machine people. Yes, we built that on purpose. And yes, we're just getting started. We're looking for people who want to thrive in an environment of impactful change. Team spirit shows up in everything we do — every day, our passion and creativity drive the kind of innovation that moves an industry. We take big swings, set ambitious goals, and challenge each other to make data- and process-driven decisions in everything we do. Here are a few of our stories. We've been changing the game since 2013, and we're not letting up. Want the full story? Check it out here." About The Team And Position: "Our Safe & Secure team is the heartbeat of every Carvana location. You're the people we trust to protect our associates, our customers, and the thousands of vehicles that flow through our gates every day. Rain, shine, ice, or 110° heat — the mission doesn't change, and neither does the standard. This is a boots-on-the-ground role. We bring the strategy; you bring the hustle. From clearing snow during a winter storm to running heat-safety protocols in July, you'll be the reason our site stays open, safe, and moving. Some days you'll be at the gate — the literal face of Carvana to every associate, vendor, and visitor walking through it. Other days, you'll be out on the lot scanning vehicles, knocking out safety audits, or restocking the supplies that keep this place humming. You won't just monitor a perimeter — you'll own it. That means spotting hazards before they become incidents, building real relationships with the folks on site, and stepping up when something needs your attention. You'll be trained and trusted to act in emergencies, partner with our Inspection Center and Logistics teams, and feed sharp, accurate intel back to your Safe & Secure leadership. Hourly position, reporting to your Safe & Secure Functional Lead or Manager." What You’ll Be Doing: list of duties (starting with "Lead with a service-first mindset..." etc). That's a long list. Key Metrics: list: "Unit Loss Rate versus Plan, Safe & Secure App Execution, Inventory Control/Accuracy and Tracking, Safety Incident Performance". Could be part of Responsibilities. What You Should Know/have: bullet list starting with "1–2 years in a customer service environment" etc. We’d love it if you also have: list of preferred skills. What We’ll Offer In Return: list of benefits. Other Requirements: list of basic requirements (must be able to read/write/speak English, at least 18, safety-sensitive, lift 60 lbs, etc). Also includes accommodation statement. We need to avoid legal boilerplate: remove "Legal stuff" etc. Also remove EEO statement etc. Also remove "Of course, we’ll make any reasonable accommodations..." maybe keep as part of Other Requirements? It's not boilerplate; it's about accommodations. Could keep. We must not include duplicated lines. Now craft HTML. We'll have:

      About the role

      Combine About Carvana and About The Team And Position? Might be too long but okay. Could split: About Carvana as About the role, and About The Team And Position as maybe part of Responsibilities? But Better to put About Carvana as About the role, and About The Team And Position as part of Responsibilities? Actually responsibilities are duties. The team description is more about role context. Could include in About the role. Thus About the role paragraph: combine both paragraphs. Then Responsibilities: list of duties from What You’ll Be Doing plus Key Metrics maybe as separate bullet items. We need to use

      • for list. Thus:

        Responsibilities

        • Lead with a service-first mindset in every interaction.
        • Live the Carvana values — and make sure they're felt by everyone you work with.
        • Be the face of Carvana at the gate for associates, vendors, and visitors.
        • Communicate like a pro — clear, calm, active listener, no missed signals.
        • Use our Unified Security Platform to monitor live cameras, review footage, and investigate intrusion alerts so nothing on site catches us off guard.
        • When things get hot, keep it cool. De-escalate, win with partners, and remember — we're all in this together.
        • Run point at the gate using the Safe & Secure App (SAS App) and RFID tech, enforcing ingress/egress procedures every single time.
        • Manage and document vehicle movement through the Inspection Center entrance and exit gates.
        • Show up when the team needs you. You'll be trained and certified in first aid, CPR, and AED — and we expect you to use it when the moment calls for it.
        • Know our emergency protocols cold so you can act decisively when seconds count.
        • Keep the site operational in any weather — snow removal in winter, heat-safety protocols in summer, no excuses, no shortcuts.
        • Drive a safety-first culture by spotting environmental hazards, running safety audits, and reinforcing best practices with the people around you.
        • Scan thousands of vehicles a day to keep operational flow tight — between mobile rover tech and manual handheld scans, every car gets accounted for.
        • Cover ground. This role involves serious walking to reach restricted or hard-to-access areas of the lot.
        • Run vehicle location research and deliver clean, detailed reports to leadership when operational questions come up.
        • Key Metrics: Unit Loss Rate versus Plan, Safe & Secure App Execution, Inventory Control/Accuracy and Tracking, Safety Incident Performance.
        But note: The last bullet includes "Key Metrics:" maybe we should separate? Could be its own bullet. Now Requirements: maybe the "What You Should Know/have" list.

        Requirements

        • 1–2 years in a customer service environment
        • Strong verbal and written communication
        • A track record of solid decision-making in a complex, fast-moving environment
        • Ability to build strong working relationships and connect with people quickly
        • Ability to organize, plan, and execute multiple tasks at once in a fast-paced setting
        • Ability to handle conflict in a positive, productive way
        Skills: the "We’d love it if you also have" list.

        Skills

        • Familiarity with CCTV, RFID, Card Access, or other Safe & Secure technology
        • Previous experience supporting an OSHA / Safety Team program
        • Experience with crisis prevention and/or response plans
        Qualifications: the "Other Requirements" list (basic requirements). Might be better as Qualifications.

        Qualifications

        • Must be able to read, write, speak, and understand English
        • Must be at least 18 years of age
        • This position is designated as a

Similar jobs