Jobs · Finance · Ohio

Winter Security Associate

Carvana · Heath, OH · 1 mo ago
On-siteFinance$17/hrFull-time
We need to output only HTML fragment, using

for section headings,
  • for lists,

    for prose. No job title heading, no Job ID. Include sections only when posting has real specific content. We need to extract sections: About Carvana (maybe "About Carvana" heading), About The Team And Position (maybe "About the team and position" but we can use heading "About the team and position" or "About the team". The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings where appropriate. We have: - Schedule (Open Availability Highly Preferred): Must have open availability to work any shift - Pay Range: $17 hourly - About Carvana (paragraph) - About The Team And Position (long description) - What You’ll Be Doing (list of duties) - Key Metrics (list) - What You Should Know/have (list of qualifications) - We’d love it if you also have (additional nice-to-have) - What We’ll Offer In Return (benefits etc.) - Other Requirements (list of requirements) - Legal stuff (EEO etc.) - we should remove boilerplate EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the legal stuff (EEO statement, background check, visa sponsorship, etc.) as boilerplate. We need to preserve all substantive information, not invent or summarize away detail. Remove duplicated lines. We need to decide which sections to include: About Carvana (maybe "About the role"? Actually "About Carvana" is about company, could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - Schedule: we have schedule info: open availability. So

    Schedule

    with

    Must have open availability to work any shift

    - Pay: Pay Range: $17 hourly. So

    Pay

    with

    $17 hourly

    - About Carvana: Could be "About the role"? But maybe better to use "About the role" heading for description of role and team. However we have separate "About The Team And Position". That could be "About the role". We'll use

    About the role

    for that section. - Responsibilities: "What You’ll Be Doing" list. So

    Responsibilities

    with
    • ... each bullet. - Requirements: "What You Should Know/have" list (mandatory). Also "Other Requirements" list (physical requirements). Could combine? But we need to avoid thin sections. Could have "Requirements" covering both mandatory qualifications and other requirements. But we also have "Qualifications" maybe for nice-to-have? The instruction: use headings like Qualifications, Skills, Benefits. We can decide: - Qualifications: maybe "What You Should Know/have" (mandatory). Could be "Qualifications". - Skills: maybe "We’d love it if you also have" (nice-to-have). Could be "Skills". - Benefits: "What We’ll Offer In Return". So

      Benefits

      . We also have "Key Metrics" maybe not a standard heading; could be omitted or placed under Responsibilities? It's about performance metrics. Could be its own section but not in list. The instruction: prefer a few substantive sections over many thin ones. Could combine Key Metrics under Responsibilities? But they are metrics, not duties. Could create a section "Performance Metrics" but not in allowed headings. Might be better to omit? But we must preserve ALL substantive information. So we need to include it somewhere. Could add a heading "Key Metrics" but not in allowed list; but 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 exclusive? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should map content to those headings. Key Metrics could be placed under Responsibilities as a sub-list? But we must not invent headings. Could add a

      under Responsibilities summarizing metrics? But we must preserve all detail, not summarize away. Could list them as

        under a

        Responsibilities

        but that would mix duties with metrics. Might be okay but could be considered mixing. However we could create a separate section "Key Metrics" but that deviates from allowed headings. The instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we can use other headings if needed, but they gave examples. Safer to stick to those headings. But we need to include Key Metrics somewhere. Could put under "Responsibilities" as a subheading? Not allowed to use

        . Could embed as a

        with list. That would preserve detail. Similarly "Other Requirements" could go under "Requirements". "What You Should Know/have" also under Requirements? But we have separate nice-to-have. We could structure: - About the role (combines About Carvana and About The Team And Position) - Responsibilities (What You’ll Be Doing + Key Metrics) - Requirements (What You Should Know/have + Other Requirements) - Skills (We’d love it if you also have) - Benefits (What We’ll Offer In Return) - Pay - Schedule We must not repeat job title heading. No Job ID. We must remove boilerplate legal stuff. Now craft HTML. We need to ensure we use

        • for any list of duties/requirements/benefits. For prose use

          . We'll produce something like:

          About the role

          About Carvana ...

          About The Team And Position ...

          But we have two paragraphs; could combine into one

          with both? Better to keep separate

          elements. Then Responsibilities: list of duties from "What You’ll Be Doing" plus Key Metrics as separate items? Could separate with a heading inside? Not allowed. Could just list all items together. We'll extract each bullet from "What You’ll Be Doing". Then also add Key Metrics bullets. We need to preserve all detail exactly as in posting, but we can rephrase? Must not invent or summarize away detail. We can copy the text as is. Let's extract the duties list: - 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. - When winter hits, this becomes your priority: be the first back on site in extreme or harsh conditions to assess the lot and get it safe and operational for the team. - Execute snow and ice removal — plowing, shoveling, salting, and brining entry paths, employee lots, load/unload zones, gates, and the tight rows between parked vehicles where plows can't reach. - Run salt-bin execution at Inspection Center doors, and pre-treat and re-treat danger zones — including day-2 refreeze mornings. - Provide extended winter support in the 7–10 days after a storm as melt and refreeze continue, not just during the event itself. - Operate winter equipment safely — snow plow, and with training, trucks with plow and salt-spreader attachments, skid steers, and loaders — always working in your ice cleats. Now Key Metrics bullets: - Unit Loss Rate versus Plan - Safe & Secure App Execution - Inventory Control/Accuracy and Tracking - Safety Incident Performance - Snow and ice removal execution and timeliness; salt, brine, and cleat protocol compliance We'll include these as list items under Responsibilities. Now Requirements: combine "What You Should Know/have" and "Other Requirements". What You Should Know/have list: - 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 - Able and willing to report to work and perform in extreme cold, snow, and ice — often as the first person on site - Open availability and schedule flexibility for storms, overnights, weekends, and extended post-storm support - Ability to safely operate a snow plow and perform physical snow and ice removal - Focused, aware, alert, adaptable, and safety-first - Valid driver's license; MVR check required for multiple-lot sites or roles that require driving between lots; no CDL required Other Requirements list: - Must be able to read, write, speak, and understand English - Must be at least 18 years of age - This position is designated as a safety-sensitive position - Must be able to lift up to 60 pounds independently; the majority of lifting from knee to shoulder heights; other lifting required from various levels - Must be able to carry and transport up to 60 pounds up to 20 feet - Requires standing for extended periods of time with frequent stretching, reaching, walking, stooping, pushing, pulling, and snow and ice removal in an environment that may be cold, hot, noisy, wet, snowy, and icy, and may have fumes or odors due to vehicle maintenance - Requires excellent visual acuity and manual dexterity - Requires use of safety equipment that may include, but is not limited to, ice cleats, cold-weather protective gear, face shield or goggles, non-slip shoes, gloves, mask, and other protective garments and equipment - Requires frequent driving and computer data entry - Must adhere to regular and predictable attendance - The facility is a 24/7 operation, and gates must be manned at all times - Of course,

Similar jobs