Automotive Technician - A or B+ - Up to $131k
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists of duties/requirements/benefits
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
- 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
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's parse the input:
The input includes:
- Location: Newton, New Jersey
- Schedule: Monday-Saturday (Five-Day Work Week)
- Pay Type: Hourly + Overtime
- Pay Schedule: Weekly
- Pay Rate: A Level: $32-$46/hour / Earning Potential: $66,000-$131,000 annually; B Level: $25-$32/hour / Earning Potential: $52,000-$91,000 annually
- Introduction: paragraph about seeking experienced A-Level and B-Level Automotive Technicians, family-owned shop, high-volume, etc.
- Key Responsibilities: list of duties
- Qualifications: A Level and B Level requirements, ASE certifications preferred, ability to work independently, strong work ethic
- Compensation & Benefits: Compensation details (repeats pay rates), Benefits list
- Why Work Here: list of reasons
- Additional Requirements: paragraph about driver's license, background screening, etc.
We need to structure this into sections. The user says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have:
- Introduction: could be "About the role" or "Overview"
- Key Responsibilities: "Responsibilities"
- Qualifications: "Qualifications" (or "Requirements")
- Compensation & Benefits: includes Pay and Benefits. The posting has specific pay rates and benefits. So we can have "Pay" and "Benefits" sections, or combine into "Compensation & Benefits". The rules say use headings like Pay, Benefits. Since the posting has both, we can create separate sections for Pay and Benefits. However, the Compensation & Benefits section in the posting includes both. We'll split: Pay section with the pay rates, Benefits section with the benefits list.
- Why Work Here: could be "Why Work Here" or "Benefits" but it's more about culture. Could be a separate section "Why Work Here" or "Culture". The rules don't list that as a standard heading, but we can use a custom heading? The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so we can use other headings if needed. But we should prefer standard ones. "Why Work Here" is not standard, but we could include it as a section with heading "Why Work Here". However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but we should keep it consistent. Maybe we can fold "Why Work Here" into "Benefits" or "About the role". But it's a distinct list of reasons. I think we can create a section "Why Work Here" as a heading. But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine "Why Work Here" with "Benefits" or "About the role". However, the benefits list is separate from the "Why Work Here" list. The "Why Work Here" includes things like family-owned shop, high-volume, heated shop, modern equipment, ongoing training, variety of vehicles, team culture, employee events. These are more about the work environment and culture. Could be a section "Work Environment" or "Culture". But the rules don't specify. I'll include it as a separate section with heading "Why Work Here" because it's substantive.
- Additional Requirements: this is about pre-employment screening. Could be "Additional Requirements" or "Pre-Employment Requirements". We'll include as a section.
- Schedule: The posting includes "Schedule: Monday-Saturday (Five-Day Work Week)". That's a schedule. We can have a "Schedule" section.
- Location: Newton, New Jersey. Could be included in a "Location" section or folded into a short
at the top. The rules say "fold minor metadata into a short
or drop it." Location is not minor? It's important. But the page might already show location. The user says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say about location. But we can include location in a short paragraph at the beginning, maybe under "About the role". Or we can have a "Location" heading? Not in the example headings. I'll include location in the introductory paragraph.
- Pay Type and Pay Schedule: included in Pay section.
Now, we must not include boilerplate: the "Additional Requirements" paragraph includes legal language about screening, criminal histories, etc. That might be considered boilerplate? The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This paragraph is legal/EEO boilerplate. It says "Qualified applicants, including those with criminal histories, will be considered in accordance with applicable law." That's EEO boilerplate. Should we remove it? The rules say remove legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove that paragraph. However, the first sentence: "Some positions may require a valid driver's license, motor vehicle record review, background screening, drug or alcohol screening, or other job-related pre-employment requirements based on the duties of the position, the client's lawful requirements, and applicable law." That is specific to the job (driver's license, background screening). That might be substantive. But the rest is legal boilerplate. We could keep the first sentence and drop the rest. But the rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove the entire paragraph if it's boilerplate. However, the first sentence is not boilerplate; it's a requirement. But it's phrased as "Some positions may require...". It's a generic statement. Might be considered boilerplate. I'll keep it as a short paragraph under "Additional Requirements" but remove the legalese. Actually, the user says "Preserve ALL substantive information". The requirement for driver's license and background screening is substantive. The rest is legal boilerplate. I'll include a concise version: "Some positions may require a valid driver's license, motor vehicle record review, background screening, drug or alcohol screening, or other job-related pre-employment requirements." That's substantive. I'll omit the rest.
Also, the "Compensation & Benefits" section repeats pay rates already given at the top. We'll consolidate.
Now, let's structure:
We'll have:
-
About the Role
with introductory paragraph including location, schedule, pay type, pay schedule.
- Responsibilities
with ul of duties.
- Qualifications
with ul of qualifications (A Level, B Level, ASE, etc.)
- Pay
with details for A Level and B Level.
- Benefits
with ul of benefits.
- Why Work Here
with ul of reasons.
- Schedule
with schedule details (Monday-Saturday, five-day work week). Could be included in About the Role, but the rules mention Schedule as a possible heading. Since the posting has a specific schedule, we can include a Schedule section.
- Additional Requirements
with a paragraph about driver's license, background screening.
But note: The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. So we can create them.
We must not include headings with filler. All sections have content.
Now, write HTML.
We'll start with About the Role: include the introduction paragraph, and maybe incorporate location, schedule, pay type, pay schedule into that paragraph or separate. The introduction already says "We are seeking experienced A-Level and B-Level Automotive Technicians to join a respected, family-owned automotive repair and tire shop in Newton, New Jersey. This high-volume facility offers consistent workflow, weekly pay, overtime opportunities, company-paid training, and excellent benefits while servicing a wide variety of domestic, Asian, European, and fleet vehicles." That covers location, weekly pay, overtime, training, benefits. The schedule is Monday-Saturday (Five-Day Work Week). Pay Type: Hourly + Overtime. Pay Schedule: Weekly. We can add a sentence: "The position follows a Monday–Saturday, five-day work week with hourly pay plus overtime, paid weekly." But we should not duplicate. I'll include a short paragraph after the introduction that includes schedule and pay type.
Better: In About the Role, include the introduction paragraph, then a paragraph with schedule and pay type.
Now, Responsibilities: list from Key Responsibilities.
Qualifications: list from Qualifications.
Pay: include the pay rates for A Level and B Level. The posting has "Compensation" section with same numbers. We'll include both hourly and annual earning potential, and typical overtime.
Benefits: list from Benefits.
Why Work Here: list from Why Work Here.
Schedule: maybe just a short paragraph: "Monday–Saturday, five-day work week." But we already mentioned in About the Role. Could be a separate section. The rules say "Schedule" as a possible heading. Since the posting has a specific schedule, we can include a Schedule section with that detail. But it might be thin. The rules say "Prefer a few substantive sections over many thin ones." So maybe fold schedule into About the Role. I'll fold schedule into About the Role and not create a separate Schedule section.
Additional Requirements: include the concise paragraph.
Now, ensure we use - for lists. For Pay, we can use a list or paragraphs. Since there are two levels, we can use a list with two items, each containing details. Or use paragraphs. The rules say use
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but it's a list of pay levels. Could be a list. I'll use a list for Pay.
Similarly, Benefits is a list.
Why Work Here is a list.
Qualifications is a list.
Responsibilities is a list.
Now, write HTML.
We must not include any markdown code fences. Just raw HTML.
Let's craft.
First, About the Role:
About the Role
We are seeking experienced A-Level and B-Level Automotive Technicians to join a respected, family-owned automotive repair and tire shop in Newton, New Jersey. This high-volume facility offers consistent workflow, weekly pay, overtime opportunities, company-paid training, and excellent benefits while servicing a wide variety of domestic
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop - 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 - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's parse the input: The input includes: - Location: Newton, New Jersey - Schedule: Monday-Saturday (Five-Day Work Week) - Pay Type: Hourly + Overtime - Pay Schedule: Weekly - Pay Rate: A Level: $32-$46/hour / Earning Potential: $66,000-$131,000 annually; B Level: $25-$32/hour / Earning Potential: $52,000-$91,000 annually - Introduction: paragraph about seeking experienced A-Level and B-Level Automotive Technicians, family-owned shop, high-volume, etc. - Key Responsibilities: list of duties - Qualifications: A Level and B Level requirements, ASE certifications preferred, ability to work independently, strong work ethic - Compensation & Benefits: Compensation details (repeats pay rates), Benefits list - Why Work Here: list of reasons - Additional Requirements: paragraph about driver's license, background screening, etc. We need to structure this into sections. The user says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have:
- Introduction: could be "About the role" or "Overview"
- Key Responsibilities: "Responsibilities"
- Qualifications: "Qualifications" (or "Requirements")
- Compensation & Benefits: includes Pay and Benefits. The posting has specific pay rates and benefits. So we can have "Pay" and "Benefits" sections, or combine into "Compensation & Benefits". The rules say use headings like Pay, Benefits. Since the posting has both, we can create separate sections for Pay and Benefits. However, the Compensation & Benefits section in the posting includes both. We'll split: Pay section with the pay rates, Benefits section with the benefits list.
- Why Work Here: could be "Why Work Here" or "Benefits" but it's more about culture. Could be a separate section "Why Work Here" or "Culture". The rules don't list that as a standard heading, but we can use a custom heading? The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so we can use other headings if needed. But we should prefer standard ones. "Why Work Here" is not standard, but we could include it as a section with heading "Why Work Here". However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but we should keep it consistent. Maybe we can fold "Why Work Here" into "Benefits" or "About the role". But it's a distinct list of reasons. I think we can create a section "Why Work Here" as a heading. But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine "Why Work Here" with "Benefits" or "About the role". However, the benefits list is separate from the "Why Work Here" list. The "Why Work Here" includes things like family-owned shop, high-volume, heated shop, modern equipment, ongoing training, variety of vehicles, team culture, employee events. These are more about the work environment and culture. Could be a section "Work Environment" or "Culture". But the rules don't specify. I'll include it as a separate section with heading "Why Work Here" because it's substantive.
- Additional Requirements: this is about pre-employment screening. Could be "Additional Requirements" or "Pre-Employment Requirements". We'll include as a section.
- Schedule: The posting includes "Schedule: Monday-Saturday (Five-Day Work Week)". That's a schedule. We can have a "Schedule" section.
- Location: Newton, New Jersey. Could be included in a "Location" section or folded into a short
at the top. The rules say "fold minor metadata into a short
or drop it." Location is not minor? It's important. But the page might already show location. The user says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say about location. But we can include location in a short paragraph at the beginning, maybe under "About the role". Or we can have a "Location" heading? Not in the example headings. I'll include location in the introductory paragraph. - Pay Type and Pay Schedule: included in Pay section. Now, we must not include boilerplate: the "Additional Requirements" paragraph includes legal language about screening, criminal histories, etc. That might be considered boilerplate? The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This paragraph is legal/EEO boilerplate. It says "Qualified applicants, including those with criminal histories, will be considered in accordance with applicable law." That's EEO boilerplate. Should we remove it? The rules say remove legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove that paragraph. However, the first sentence: "Some positions may require a valid driver's license, motor vehicle record review, background screening, drug or alcohol screening, or other job-related pre-employment requirements based on the duties of the position, the client's lawful requirements, and applicable law." That is specific to the job (driver's license, background screening). That might be substantive. But the rest is legal boilerplate. We could keep the first sentence and drop the rest. But the rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove the entire paragraph if it's boilerplate. However, the first sentence is not boilerplate; it's a requirement. But it's phrased as "Some positions may require...". It's a generic statement. Might be considered boilerplate. I'll keep it as a short paragraph under "Additional Requirements" but remove the legalese. Actually, the user says "Preserve ALL substantive information". The requirement for driver's license and background screening is substantive. The rest is legal boilerplate. I'll include a concise version: "Some positions may require a valid driver's license, motor vehicle record review, background screening, drug or alcohol screening, or other job-related pre-employment requirements." That's substantive. I'll omit the rest. Also, the "Compensation & Benefits" section repeats pay rates already given at the top. We'll consolidate. Now, let's structure: We'll have: -
About the Role
with introductory paragraph including location, schedule, pay type, pay schedule. -Responsibilities
with ul of duties. -Qualifications
with ul of qualifications (A Level, B Level, ASE, etc.) -Pay
with details for A Level and B Level. -Benefits
with ul of benefits. -Why Work Here
with ul of reasons. -Schedule
with schedule details (Monday-Saturday, five-day work week). Could be included in About the Role, but the rules mention Schedule as a possible heading. Since the posting has a specific schedule, we can include a Schedule section. -Additional Requirements
with a paragraph about driver's license, background screening. But note: The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. So we can create them. We must not include headings with filler. All sections have content. Now, write HTML. We'll start with About the Role: include the introduction paragraph, and maybe incorporate location, schedule, pay type, pay schedule into that paragraph or separate. The introduction already says "We are seeking experienced A-Level and B-Level Automotive Technicians to join a respected, family-owned automotive repair and tire shop in Newton, New Jersey. This high-volume facility offers consistent workflow, weekly pay, overtime opportunities, company-paid training, and excellent benefits while servicing a wide variety of domestic, Asian, European, and fleet vehicles." That covers location, weekly pay, overtime, training, benefits. The schedule is Monday-Saturday (Five-Day Work Week). Pay Type: Hourly + Overtime. Pay Schedule: Weekly. We can add a sentence: "The position follows a Monday–Saturday, five-day work week with hourly pay plus overtime, paid weekly." But we should not duplicate. I'll include a short paragraph after the introduction that includes schedule and pay type. Better: In About the Role, include the introduction paragraph, then a paragraph with schedule and pay type. Now, Responsibilities: list from Key Responsibilities. Qualifications: list from Qualifications. Pay: include the pay rates for A Level and B Level. The posting has "Compensation" section with same numbers. We'll include both hourly and annual earning potential, and typical overtime. Benefits: list from Benefits. Why Work Here: list from Why Work Here. Schedule: maybe just a short paragraph: "Monday–Saturday, five-day work week." But we already mentioned in About the Role. Could be a separate section. The rules say "Schedule" as a possible heading. Since the posting has a specific schedule, we can include a Schedule section with that detail. But it might be thin. The rules say "Prefer a few substantive sections over many thin ones." So maybe fold schedule into About the Role. I'll fold schedule into About the Role and not create a separate Schedule section. Additional Requirements: include the concise paragraph. Now, ensure we use- for lists. For Pay, we can use a list or paragraphs. Since there are two levels, we can use a list with two items, each containing details. Or use paragraphs. The rules say use
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but it's a list of pay levels. Could be a list. I'll use a list for Pay.
Similarly, Benefits is a list.
Why Work Here is a list.
Qualifications is a list.
Responsibilities is a list.
Now, write HTML.
We must not include any markdown code fences. Just raw HTML.
Let's craft.
First, About the Role:
About the Role
We are seeking experienced A-Level and B-Level Automotive Technicians to join a respected, family-owned automotive repair and tire shop in Newton, New Jersey. This high-volume facility offers consistent workflow, weekly pay, overtime opportunities, company-paid training, and excellent benefits while servicing a wide variety of domestic
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but it's a list of pay levels. Could be a list. I'll use a list for Pay.
Similarly, Benefits is a list.
Why Work Here is a list.
Qualifications is a list.
Responsibilities is a list.
Now, write HTML.
We must not include any markdown code fences. Just raw HTML.
Let's craft.
First, About the Role: