Entry Level I&C Engineer
Donohue & Associates, Inc. · Indianapolis, IN · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. No job title heading. No metadata like Job ID. Remove boilerplate: EEO, etc. Also remove application instructions (none). Keep substantive info.
Let's parse posting:
First paragraph: "Donohue & Associates, a preferred provider of water and wastewater engineering services, is looking for an Entry Level I&C Engineer to join our multi-disciplinary team. In this position, you will be guided by highly experienced engineers specializing in the design, development and implementation of control systems for water and wastewater treatment facilities. You’ll be involved in ensuring that all systems meet the required specifications and quality standards for municipal and industrial clients throughout the Midwest. Our ideal candidate will be motivated, interested in continuous learning, and have strong communication, interpersonal and problem-solving skills."
That's about the role/responsibilities? Could be "About the role" and "Responsibilities". We need to decide sections.
We have "Requirements" list: Bachelor's degree in electrical engineering, automation, or related field. Relevant coursework and internships. Positive team- and client-focused attitude toward delivering quality work on time and within budget. Desire to be involved in the designing and developing of control systems for water/wastewater facilities. Strong communication and interpersonal skills. EIT certification or working towards PE.
Also "Qualifications" maybe same as requirements? But we can treat "Requirements" as the list. "Skills" could be communication, interpersonal, problem-solving, etc. But we already have those in requirements. Might combine.
We have "Benefits": list after "Donohue offers a competitive wage and comprehensive benefits package, including:" then bullet list: Medical, dental, and vision insurance; Robust 401(k) plan with company contribution; Paid time off and company holidays; Flexible work schedules around core hours; Short- and long-term disability/life insurance; Flexible spending accounts (FSAs); Professional organization support; Discretionary annual bonuses; Industry-unique monthly profit-sharing plan.
Also mention "competitive wage" but no specific number; we should not create Pay section unless posting actually states them. It says "competitive wage" but no specific number; that is vague. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, they do state them, so include Benefits. For Pay, they only say competitive wage (no specifics) - that's vague; we should not create Pay section. For Schedule, they mention "Flexible work schedules around core hours" which is a schedule detail; that is specific enough? It says flexible work schedules around core hours. That is a schedule detail. Should we include Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state flexible work schedules around core hours, which is schedule info. So we can include Schedule section with that detail.
But also note that flexible work schedules already appears in Benefits list; but we can still include Schedule section with that detail. However we should avoid duplication? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we put it in Benefits, it's already there. But we could also put in Schedule. However duplication may be okay but better to avoid redundancy. Since they listed flexible work schedules as part of benefits, we could keep it under Benefits and not create separate Schedule section. But the rule says we should not create Schedule section unless posting actually states them. It does state flexible work schedules around core hours, which is schedule info. So we could create Schedule section with that detail. However we already have that detail in Benefits list; duplication may be okay but maybe better to keep it only once. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating a thin Schedule section if the info is already covered elsewhere. So we can omit Schedule section and keep flexible work schedules under Benefits.
Thus sections: About the role (maybe combine with Responsibilities), Requirements, Benefits. Possibly Skills? But we have communication etc in requirements; we could have Skills section separate. But we can combine.
Let's decide: About the role: description of position, what you'll do. Responsibilities: maybe the bullet list of duties? Not explicitly listed as bullet; but we have sentences: "you will be guided by ...", "You’ll be involved in ensuring that all systems meet the required specifications and quality standards...". That's responsibilities.
We could make About the role: brief intro. Responsibilities: the two sentences about guidance and ensuring systems meet specs. Requirements: list as above. Benefits: list.
We should not include Qualifications separate if same as Requirements. Could omit.
Thus output HTML:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, but we should likely stick to those headings. It says "use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. No job title heading. No metadata like Job ID. Remove boilerplate: EEO, etc. Also remove application instructions (none). Keep substantive info.
Let's parse posting:
First paragraph: "Donohue & Associates, a preferred provider of water and wastewater engineering services, is looking for an Entry Level I&C Engineer to join our multi-disciplinary team. In this position, you will be guided by highly experienced engineers specializing in the design, development and implementation of control systems for water and wastewater treatment facilities. You’ll be involved in ensuring that all systems meet the required specifications and quality standards for municipal and industrial clients throughout the Midwest. Our ideal candidate will be motivated, interested in continuous learning, and have strong communication, interpersonal and problem-solving skills."
That's about the role/responsibilities? Could be "About the role" and "Responsibilities". We need to decide sections.
We have "Requirements" list: Bachelor's degree in electrical engineering, automation, or related field. Relevant coursework and internships. Positive team- and client-focused attitude toward delivering quality work on time and within budget. Desire to be involved in the designing and developing of control systems for water/wastewater facilities. Strong communication and interpersonal skills. EIT certification or working towards PE.
Also "Qualifications" maybe same as requirements? But we can treat "Requirements" as the list. "Skills" could be communication, interpersonal, problem-solving, etc. But we already have those in requirements. Might combine.
We have "Benefits": list after "Donohue offers a competitive wage and comprehensive benefits package, including:" then bullet list: Medical, dental, and vision insurance; Robust 401(k) plan with company contribution; Paid time off and company holidays; Flexible work schedules around core hours; Short- and long-term disability/life insurance; Flexible spending accounts (FSAs); Professional organization support; Discretionary annual bonuses; Industry-unique monthly profit-sharing plan.
Also mention "competitive wage" but no specific number; we should not create Pay section unless posting actually states them. It says "competitive wage" but no specific number; that is vague. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, they do state them, so include Benefits. For Pay, they only say competitive wage (no specifics) - that's vague; we should not create Pay section. For Schedule, they mention "Flexible work schedules around core hours" which is a schedule detail; that is specific enough? It says flexible work schedules around core hours. That is a schedule detail. Should we include Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state flexible work schedules around core hours, which is schedule info. So we can include Schedule section with that detail.
But also note that flexible work schedules already appears in Benefits list; but we can still include Schedule section with that detail. However we should avoid duplication? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we put it in Benefits, it's already there. But we could also put in Schedule. However duplication may be okay but better to avoid redundancy. Since they listed flexible work schedules as part of benefits, we could keep it under Benefits and not create separate Schedule section. But the rule says we should not create Schedule section unless posting actually states them. It does state flexible work schedules around core hours, which is schedule info. So we could create Schedule section with that detail. However we already have that detail in Benefits list; duplication may be okay but maybe better to keep it only once. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating a thin Schedule section if the info is already covered elsewhere. So we can omit Schedule section and keep flexible work schedules under Benefits.
Thus sections: About the role (maybe combine with Responsibilities), Requirements, Benefits. Possibly Skills? But we have communication etc in requirements; we could have Skills section separate. But we can combine.
Let's decide: About the role: description of position, what you'll do. Responsibilities: maybe the bullet list of duties? Not explicitly listed as bullet; but we have sentences: "you will be guided by ...", "You’ll be involved in ensuring that all systems meet the required specifications and quality standards...". That's responsibilities.
We could make About the role: brief intro. Responsibilities: the two sentences about guidance and ensuring systems meet specs. Requirements: list as above. Benefits: list.
We should not include Qualifications separate if same as Requirements. Could omit.
Thus output HTML:
About the role
Donohue & Associates, a preferred provider of water and wastewater engineering services, is looking for an Entry Level I&C Engineer to join our multi-disciplinary team. In this position, you will be guided by highly experienced engineers specializing in the design, development and implementation of control systems for water and wastewater treatment facilities. You’ll be involved in ensuring that all systems meet the required specifications and quality standards for municipal and industrial clients throughout the Midwest. Our ideal candidate will be motivated, interested in continuous learning, and have strong communication, interpersonal and problem-solving skills.
Responsibilities
You will be guided by highly experienced engineers specializing in the design, development and implementation of control systems for water and wastewater treatment facilities. You’ll be involved in ensuring that all systems meet the required specifications and quality standards for municipal and industrial clients throughout the Midwest.
But that duplicates the earlier sentences. Might be redundant. Better to have About the role as intro, Responsibilities as bullet list of duties. However we don't have explicit bullet list; we could turn the two sentences into responsibilities. But we need to avoid duplication. Perhaps we can combine: About the role includes the first sentence about looking for engineer; Responsibilities includes the guidance and ensuring systems meet specs. The ideal candidate sentence could go to Requirements or Skills. Let's think: The ideal candidate sentence: "Our ideal candidate will be motivated, interested in continuous learning, and have strong communication, interpersonal and problem-solving skills." That's more about skills/qualities. Could go to Skills section. Thus: About the role: first sentence about looking for Entry Level I&C Engineer. Responsibilities: the two sentences about guidance and ensuring systems meet specs. Skills: motivated, interested in continuous learning, strong communication, interpersonal and problem-solving skills. Requirements: Bachelor's degree in electrical engineering, automation, or related field. Relevant coursework and internships. Positive team- and client-focused attitude toward delivering quality work on time and within budget. Desire to be involved in the designing and developing of control systems for water/wastewater facilities. EIT certification or working towards PE. Benefits: list. We should not repeat the same content. Let's craft. About the role:Donohue & Associates, a preferred provider of water and wastewater engineering services, is looking for an Entry Level I&C Engineer to join our multi-disciplinary team.
Responsibilities:In this position, you will be guided by highly experienced engineers specializing in the design, development and implementation of control systems for water and wastewater treatment facilities. You’ll be involved in ensuring that all systems meet the required specifications and quality standards for municipal and industrial clients throughout the Midwest.
Skills:Our ideal candidate will be motivated, interested in continuous learning, and have strong communication, interpersonal and problem-solving skills.
Requirements:- Bachelor's degree in electrical engineering, automation, or related field.
- Relevant coursework and internships.
- Positive team- and client-focused attitude toward delivering quality work on time and within budget.
- Desire to be involved in the designing and developing of control systems for water/wastewater facilities.
- EIT certification or working towards PE.
Donohue offers a competitive wage and comprehensive benefits package, including:
- Medical, dental, and vision insurance
- Robust 401(k) plan with company contribution
- Paid time off and company holidays
- Flexible work schedules around core hours
- Short- and long-term disability/life insurance
- Flexible spending accounts (FSAs)
- Professional organization support
- Discretionary annual bonuses
- Industry-unique monthly profit-sharing plan
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, but we should likely stick to those headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. So we cannot add a custom heading like "About the company". We must fit that info into one of the allowed sections. Probably "About the role" can include company description. Or we could put under Responsibilities? Not ideal. Better to extend About the role to include company overview.
Thus About the role paragraph(s) can include multiple sentences: the job lookup, company description, collaborative environment, awards, etc.
Let's craft About the role with multiple paragraphs? We can have multiple
under same heading? Probably yes. We'll put multiple
elements under the heading. Thus:
About the role
Donohue & Associates, a preferred provider of water and wastewater engineering services, is looking for an Entry Level I&C Engineer to join our multi-disciplinary team.
An employee-owned engineering consulting firm since 1997, Donoh