SPED Non-CDL Driver - IDEA La Joya (Immediate Opening)

We need to output HTML fragment with headings

for sections present: About the role? The description includes "Description Role Mission:" maybe that's about role. There's "What We Offer" with subparts Compensation, Other Benefits. "What You Bring -- Competencies" maybe Qualifications? Actually there is "Qualifications" later. There's "What You’ll Do – Accountabilities". Also "We look for Team and Family who embody the following values and characteristics:" maybe values. Also "About IDEA Public Schools". Also "To Apply" which we must drop (application instructions). Also "Please submit your application online through Jobvite." drop. We need to include sections only when real specific content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. We have: - About the role: maybe "Description Role Mission:" and mission statement. Could be "About the role". Provide mission: Provide safe transportation for SPED and/or RISE students to and from home and campus daily while reducing operational cost. - Responsibilities: "What You’ll Do – Accountabilities" list of duties. - Requirements/Qualifications: There's "Qualifications Education: HS diploma or GED required Experience: Minimal 1 year experience driving a non-CDL vehicle passenger vehicle Must be at least 21 years of age Must be able to work with open calendar Must be able to work on evenings, weekends, holidays, etc. Expected to work a minimum of 32 hours per week – not including extra-curricular activities assigned by campus Must be able to work extended hours when necessary to meet business needs". Also "What You Bring -- Competencies" includes competencies like ability to assist with equipment, participate in ARD/IEP meetings, conduct inspections, report availability. Those could be Skills or Requirements. We'll treat "What You Bring -- Competencies" as Skills. - Benefits: "What We Offer" includes Compensation, Other Benefits. Pay: hourly rate ranging between $15.34 for 0 years of experience and $19.18 (maybe missing per hour?). Also performance bonus based on team performance and goal attainment. Benefits: comprehensive benefits plan covering majority of employee premium for base medical plan, subsidizing majority of costs for spouse/domestic partner and children. Paid Family Leave up to 8 weeks, Tuition Reimbursement up to 50% tuition up to $5,250 max per year, Employer-Paid Mental/Behavioral Health: 5 face-to-face counseling sessions within a year, unlimited 24/7 telephonic counseling, other work-life services at no cost. Other benefits include dental and vision plans, disability, life insurance, parenting benefits, generous vacation time, referral bonuses and professional development. IDEA may offer a relocation allowance to defray cost of moving for this role, if applicable. Thus we have Pay and Benefits sections. Schedule? Not explicitly given besides expected to work minimum 32 hours per week, evenings, weekends, holidays, extended hours when necessary. That could be Schedule. We'll include Schedule section with that info. We also have "About IDEA Public Schools" maybe not needed as a heading? Could be "About the company" but not in list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we need to map content to those headings. "About IDEA Public Schools" maybe not needed; could be omitted or placed under About the role? Probably we can omit as not required heading. But we must preserve ALL substantive information; cannot drop info. However we can embed that info under a heading like About the role? But that heading is for role description, not company. Could we create a section "About the role" and include both mission and company info? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use 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 only. So we need to fit all substantive info under those headings. We can put company info under About the role? Might be okay. Or we could create a separate heading like "About IDEA Public Schools" but that's not in the list; risk of being considered not following instruction. Safer to stick to given headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must decide what goes where. - About the role: mission statement: Provide safe transportation for SPED and/or RISE students to and from home and campus daily while reducing operational cost. Also maybe mention role is to transport students etc. Could also include brief description of role from "Description Role Mission:" plus maybe "What You’ll Do – Accountabilities" but that's responsibilities. - Responsibilities: the list under "What You’ll Do – Accountabilities". We'll output as

