Early Elementary Teacher, Alpha - $100,000/year USD
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting and extract sections.
Key info:
- Salary: $100,000/year salaried, paid weekly, with day-one health, dental, and vision benefits. 40 hours/week, five days a week, on-site at one Alpha campus, with relocation support.
Thus we have Pay, Schedule, Benefits.
- Benefits: health, dental, vision day-one.
- Pay: $100,000/year, weekly.
- Schedule: 40 hours/week, five days a week, on-site.
- Relocation support.
- Role description: many paragraphs.
We need sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real content.
We have content for About the role (intro paragraph about reimagining teacher). Responsibilities (list of duties). Requirements (basic requirements). Qualifications (maybe same as requirements? but we can combine). Skills (nice-to-have). Benefits (health/dental/vision). Pay (salary). Schedule (hours). Also maybe "Location" but not required.
We must not repeat job title heading. So we will not include heading "Early Elementary Teacher". Use headings for sections.
We must not include Job ID / requisition numbers as headings; we can fold minor metadata into short
or drop it. The posting includes "Crossover Job Code: LJ-4849-US-SanAnton-EarlyElementar". That's minor metadata; we can put in a
at end maybe.
We must remove boilerplate like "Working with us This is a full-time, W2 employee position..." but we need to keep substantive info like benefits, pay, schedule. The "Working with us" paragraph includes compensation level and payment period; we already have that. Also includes link to benefits; we can keep mention of immediate access to benefits but not the link? Probably keep the statement but not the URL? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link might be considered navigation? It's a URL; maybe we can drop it. But we need to preserve substantive info: immediate access to benefits, year-long positions, compensation level, payment period. We can keep that in a
under Benefits/Pay sections.
We need to output only HTML fragment.
Let's structure:
About the role
... (intro paragraph about reimagining teacher, quote, etc.)
Responsibilities
- Running short structured-literacy workshops with two to four students — diagnosing a phonics or decoding gap from running records and fluency probes, teaching a sequence you designed for it, and checking that it transferred
- Coaching students through app-based core learning: seeing who has stalled, asking the question that unsticks them, holding the daily goal
- Leading morning launch, life-skills workshops, and check-chart activities that keep six-year-olds moving
- Driving students to their weekly app goals with school currency, leaderboards, and gamification pitched at their age
- Staying with your students through lunch, recess, and closing, meeting refusal and frustration with a plan built for that particular child
Maybe also include "What You Won’t Be Doing" as responsibilities? Could be separate but maybe not needed. But we could include as part of responsibilities? The instruction: use - for any list of duties/requirements/benefits. The "What You Won’t Be Doing" is a list of negatives; could be included but maybe not needed. However we should preserve ALL substantive information. So we should include that list as well. Could be under Responsibilities or a separate section "What you won’t be doing". But we only have predefined headings; we could add a heading "What you won’t be doing" but not in list. The instruction says use headings for sections like 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)." It implies those are examples; we could use other headings if needed. However to be safe, we could incorporate the "What You Won’t Be Doing" as part of Responsibilities (maybe as a sublist). But we need to preserve all substantive info; we can include as a separate under Responsibilities with a preceding maybe.
Better: Under Responsibilities, we can have two lists: "What you will be doing" and "What you won’t be doing". But we need to keep it simple.
Alternatively, we could create a section "What you won’t be doing" with heading
What you won’t be doing
. That seems acceptable as it's a section heading. The instruction didn't restrict to only those examples; it gave examples. So we can add.
Similarly, we have "Early Elementary Teacher Key Responsibilities" and "Basic Requirements", "Nice-to-have Requirements". We can map those to Requirements and Qualifications and Skills.
Let's extract:
Basic Requirements:
- Willing to work on-site at one of the campuses listed above, with relocation support
- At least 3 years working directly with children ages 4-9: teaching, coaching, tutoring, camps, youth programs, children's theater, or similar settings where kids showed up because of you
- At least 2 years of that experience teaching reading in grades K-3, within the last 5 years
- Completed structured-literacy training: LETRS, IMSE, Orton-Gillingham, Wilson Reading System, Fundations, UFLI, CERI, Neuhaus, SIPPS, Really Great Reading, or similar; or a master's in reading or literacy
- Bachelor's degree in any subject. A teaching certificate is not required
- Comfortable spending about 90% of your day guiding students through app-based learning, workshops, and campus routines, and 10% on reading sessions
- Willing to work with all K-3 students, not only struggling readers
- Legally authorized to work in the US without visa sponsorship
Nice-to-have Requirements:
- You can keep a room of six-year-olds engaged with nothing but your energy and a good activity
- Tired children kept coming back to your after-school or summer program
- Experience with reading platforms (Amira, Lexia, i-Ready) or diagnostic assessments (DRA, DIBELS, AIMSweb)
- You can name a specific child whose decoding you fixed, and say how you did it
- You have worked in a non-traditional school model: charter, micro-school, Montessori, or hybrid
We could put Basic Requirements under "Requirements" heading, Nice-to-have under "Skills" heading, and maybe "Qualifications" could be combined with Requirements? But we need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one section "Requirements". But we have both Basic and Nice-to-have; we could split into Requirements (basic) and Skills (nice-to-have). Qualifications maybe not needed separately.
We also have "Early Elementary Teacher Key Responsibilities" which is a short sentence: "Get every K-3 student to their daily learning goals, and close the reading gaps that keep them from getting there on their own." That could be part of Responsibilities.
We also have "Role We recruit nationally..." etc. That's about location and applying; we can maybe put under "About the role" or a separate "Location" but not needed.
We have "Current openings: AZ - Phoenix and Scottsdale TX - Dallas, Fort Worth (Keller), Plano, and The Woodlands UT - Park City (Salt Lake City)". That's location info; we could include under About the role or a separate "Location" section. But we might not need a separate heading; we can include in About the role paragraph.
We also have "Interested in a different Alpha campus? Apply anyway, name your preferred location, and we will route you to the right opening." That's application instruction; we should remove application instructions per instruction. So we drop that.
We also have "Hit the Apply button if you found this interesting and want to learn more." That's application instruction; drop.
We also have "We look forward to meeting you!" drop.
We also have "Working with us This is a full-time, W2 employee position with immediate access to benefits (link). All roles are year-long positions. The compensation level for this role is $100,000 USD/year. The payment period is weekly. Consult www.crossover.com/help-and-faqs for more details on this topic. Crossover Job Code: LJ-4849-US-SanAnton-EarlyElementar". We need to keep compensation and payment period and benefits info; we can drop the link and job code maybe as minor metadata in a short . The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
at end with "Crossover Job Code: LJ-4849-US-SanAnton-EarlyElementar". Or we could drop it entirely; but it's minor metadata, we can drop. Safer to drop.
We need to keep "immediate access to benefits" maybe under Benefits.
We need to keep "All roles are year-long positions." That's maybe not needed for sections but could be under About the role.
Now, let's craft HTML.
We'll have sections:
About the role
... (intro paragraph including quote, description of Alpha, reimagining teacher, etc.)
Responsibilities
Key responsibility: Get every K-3 student to their daily learning goals, and close the reading gaps that keep them from getting there on their own.
- Running short structured-literacy workshops with two to four students — diagnosing a phonics or decoding gap from running records and fluency probes, teaching a sequence you designed for it, and checking that it transferred
- Coaching students through app-based core learning: seeing who has stalled, asking the question that unsticks them, holding the daily goal
- Leading morning launch, life-skills workshops, and check-chart activities that keep six-year-olds moving
- Driving students to their weekly app goals with school currency, leaderboards, and gamification pitched at their age
- Staying with your students through lunch, recess, and closing, meeting refusal and frustration with a plan built for that particular child
What
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. Key info: - Salary: $100,000/year salaried, paid weekly, with day-one health, dental, and vision benefits. 40 hours/week, five days a week, on-site at one Alpha campus, with relocation support. Thus we have Pay, Schedule, Benefits. - Benefits: health, dental, vision day-one. - Pay: $100,000/year, weekly. - Schedule: 40 hours/week, five days a week, on-site. - Relocation support. - Role description: many paragraphs. We need sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real content. We have content for About the role (intro paragraph about reimagining teacher). Responsibilities (list of duties). Requirements (basic requirements). Qualifications (maybe same as requirements? but we can combine). Skills (nice-to-have). Benefits (health/dental/vision). Pay (salary). Schedule (hours). Also maybe "Location" but not required. We must not repeat job title heading. So we will not include heading "Early Elementary Teacher". Use headings for sections. We must not include Job ID / requisition numbers as headings; we can fold minor metadata into short
or drop it. The posting includes "Crossover Job Code: LJ-4849-US-SanAnton-EarlyElementar". That's minor metadata; we can put in a
at end maybe. We must remove boilerplate like "Working with us This is a full-time, W2 employee position..." but we need to keep substantive info like benefits, pay, schedule. The "Working with us" paragraph includes compensation level and payment period; we already have that. Also includes link to benefits; we can keep mention of immediate access to benefits but not the link? Probably keep the statement but not the URL? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link might be considered navigation? It's a URL; maybe we can drop it. But we need to preserve substantive info: immediate access to benefits, year-long positions, compensation level, payment period. We can keep that in a
under Benefits/Pay sections. We need to output only HTML fragment. Let's structure:
About the role
... (intro paragraph about reimagining teacher, quote, etc.)
Responsibilities
- Running short structured-literacy workshops with two to four students — diagnosing a phonics or decoding gap from running records and fluency probes, teaching a sequence you designed for it, and checking that it transferred
- Coaching students through app-based core learning: seeing who has stalled, asking the question that unsticks them, holding the daily goal
- Leading morning launch, life-skills workshops, and check-chart activities that keep six-year-olds moving
- Driving students to their weekly app goals with school currency, leaderboards, and gamification pitched at their age
- Staying with your students through lunch, recess, and closing, meeting refusal and frustration with a plan built for that particular child
- for any list of duties/requirements/benefits. The "What You Won’t Be Doing" is a list of negatives; could be included but maybe not needed. However we should preserve ALL substantive information. So we should include that list as well. Could be under Responsibilities or a separate section "What you won’t be doing". But we only have predefined headings; we could add a heading "What you won’t be doing" but not in list. The instruction says use headings for sections like 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)." It implies those are examples; we could use other headings if needed. However to be safe, we could incorporate the "What You Won’t Be Doing" as part of Responsibilities (maybe as a sublist). But we need to preserve all substantive info; we can include as a separate
- under Responsibilities with a preceding
- Running short structured-literacy workshops with two to four students — diagnosing a phonics or decoding gap from running records and fluency probes, teaching a sequence you designed for it, and checking that it transferred
- Coaching students through app-based core learning: seeing who has stalled, asking the question that unsticks them, holding the daily goal
- Leading morning launch, life-skills workshops, and check-chart activities that keep six-year-olds moving
- Driving students to their weekly app goals with school currency, leaderboards, and gamification pitched at their age
- Staying with your students through lunch, recess, and closing, meeting refusal and frustration with a plan built for that particular child
maybe. Better: Under Responsibilities, we can have two lists: "What you will be doing" and "What you won’t be doing". But we need to keep it simple. Alternatively, we could create a section "What you won’t be doing" with heading
What you won’t be doing
. That seems acceptable as it's a section heading. The instruction didn't restrict to only those examples; it gave examples. So we can add. Similarly, we have "Early Elementary Teacher Key Responsibilities" and "Basic Requirements", "Nice-to-have Requirements". We can map those to Requirements and Qualifications and Skills. Let's extract: Basic Requirements: - Willing to work on-site at one of the campuses listed above, with relocation support - At least 3 years working directly with children ages 4-9: teaching, coaching, tutoring, camps, youth programs, children's theater, or similar settings where kids showed up because of you - At least 2 years of that experience teaching reading in grades K-3, within the last 5 years - Completed structured-literacy training: LETRS, IMSE, Orton-Gillingham, Wilson Reading System, Fundations, UFLI, CERI, Neuhaus, SIPPS, Really Great Reading, or similar; or a master's in reading or literacy - Bachelor's degree in any subject. A teaching certificate is not required - Comfortable spending about 90% of your day guiding students through app-based learning, workshops, and campus routines, and 10% on reading sessions - Willing to work with all K-3 students, not only struggling readers - Legally authorized to work in the US without visa sponsorship Nice-to-have Requirements: - You can keep a room of six-year-olds engaged with nothing but your energy and a good activity - Tired children kept coming back to your after-school or summer program - Experience with reading platforms (Amira, Lexia, i-Ready) or diagnostic assessments (DRA, DIBELS, AIMSweb) - You can name a specific child whose decoding you fixed, and say how you did it - You have worked in a non-traditional school model: charter, micro-school, Montessori, or hybrid We could put Basic Requirements under "Requirements" heading, Nice-to-have under "Skills" heading, and maybe "Qualifications" could be combined with Requirements? But we need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one section "Requirements". But we have both Basic and Nice-to-have; we could split into Requirements (basic) and Skills (nice-to-have). Qualifications maybe not needed separately. We also have "Early Elementary Teacher Key Responsibilities" which is a short sentence: "Get every K-3 student to their daily learning goals, and close the reading gaps that keep them from getting there on their own." That could be part of Responsibilities. We also have "Role We recruit nationally..." etc. That's about location and applying; we can maybe put under "About the role" or a separate "Location" but not needed. We have "Current openings: AZ - Phoenix and Scottsdale TX - Dallas, Fort Worth (Keller), Plano, and The Woodlands UT - Park City (Salt Lake City)". That's location info; we could include under About the role or a separate "Location" section. But we might not need a separate heading; we can include in About the role paragraph. We also have "Interested in a different Alpha campus? Apply anyway, name your preferred location, and we will route you to the right opening." That's application instruction; we should remove application instructions per instruction. So we drop that. We also have "Hit the Apply button if you found this interesting and want to learn more." That's application instruction; drop. We also have "We look forward to meeting you!" drop. We also have "Working with us This is a full-time, W2 employee position with immediate access to benefits (link). All roles are year-long positions. The compensation level for this role is $100,000 USD/year. The payment period is weekly. Consult www.crossover.com/help-and-faqs for more details on this topic. Crossover Job Code: LJ-4849-US-SanAnton-EarlyElementar". We need to keep compensation and payment period and benefits info; we can drop the link and job code maybe as minor metadata in a short. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
at end with "Crossover Job Code: LJ-4849-US-SanAnton-EarlyElementar". Or we could drop it entirely; but it's minor metadata, we can drop. Safer to drop. We need to keep "immediate access to benefits" maybe under Benefits. We need to keep "All roles are year-long positions." That's maybe not needed for sections but could be under About the role. Now, let's craft HTML. We'll have sections:
About the role
... (intro paragraph including quote, description of Alpha, reimagining teacher, etc.)
Responsibilities
Key responsibility: Get every K-3 student to their daily learning goals, and close the reading gaps that keep them from getting there on their own.
What