B-Level Automotive Technician | Up to $36/Hour | M-F
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
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, 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 posting starts with:
"Auto Kings
Location: Bend, OR
Schedule: Monday-Friday, 8:00 AM-5:00 PM (Flexible Start Times Available)
Pay Rate: $25-$36/hour, based on experience and skill level
Pay Type: Hourly
Pay Schedule: Bi-weekly"
This is metadata. The job title "Auto Kings" might be the company name? Actually "Auto Kings" appears to be the company. The job title is likely "A-Level or B-Level Automotive Technician" from the end. But the rule says do not repeat job title as heading. The page already shows it. So we should not include a heading for the job title.
We have "How to Apply (Important)" section with steps - this is application instructions, should be removed.
Then "Key Responsibilities" - list of duties.
"Qualifications" - list of requirements.
"Preferred Qualifications" - list.
"Compensation & Benefits" - includes pay rates for B-Level and A-Level, pay type, schedule, benefits (Medical, Dental & Vision Insurance, PTO, Paid Holidays, ASE Certification Reimbursement, Monday-Friday Schedule, Flexible Start Times, Toolbox Moving Assistance).
"Why Work Here?" - list of reasons.
"Additional Requirements" - about driver's license, background screening, etc.
We need to structure into sections.
Possible sections:
- About the role (maybe a brief intro from the beginning? The posting doesn't have a clear "About the role" paragraph. It starts with metadata. Could create a short paragraph summarizing the role? But rule: preserve all substantive information, do not invent. The metadata includes location, schedule, pay rate. Could fold into a short
under a heading like "Position Details" or "Overview". But the rule says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have "About the role" with a paragraph describing the role. However, the posting doesn't have a prose description of the role. It has "Why Work Here?" which describes the shop. Maybe we can create an "About the role" section with a paragraph that includes location, schedule, pay range? But the rule says do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can create a short paragraph at the top with location, schedule, pay rate, pay type, pay schedule. That could be under "About the role" or "Position Overview". But the rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" as heading and include a paragraph with the metadata.
But note: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given explicitly in the input, but "Auto Kings" is likely the company. The job title might be "Automotive Technician". The page already shows it, so we don't need to include it.
We need to include sections only when there is real content.
Let's list sections with content:
1. About the role: Could include a paragraph: "Auto Kings is seeking an A-Level or B-Level Automotive Technician in Bend, OR. The position offers a Monday–Friday schedule (8:00 AM–5:00 PM) with flexible start times available. Pay ranges from $25–$36/hour based on experience and skill level, paid hourly on a bi-weekly schedule." That's substantive.
2. Responsibilities: The "Key Responsibilities" list. Use - .
3. Qualifications: The "Qualifications" list. Use
- .
4. Preferred Qualifications: The "Preferred Qualifications" list. Could be separate or merged. Since it's distinct, we can have a separate section "Preferred Qualifications".
5. Compensation & Benefits: The "Compensation & Benefits" section includes pay rates for two levels, benefits. This could be split into "Pay" and "Benefits" sections. But the rule says use
for Pay, Schedule, Benefits. However, the posting has a combined "Compensation & Benefits". We can create "Pay" and "Benefits" sections. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay rates, pay type, pay schedule, and benefits. So we can create "Pay" and "Benefits". However, the schedule is also mentioned in metadata and in "Why Work Here?" (Monday-Friday schedule). Could have a "Schedule" section. But the rule says prefer few substantive sections over many thin ones. Maybe combine Pay and Benefits into "Compensation & Benefits" as a single section with sub-lists? But the rule says use for section headings like Pay, Benefits. It doesn't forbid combining. However, the example headings include Pay, Schedule, Benefits as separate. But we can decide.
Let's see: The posting has "Compensation & Benefits" heading with bullet points. It includes pay rates for B-Level and A-Level, pay type, pay schedule, then benefits list. That's a lot. Could split into "Pay" and "Benefits". But the schedule is also mentioned elsewhere. Might be okay to have "Compensation & Benefits" as one section with two sub-lists? But the rule says use - for any list of duties/requirements/benefits. It doesn't say we can't have subheadings within a section. But we only output
for top-level sections. We could have Compensation & Benefits
then Pay
? But the rule says use for section headings. It doesn't mention . Safer to keep only headings. So we can have separate Pay
and Benefits
. But the posting doesn't have separate headings; it's combined. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use those standard headings. The posting has pay and benefits info, so we can create Pay and Benefits sections.
But note: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states them. So we can create them.
Similarly, Schedule is stated in metadata and in "Why Work Here?" (Monday-Friday schedule, weekends off). Could create a Schedule section. But that might be thin. The metadata already includes schedule. Could fold into About the role or Benefits. The rule says prefer few substantive sections. So maybe include schedule in About the role paragraph and also in Benefits? The "Why Work Here?" includes "Monday-Friday Schedule: Regular hours of 8:00 AM-5:00 PM, with weekends off. Flexible Start Times: Earlier start times may be available, with consistent scheduling once established." That's a benefit. So we can include that in Benefits.
The "Why Work Here?" section is essentially benefits/work environment. Could be merged into Benefits.
"Additional Requirements" is about pre-employment screenings. Could be a separate section "Additional Requirements" or folded into Qualifications. Since it's specific, we can include as a section.
Now, we must remove application instructions (How to Apply), and any boilerplate (EEO, etc.). The "Additional Requirements" includes legal language about screenings, which is substantive? It's a requirement. We'll keep it.
Now, let's structure:
- About the role (paragraph with location, schedule, pay range)
- Responsibilities (list)
- Qualifications (list)
- Preferred Qualifications (list)
- Pay (list of pay rates, type, schedule)
- Benefits (list of benefits)
- Additional Requirements (paragraph or list)
But the rule says use - for any list of duties/requirements/benefits. For Pay, it's not a list of duties but a list of pay details. Could be a list. For Benefits, list.
We need to preserve all substantive information. So we must include all bullet points from the original.
Let's extract each list:
Key Responsibilities (8 items):
1. Perform comprehensive digital vehicle inspections (DVIs) to identify mechanical concerns, maintenance needs, and necessary repairs.
2. Diagnose and repair domestic, Asian, and European vehicles, including brake, suspension, steering, and cooling systems.
3. Complete general automotive maintenance, mechanical repairs, and removal and replacement (R&R) of vehicle components.
4. Use Snap-on Triton and Autel MaxiSys diagnostic scan tools to troubleshoot mechanical and electrical issues.
5. Perform independent mechanical and electrical diagnostics at the A-Level, or develop advanced diagnostic skills with shop manager support at the B-Level.
6. Identify root causes of vehicle concerns and complete repairs necessary to prepare used vehicles for dealership inventory.
7. Document inspection findings, repair recommendations, and completed work accurately through the shop's digital vehicle inspection process.
8. Maintain a clean, organized, and safe workspace while completing repairs efficiently and to established quality standards.
Qualifications (7 items):
1. Previous professional automotive repair experience in a dealership or independent repair shop required; 3-4 years of experience preferred.
2. Demonstrated ability to perform automotive maintenance, mechanical repairs, and component removal and replacement.
3. Strong understanding of automotive braking, suspension, steering, cooling, and general mechanical systems.
4. A-Level candidates must demonstrate independent mechanical and electrical diagnostic capabilities; B-Level candidates should have solid repair experience and developing diagnostic skills.
5. Experience servicing multiple makes and models, including domestic, Asian, and European vehicles.
6. Familiarity with automotive diagnostic scan tools and digital vehicle inspections, with training available on the shop's inspection process.
7. Ability to work independently, communicate repair findings clearly, and collaborate with shop leadership.
Preferred Qualifications (6 items):
1. Previous automotive dealership technician experience.
2. ASE certifications preferred but not required.
3. Experience with Tekmetric or similar automotive shop management software.
4. Experience performing digital vehicle inspections (DVIs).
5. Advanced electrical troubleshooting and automotive diagnostic skills, including experience with European vehicles.
Compensation & Benefits:
Pay rates:
- B-Level Technician: $25
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, 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 posting starts with: "Auto Kings Location: Bend, OR Schedule: Monday-Friday, 8:00 AM-5:00 PM (Flexible Start Times Available) Pay Rate: $25-$36/hour, based on experience and skill level Pay Type: Hourly Pay Schedule: Bi-weekly" This is metadata. The job title "Auto Kings" might be the company name? Actually "Auto Kings" appears to be the company. The job title is likely "A-Level or B-Level Automotive Technician" from the end. But the rule says do not repeat job title as heading. The page already shows it. So we should not include a heading for the job title. We have "How to Apply (Important)" section with steps - this is application instructions, should be removed. Then "Key Responsibilities" - list of duties. "Qualifications" - list of requirements. "Preferred Qualifications" - list. "Compensation & Benefits" - includes pay rates for B-Level and A-Level, pay type, schedule, benefits (Medical, Dental & Vision Insurance, PTO, Paid Holidays, ASE Certification Reimbursement, Monday-Friday Schedule, Flexible Start Times, Toolbox Moving Assistance). "Why Work Here?" - list of reasons. "Additional Requirements" - about driver's license, background screening, etc. We need to structure into sections. Possible sections: - About the role (maybe a brief intro from the beginning? The posting doesn't have a clear "About the role" paragraph. It starts with metadata. Could create a short paragraph summarizing the role? But rule: preserve all substantive information, do not invent. The metadata includes location, schedule, pay rate. Could fold into a short
under a heading like "Position Details" or "Overview". But the rule says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have "About the role" with a paragraph describing the role. However, the posting doesn't have a prose description of the role. It has "Why Work Here?" which describes the shop. Maybe we can create an "About the role" section with a paragraph that includes location, schedule, pay range? But the rule says do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can create a short paragraph at the top with location, schedule, pay rate, pay type, pay schedule. That could be under "About the role" or "Position Overview". But the rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" as heading and include a paragraph with the metadata.
But note: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given explicitly in the input, but "Auto Kings" is likely the company. The job title might be "Automotive Technician". The page already shows it, so we don't need to include it.
We need to include sections only when there is real content.
Let's list sections with content:
1. About the role: Could include a paragraph: "Auto Kings is seeking an A-Level or B-Level Automotive Technician in Bend, OR. The position offers a Monday–Friday schedule (8:00 AM–5:00 PM) with flexible start times available. Pay ranges from $25–$36/hour based on experience and skill level, paid hourly on a bi-weekly schedule." That's substantive.
2. Responsibilities: The "Key Responsibilities" list. Use - .
3. Qualifications: The "Qualifications" list. Use
- .
4. Preferred Qualifications: The "Preferred Qualifications" list. Could be separate or merged. Since it's distinct, we can have a separate section "Preferred Qualifications".
5. Compensation & Benefits: The "Compensation & Benefits" section includes pay rates for two levels, benefits. This could be split into "Pay" and "Benefits" sections. But the rule says use
for Pay, Schedule, Benefits. However, the posting has a combined "Compensation & Benefits". We can create "Pay" and "Benefits" sections. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay rates, pay type, pay schedule, and benefits. So we can create "Pay" and "Benefits". However, the schedule is also mentioned in metadata and in "Why Work Here?" (Monday-Friday schedule). Could have a "Schedule" section. But the rule says prefer few substantive sections over many thin ones. Maybe combine Pay and Benefits into "Compensation & Benefits" as a single section with sub-lists? But the rule says use for section headings like Pay, Benefits. It doesn't forbid combining. However, the example headings include Pay, Schedule, Benefits as separate. But we can decide.
Let's see: The posting has "Compensation & Benefits" heading with bullet points. It includes pay rates for B-Level and A-Level, pay type, pay schedule, then benefits list. That's a lot. Could split into "Pay" and "Benefits". But the schedule is also mentioned elsewhere. Might be okay to have "Compensation & Benefits" as one section with two sub-lists? But the rule says use - for any list of duties/requirements/benefits. It doesn't say we can't have subheadings within a section. But we only output
for top-level sections. We could have Compensation & Benefits
then Pay
? But the rule says use for section headings. It doesn't mention . Safer to keep only headings. So we can have separate Pay
and Benefits
. But the posting doesn't have separate headings; it's combined. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use those standard headings. The posting has pay and benefits info, so we can create Pay and Benefits sections.
But note: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states them. So we can create them.
Similarly, Schedule is stated in metadata and in "Why Work Here?" (Monday-Friday schedule, weekends off). Could create a Schedule section. But that might be thin. The metadata already includes schedule. Could fold into About the role or Benefits. The rule says prefer few substantive sections. So maybe include schedule in About the role paragraph and also in Benefits? The "Why Work Here?" includes "Monday-Friday Schedule: Regular hours of 8:00 AM-5:00 PM, with weekends off. Flexible Start Times: Earlier start times may be available, with consistent scheduling once established." That's a benefit. So we can include that in Benefits.
The "Why Work Here?" section is essentially benefits/work environment. Could be merged into Benefits.
"Additional Requirements" is about pre-employment screenings. Could be a separate section "Additional Requirements" or folded into Qualifications. Since it's specific, we can include as a section.
Now, we must remove application instructions (How to Apply), and any boilerplate (EEO, etc.). The "Additional Requirements" includes legal language about screenings, which is substantive? It's a requirement. We'll keep it.
Now, let's structure:
- About the role (paragraph with location, schedule, pay range)
- Responsibilities (list)
- Qualifications (list)
- Preferred Qualifications (list)
- Pay (list of pay rates, type, schedule)
- Benefits (list of benefits)
- Additional Requirements (paragraph or list)
But the rule says use - for any list of duties/requirements/benefits. For Pay, it's not a list of duties but a list of pay details. Could be a list. For Benefits, list.
We need to preserve all substantive information. So we must include all bullet points from the original.
Let's extract each list:
Key Responsibilities (8 items):
1. Perform comprehensive digital vehicle inspections (DVIs) to identify mechanical concerns, maintenance needs, and necessary repairs.
2. Diagnose and repair domestic, Asian, and European vehicles, including brake, suspension, steering, and cooling systems.
3. Complete general automotive maintenance, mechanical repairs, and removal and replacement (R&R) of vehicle components.
4. Use Snap-on Triton and Autel MaxiSys diagnostic scan tools to troubleshoot mechanical and electrical issues.
5. Perform independent mechanical and electrical diagnostics at the A-Level, or develop advanced diagnostic skills with shop manager support at the B-Level.
6. Identify root causes of vehicle concerns and complete repairs necessary to prepare used vehicles for dealership inventory.
7. Document inspection findings, repair recommendations, and completed work accurately through the shop's digital vehicle inspection process.
8. Maintain a clean, organized, and safe workspace while completing repairs efficiently and to established quality standards.
Qualifications (7 items):
1. Previous professional automotive repair experience in a dealership or independent repair shop required; 3-4 years of experience preferred.
2. Demonstrated ability to perform automotive maintenance, mechanical repairs, and component removal and replacement.
3. Strong understanding of automotive braking, suspension, steering, cooling, and general mechanical systems.
4. A-Level candidates must demonstrate independent mechanical and electrical diagnostic capabilities; B-Level candidates should have solid repair experience and developing diagnostic skills.
5. Experience servicing multiple makes and models, including domestic, Asian, and European vehicles.
6. Familiarity with automotive diagnostic scan tools and digital vehicle inspections, with training available on the shop's inspection process.
7. Ability to work independently, communicate repair findings clearly, and collaborate with shop leadership.
Preferred Qualifications (6 items):
1. Previous automotive dealership technician experience.
2. ASE certifications preferred but not required.
3. Experience with Tekmetric or similar automotive shop management software.
4. Experience performing digital vehicle inspections (DVIs).
5. Advanced electrical troubleshooting and automotive diagnostic skills, including experience with European vehicles.
Compensation & Benefits:
Pay rates:
- B-Level Technician: $25
- .
4. Preferred Qualifications: The "Preferred Qualifications" list. Could be separate or merged. Since it's distinct, we can have a separate section "Preferred Qualifications".
5. Compensation & Benefits: The "Compensation & Benefits" section includes pay rates for two levels, benefits. This could be split into "Pay" and "Benefits" sections. But the rule says use
for Pay, Schedule, Benefits. However, the posting has a combined "Compensation & Benefits". We can create "Pay" and "Benefits" sections. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay rates, pay type, pay schedule, and benefits. So we can create "Pay" and "Benefits". However, the schedule is also mentioned in metadata and in "Why Work Here?" (Monday-Friday schedule). Could have a "Schedule" section. But the rule says prefer few substantive sections over many thin ones. Maybe combine Pay and Benefits into "Compensation & Benefits" as a single section with sub-lists? But the rule says use
for section headings like Pay, Benefits. It doesn't forbid combining. However, the example headings include Pay, Schedule, Benefits as separate. But we can decide. Let's see: The posting has "Compensation & Benefits" heading with bullet points. It includes pay rates for B-Level and A-Level, pay type, pay schedule, then benefits list. That's a lot. Could split into "Pay" and "Benefits". But the schedule is also mentioned elsewhere. Might be okay to have "Compensation & Benefits" as one section with two sub-lists? But the rule says use
- for any list of duties/requirements/benefits. It doesn't say we can't have subheadings within a section. But we only output
for top-level sections. We could have
Compensation & Benefits
thenPay
? But the rule says usefor section headings. It doesn't mention
. Safer to keep only
headings. So we can have separate
Pay
andBenefits
. But the posting doesn't have separate headings; it's combined. However, the rule says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use those standard headings. The posting has pay and benefits info, so we can create Pay and Benefits sections. But note: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states them. So we can create them. Similarly, Schedule is stated in metadata and in "Why Work Here?" (Monday-Friday schedule, weekends off). Could create a Schedule section. But that might be thin. The metadata already includes schedule. Could fold into About the role or Benefits. The rule says prefer few substantive sections. So maybe include schedule in About the role paragraph and also in Benefits? The "Why Work Here?" includes "Monday-Friday Schedule: Regular hours of 8:00 AM-5:00 PM, with weekends off. Flexible Start Times: Earlier start times may be available, with consistent scheduling once established." That's a benefit. So we can include that in Benefits. The "Why Work Here?" section is essentially benefits/work environment. Could be merged into Benefits. "Additional Requirements" is about pre-employment screenings. Could be a separate section "Additional Requirements" or folded into Qualifications. Since it's specific, we can include as a section. Now, we must remove application instructions (How to Apply), and any boilerplate (EEO, etc.). The "Additional Requirements" includes legal language about screenings, which is substantive? It's a requirement. We'll keep it. Now, let's structure: - About the role (paragraph with location, schedule, pay range) - Responsibilities (list) - Qualifications (list) - Preferred Qualifications (list) - Pay (list of pay rates, type, schedule) - Benefits (list of benefits) - Additional Requirements (paragraph or list) But the rule says use
- for any list of duties/requirements/benefits. For Pay, it's not a list of duties but a list of pay details. Could be a list. For Benefits, list. We need to preserve all substantive information. So we must include all bullet points from the original. Let's extract each list: Key Responsibilities (8 items): 1. Perform comprehensive digital vehicle inspections (DVIs) to identify mechanical concerns, maintenance needs, and necessary repairs. 2. Diagnose and repair domestic, Asian, and European vehicles, including brake, suspension, steering, and cooling systems. 3. Complete general automotive maintenance, mechanical repairs, and removal and replacement (R&R) of vehicle components. 4. Use Snap-on Triton and Autel MaxiSys diagnostic scan tools to troubleshoot mechanical and electrical issues. 5. Perform independent mechanical and electrical diagnostics at the A-Level, or develop advanced diagnostic skills with shop manager support at the B-Level. 6. Identify root causes of vehicle concerns and complete repairs necessary to prepare used vehicles for dealership inventory. 7. Document inspection findings, repair recommendations, and completed work accurately through the shop's digital vehicle inspection process. 8. Maintain a clean, organized, and safe workspace while completing repairs efficiently and to established quality standards. Qualifications (7 items): 1. Previous professional automotive repair experience in a dealership or independent repair shop required; 3-4 years of experience preferred. 2. Demonstrated ability to perform automotive maintenance, mechanical repairs, and component removal and replacement. 3. Strong understanding of automotive braking, suspension, steering, cooling, and general mechanical systems. 4. A-Level candidates must demonstrate independent mechanical and electrical diagnostic capabilities; B-Level candidates should have solid repair experience and developing diagnostic skills. 5. Experience servicing multiple makes and models, including domestic, Asian, and European vehicles. 6. Familiarity with automotive diagnostic scan tools and digital vehicle inspections, with training available on the shop's inspection process. 7. Ability to work independently, communicate repair findings clearly, and collaborate with shop leadership. Preferred Qualifications (6 items): 1. Previous automotive dealership technician experience. 2. ASE certifications preferred but not required. 3. Experience with Tekmetric or similar automotive shop management software. 4. Experience performing digital vehicle inspections (DVIs). 5. Advanced electrical troubleshooting and automotive diagnostic skills, including experience with European vehicles. Compensation & Benefits: Pay rates: - B-Level Technician: $25
- for any list of duties/requirements/benefits. It doesn't say we can't have subheadings within a section. But we only output