• items. - Requirements: maybe the eligibility criteria like age, driver license? Actually "Qualifications" section includes education, experience, age, calendar, schedule. Could be Requirements. - Qualifications: maybe the same as Requirements? But we need both headings; we can split: Requirements: minimal qualifications (education, experience, age, ability to work schedule). Qualifications: maybe additional like ability to assist with equipment, participate in meetings, conduct inspections, report availability. But those are competencies. Hmm. Better: Use Requirements for the hard requirements (education, experience, age, schedule). Use Skills for competencies (assist with equipment, ARD/IEP meetings, inspections, reporting availability, communication, feedback, multitasking, adaptability). Use Qualifications maybe for something else? But we have both Requirements and Qualifications headings; we need to decide. We could treat Requirements as the bullet list under "Qualifications Education: HS diploma or GED required Experience: Minimal 1 year experience driving a non-CDL vehicle passenger vehicle Must be at least 21 years of age Must be able to work with open calendar Must be able to work on evenings, weekends, holidays, etc. Expected to work a minimum of 32 hours per week – not including extra-curricular activities assigned by campus Must be able to work extended hours when necessary to meet business needs". That's requirements. Qualifications could be the "What You Bring -- Competencies" list (assist with equipment, participate in ARD/IEP meetings, conduct inspections, report availability). But those are more like skills/competencies. However we also have Skills heading. Could combine. Maybe we treat: - Requirements: education, experience, age, schedule. - Qualifications: maybe none? But we must include a section only when posting has real specific content for it. If we don't have distinct qualifications beyond requirements, we could omit Qualifications heading. But we have both headings in the list; we are not required to use all. So we can omit Qualifications if no distinct content. - Skills: the competencies list. - Benefits: other benefits (medical, paid leave, tuition reimbursement, mental health, dental/vision, disability, life, parenting, vacation, referral bonuses, professional development, relocation allowance). - Pay: compensation hourly rate range and performance bonus. - Schedule: expected work hours (minimum 32 hours per week, evenings, weekends, holidays, extended hours as needed). Also maybe mention open calendar. But schedule info already in Requirements; we might duplicate. Better to put schedule under Schedule section, and not repeat in Requirements. However Requirements includes schedule; we could move schedule to Schedule and keep Requirements focusing on education, experience, age, ability to work open calendar (maybe still). But open calendar is schedule-related. Let's think. We can define: - Requirements: Education: HS diploma or GED required. Experience: Minimal 1 year experience driving a non-CDL vehicle passenger vehicle. Must be at least 21 years of age. - Schedule: Must be able to work with open calendar, evenings, weekends, holidays, etc. Expected to work a minimum of 32 hours per week – not including extra-curricular activities assigned by campus. Must be able to work extended hours when necessary to meet business needs. - Skills: Competencies list (assist with equipment, participate in ARD/IEP meetings, conduct inspections, report availability, communication, feedback, multitasking, adaptability, etc.) - Benefits: as described. - Pay: compensation and performance bonus. - About the role: mission statement. - Responsibilities: list of duties. We'll omit Qualifications heading. Now we need to ensure we don't include boilerplate like EEO, etc. Already removed. Now produce HTML fragment with

  headings and appropriate

  or

  • . We must not repeat job title as heading. Not include Job ID etc. Let's craft. About the role:

    About the role

    Provide safe transportation for SPED and/or RISE students to and from home and campus daily while reducing operational cost.

    Responsibilities:

    Responsibilities

    • Safely transport students
    • Drives a SPED approved vehicle safely, in accordance with time schedules
    • Transports students to and from their homes, a variety of school sites, and on field trips as assigned
    • Oversees the loading and unloading of students; only releases students to authorized individuals; assures that safety belts are fastened in passenger vans
    • Maintains order and proper discipline of passengers; resolves disputes; documents and reports severe disciplinary cases
    • Follow safety rules and procedures
    • Conducts established safety and operational inspection of assigned vehicle daily
    • Maintains a variety of records and reports including but not limited to mileage, routing, maintenance, and time schedules
    • Notifies appropriate individuals of any delays in scheduled route
    • Maintains and carries proper credentials updated accordingly to DOT and IDEA policy
    • Takes direction and feedback well
    • Has an open communication channel with campus managers
    • Able to accept feedback, both positive and critical
    • Able to self‑reflect on own performance in order to improve continuously
    • Manages multiple tasks by prioritizing work
    • Needs to adapt to changing circumstances while performing various tasks
    • Handles various tasks simultaneously and within established time constraints
    Requirements:

    Requirements

    • Education: HS diploma or GED required
    • Experience: Minimal 1 year experience driving a non‑CDL vehicle passenger vehicle
    • Must be at least 21 years of age
    Schedule:

    Schedule

    • Must be able to work with an open calendar
    • Ability to work evenings, weekends, holidays, etc.
    • Expected to work a minimum of 32 hours per week – not including extra‑curricular activities assigned by campus
    • Must be able to work extended hours when necessary to meet business needs
    Skills:

    Skills

    • Ability to assist the SPED Monitor and students with equipment such as wheelchairs, car seats, child safety restraints, and any other equipment required by the IEP
    • Able to participate in ARD and IEP Meetings with Special Education personnel and Principals
    • Able to conduct pre and post trip vehicle inspections and report any maintenance related issues to SPED Transportation Manager
    • Able to report every morning to your SPED Transportation Manager or Campus Leaders of your availability status