Substation Staff Engineer
KCI · United States · 1 mo ago
RemoteRemoteEngineeringFull-time
We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include boilerplate like EEO etc. Must include only sections with real content.
We need to parse the posting: Overview (intro) maybe not a heading? The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes Overview (company description), Duties, Responsibilities & Other (detailed responsibilities), Key Technical Skills Required, The Key Responsibilities Of This Role Include (more responsibilities), Ownership And Accountability, Training, Development, And Compliance, Financial Management, Essential Duties and Responsibilities..., Qualifications (Education and/or Skills Required, Education And/or Work Experience Preferred, Certificates, Licenses, And/or Registrations Required, Preferred, etc.)
We need to decide which sections to output: About the role? Could be overview. Responsibilities: combine duties. Requirements: maybe qualifications. Skills: key technical skills. Benefits: there is a mention of benefits in "KCI Benefits Information" paragraph: "We offer a competitive compensation package, family friendly benefits, a collaborative working environment, and the training, mentoring and resources you need to advance in your career." That's benefits info. Pay: not specified (no salary). So we should not include Pay section because no specific pay. Schedule: not specified. So we omit Pay and Schedule.
We must not include headings with filler like "commensurate with experience". Not present.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from the posting.
We need to output only HTML fragment, no /, no markdown fences.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes Overview (company description), Duties, Responsibilities & Other (detailed responsibilities), Key Technical Skills Required, The Key Responsibilities Of This Role Include (more responsibilities), Ownership And Accountability, Training, Development, And Compliance, Financial Management, Essential Duties and Responsibilities..., Qualifications (Education and/or Skills Required, Education And/or Work Experience Preferred, Certificates, Licenses, And/or Registrations Required, Preferred, etc.)
We need to decide which sections to output: About the role? Could be overview. Responsibilities: combine duties. Requirements: maybe qualifications. Skills: key technical skills. Benefits: there is a mention of benefits in "KCI Benefits Information" paragraph: "We offer a competitive compensation package, family friendly benefits, a collaborative working environment, and the training, mentoring and resources you need to advance in your career." That's benefits info. Pay: not specified (no salary). So we should not include Pay section because no specific pay. Schedule: not specified. So we omit Pay and Schedule.
We must not include headings with filler like "commensurate with experience". Not present.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from the posting.
We need to output only HTML fragment, no /, no markdown fences.
We need to use for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what constitutes a list. Many paragraphs contain enumerated items separated by commas or semicolons; but we should only use
- when there is a list explicitly. The instructions: "Use
- for any list of duties/requirements/benefits". So if the content is a list (like bullet points), we should format as list. The posting uses sentences with commas; not explicit bullet list. We could still treat as list? Safer to keep as prose (
) unless there is clear list with line breaks or semicolons indicating separate items. The posting includes many sentences with semicolons separating items; but not explicit list. I'd keep as prose.
But we could convert some enumerated items into
- for clarity. However risk of altering meaning? The instruction says to use list for any list of duties/requirements/benefits. If we treat the content as a list, we should break into items. Might be okay.
Let's identify sections:
- About the role / Overview: The first paragraphs about company culture, mission, employee ownership, etc. Could be "About the role" or maybe "About the company". We'll use
About the role
and include the overview prose.
- Responsibilities: Combine duties, responsibilities, key responsibilities, ownership/accountability, training/development, financial management, essential duties. Could be one big Responsibilities section. But we might split into Responsibilities and Requirements etc. However we need to avoid too many thin sections. Prefer few substantive sections.
We could have sections: About the role, Responsibilities, Key Technical Skills (Skills), Qualifications, Benefits.
Let's extract content for each.
**About the role** (overview): The first paragraph(s) before "The Company". Actually the posting starts: "Overview Join us as we Rise to the Challenge At KCI, we’re building an enduring community that provides unparalleled value to our employee-owners. We make our mark designing and delivering our world-class solutions, so we invest deeply in supporting and developing our team. We reward integrity and commitment, and when we do well, you do well. Our employees have the freedom to innovate, unlimited growth, a voice that matters, a lifestyle that works, and skin in the game. Achievements are shared and celebrated. As a team, we are motivated to better ourselves, each other, and the world around us."
Then "The Company KCI Technologies, Inc. is a 100% employee-owned engineering, consulting and construction firm serving clients throughout the United States. KCI is recognized as an industry leader, employing cutting-edge technologies, management practices and strategic growth initiatives. Employee ownership fosters an entrepreneurial spirit, encourages technical expertise, and shapes strategic planning. KCI is currently ranked #50 on Engineering News-Record’s list of the Top 500 design firms in the nation."
Then "KCI Benefits Information We offer a competitive compensation package, family friendly benefits, a collaborative working environment, and the training, mentoring and resources you need to advance in your career. We understand that you have choices, and we know that together we will make a great team! KCI is committed to building a diverse and inclusive staff, and we encourage women, people of color, LGBTQ+ individuals, and individuals with disabilities to apply. KCI Technologies, Inc. is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability or veteran status."
We need to remove EEO boilerplate. So we should cut the equal opportunity employer sentence and the encouragement line? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the EEO statement and the encouragement line? The encouragement line about women etc is part of EEO? It's diversity encouragement; could be considered EEO boilerplate. Safer to remove that line as well. Also remove "KCI Benefits Information" heading? Not a heading; just text. We'll keep the benefits sentence.
Thus About the role section will include the overview paragraphs (first two paragraphs) and maybe the benefits sentence? Actually benefits sentence is separate; we could put it in Benefits section. Let's keep overview separate.
Thus About the role: include the first two paragraphs (Overview and The Company). We'll combine them into prose.
**Responsibilities**: Need to capture duties, responsibilities, key responsibilities, ownership/accountability, training/development, financial management, essential duties. That's a lot; we can combine into one Responsibilities section with prose. Must preserve all substantive information; we can't omit details. We'll need to include all those details.
We'll need to parse the responsibilities section text.
Let's extract the responsibilities text from "Duties, Responsibilities & Other As KCI Energy’s Staff Engineer – Substation, you perform engineering assignments..." through to the end before "Qualifications". We'll need to include all sentences.
Let's copy that section:
"Duties, Responsibilities & Other As KCI Energy’s Staff Engineer – Substation, you perform engineering assignments of increasing complexity supporting transmission and distribution substation projects. The role may be filled by an engineer whose primary technical experience or developing specialty is in Substation Physical and/or Protection & Control and/or Substation Studies and/or Settings/SCADA. Working under the direction of Project Engineers, responsible Professional Engineers, and experienced technical staff, you prepare assigned engineering work and support project delivery from conceptual engineering through construction and commissioning support. You are expected to develop technical capability in at least one specialty—not necessarily all four—while building awareness of the other specialties and multidisciplinary interfaces. You are accountable for the accuracy, completeness, coordination, and technical quality of your assigned work. You collaborate with Engineers, Designers, and CAD Technicians; follow established standards and workflows; communicate questions and risks early; apply review feedback; and steadily increase your technical judgment and project responsibility. Key Technical Skills Required Demonstrate foundational technical knowledge and developing capability in Substation Physical and/or Protection & Control and/or Substation Studies and/or Settings/SCADA. Exposure to multiple specialties is preferred but is not required. Substation Physical: Support equipment selection and application, one-line diagrams, general arrangements, equipment layouts, bus and conductor design, electrical clearances, grounding, lightning protection, raceways, cable routing, control building arrangements, auxiliary AC/DC systems, equipment specifications, bills of material, and physical design calculations. Protection & Control: Support development of protection philosophies, one-line and three-line diagrams, AC/DC schematics, relay and control panels, wiring and interconnection diagrams, CT/VT application, tripping and interlocking schemes, control logic, telecom and SCADA interfaces, cutover plans, testing requirements, and commissioning support. Substation Studies: Support power-system model development and perform assigned analysis under technical direction, which may include load flow, short circuit, grounding, arc-flash, protection coordination, insulation coordination, temporary and switching overvoltage, transient recovery voltage, electromagnetic transient, dynamic stability, EMF, induced voltage, and other specialty studies. Settings/SCADA: Support protective relay settings and coordination, relay logic and configuration, RTU/IED/gateway integration, SCADA architecture, HMI and alarm configuration, point lists, I/O mapping, databases, communications networks and protocols, IEC 61850 integration, FAT/SAT, field testing, energization, and commissioning support. Develop working knowledge of and apply IEEE, ANSI, NESC, NEC, NFPA, utility standards, client specifications, and industry practices under appropriate technical guidance. Support coordination of assigned interfaces among Substation Physical, Protection & Control, Substation Studies, Settings/SCADA, Civil, Structural, Geotechnical, Transmission Line, Project Management, vendors, contractors, and clients. Develop awareness and practical experience in constructability, brownfield execution, outage and cutover planning, system performance, field support, commissioning, quality assurance, and risk management. Use Microsoft Word, Microsoft Excel, and engineering, design, modeling, settings, automation, and document-control tools applicable to the assigned technical specialty. Experience may include AutoCAD, MicroStation, Bluebeam, ProjectWise, ETAP, SKM, CDEGS, ASPEN OneLiner, CAPE, PSS®E, PSCAD, PowerWorld, relay configuration software, SCADA platforms, and IEC 61850 engineering tools. The Key Responsibilities Of This Role Include Project Engineering and Collaboration: Complete assigned engineering tasks under the direction of a Project Engineer, Senior Engineering Designer, or responsible Professional Engineer while supporting successful project delivery. Apply established engineering execution plans, design criteria, technical approaches, deliverable requirements, review processes, and multidisciplinary workflows. Prepare assigned calculations, models, settings, databases, specifications, reports, drawings, equipment requirements, procurement documents, testing documentation, and bills of material applicable to the developing technical specialty. Support assigned interfaces among Substation Physical, Protection & Control, Substation Studies, Settings/SCADA, Civil, Structural, Geotechnical, Transmission Line, and other disciplines. Coordinate day-to-day assigned work with Engineers, Designers, CAD Technicians, specialty disciplines, vendors, and other project resources. Assist with technical coordination involving clients, utilities, vendors, contractors, and internal project leadership. Participate in technical, design, constructability, client, vendor, and interdisciplinary review meetings and document assigned actions. Assist with scope development, estimating, resource planning, technical approaches, proposals, and presentations as assigned. Collaborate effectively with Engineers, Designers, and CAD Technicians; receive coaching and review feedback; and share developing knowledge with teammates. Prepare assigned deliverables to meet KCI quality standards, client specifications, applicable codes, regulatory requirements, and professional engineering obligations. Ownership And Accountability Take ownership of assigned engineering tasks from planning through completion and comment resolution. Maintain accountability for the accuracy, completeness, coordination, quality, and compliance of assigned work. Identify questions, design conflicts, missing information, schedule impacts, quality concerns, and constructability issues early and communicate them to experienced technical staff. Document engineering assumptions, calculations, and decisions; apply established methods; seek guidance when needed; and escalate material technical or project risks appropriately. Address review comments completely and prepare assigned work for the required technical review and approval before issuance
- for any list of duties/requirements/benefits, and
for prose. We need to decide what constitutes a list. Many paragraphs contain enumerated items separated by commas or semicolons; but we should only use
- when there is a list explicitly. The instructions: "Use
- for any list of duties/requirements/benefits". So if the content is a list (like bullet points), we should format as list. The posting uses sentences with commas; not explicit bullet list. We could still treat as list? Safer to keep as prose (
) unless there is clear list with line breaks or semicolons indicating separate items. The posting includes many sentences with semicolons separating items; but not explicit list. I'd keep as prose. But we could convert some enumerated items into
- for clarity. However risk of altering meaning? The instruction says to use list for any list of duties/requirements/benefits. If we treat the content as a list, we should break into items. Might be okay.
Let's identify sections:
- About the role / Overview: The first paragraphs about company culture, mission, employee ownership, etc. Could be "About the role" or maybe "About the company". We'll use
About the role
and include the overview prose. - Responsibilities: Combine duties, responsibilities, key responsibilities, ownership/accountability, training/development, financial management, essential duties. Could be one big Responsibilities section. But we might split into Responsibilities and Requirements etc. However we need to avoid too many thin sections. Prefer few substantive sections. We could have sections: About the role, Responsibilities, Key Technical Skills (Skills), Qualifications, Benefits. Let's extract content for each. **About the role** (overview): The first paragraph(s) before "The Company". Actually the posting starts: "Overview Join us as we Rise to the Challenge At KCI, we’re building an enduring community that provides unparalleled value to our employee-owners. We make our mark designing and delivering our world-class solutions, so we invest deeply in supporting and developing our team. We reward integrity and commitment, and when we do well, you do well. Our employees have the freedom to innovate, unlimited growth, a voice that matters, a lifestyle that works, and skin in the game. Achievements are shared and celebrated. As a team, we are motivated to better ourselves, each other, and the world around us." Then "The Company KCI Technologies, Inc. is a 100% employee-owned engineering, consulting and construction firm serving clients throughout the United States. KCI is recognized as an industry leader, employing cutting-edge technologies, management practices and strategic growth initiatives. Employee ownership fosters an entrepreneurial spirit, encourages technical expertise, and shapes strategic planning. KCI is currently ranked #50 on Engineering News-Record’s list of the Top 500 design firms in the nation." Then "KCI Benefits Information We offer a competitive compensation package, family friendly benefits, a collaborative working environment, and the training, mentoring and resources you need to advance in your career. We understand that you have choices, and we know that together we will make a great team! KCI is committed to building a diverse and inclusive staff, and we encourage women, people of color, LGBTQ+ individuals, and individuals with disabilities to apply. KCI Technologies, Inc. is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability or veteran status." We need to remove EEO boilerplate. So we should cut the equal opportunity employer sentence and the encouragement line? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the EEO statement and the encouragement line? The encouragement line about women etc is part of EEO? It's diversity encouragement; could be considered EEO boilerplate. Safer to remove that line as well. Also remove "KCI Benefits Information" heading? Not a heading; just text. We'll keep the benefits sentence. Thus About the role section will include the overview paragraphs (first two paragraphs) and maybe the benefits sentence? Actually benefits sentence is separate; we could put it in Benefits section. Let's keep overview separate. Thus About the role: include the first two paragraphs (Overview and The Company). We'll combine them into prose. **Responsibilities**: Need to capture duties, responsibilities, key responsibilities, ownership/accountability, training/development, financial management, essential duties. That's a lot; we can combine into one Responsibilities section with prose. Must preserve all substantive information; we can't omit details. We'll need to include all those details. We'll need to parse the responsibilities section text. Let's extract the responsibilities text from "Duties, Responsibilities & Other As KCI Energy’s Staff Engineer – Substation, you perform engineering assignments..." through to the end before "Qualifications". We'll need to include all sentences. Let's copy that section: "Duties, Responsibilities & Other As KCI Energy’s Staff Engineer – Substation, you perform engineering assignments of increasing complexity supporting transmission and distribution substation projects. The role may be filled by an engineer whose primary technical experience or developing specialty is in Substation Physical and/or Protection & Control and/or Substation Studies and/or Settings/SCADA. Working under the direction of Project Engineers, responsible Professional Engineers, and experienced technical staff, you prepare assigned engineering work and support project delivery from conceptual engineering through construction and commissioning support. You are expected to develop technical capability in at least one specialty—not necessarily all four—while building awareness of the other specialties and multidisciplinary interfaces. You are accountable for the accuracy, completeness, coordination, and technical quality of your assigned work. You collaborate with Engineers, Designers, and CAD Technicians; follow established standards and workflows; communicate questions and risks early; apply review feedback; and steadily increase your technical judgment and project responsibility. Key Technical Skills Required Demonstrate foundational technical knowledge and developing capability in Substation Physical and/or Protection & Control and/or Substation Studies and/or Settings/SCADA. Exposure to multiple specialties is preferred but is not required. Substation Physical: Support equipment selection and application, one-line diagrams, general arrangements, equipment layouts, bus and conductor design, electrical clearances, grounding, lightning protection, raceways, cable routing, control building arrangements, auxiliary AC/DC systems, equipment specifications, bills of material, and physical design calculations. Protection & Control: Support development of protection philosophies, one-line and three-line diagrams, AC/DC schematics, relay and control panels, wiring and interconnection diagrams, CT/VT application, tripping and interlocking schemes, control logic, telecom and SCADA interfaces, cutover plans, testing requirements, and commissioning support. Substation Studies: Support power-system model development and perform assigned analysis under technical direction, which may include load flow, short circuit, grounding, arc-flash, protection coordination, insulation coordination, temporary and switching overvoltage, transient recovery voltage, electromagnetic transient, dynamic stability, EMF, induced voltage, and other specialty studies. Settings/SCADA: Support protective relay settings and coordination, relay logic and configuration, RTU/IED/gateway integration, SCADA architecture, HMI and alarm configuration, point lists, I/O mapping, databases, communications networks and protocols, IEC 61850 integration, FAT/SAT, field testing, energization, and commissioning support. Develop working knowledge of and apply IEEE, ANSI, NESC, NEC, NFPA, utility standards, client specifications, and industry practices under appropriate technical guidance. Support coordination of assigned interfaces among Substation Physical, Protection & Control, Substation Studies, Settings/SCADA, Civil, Structural, Geotechnical, Transmission Line, Project Management, vendors, contractors, and clients. Develop awareness and practical experience in constructability, brownfield execution, outage and cutover planning, system performance, field support, commissioning, quality assurance, and risk management. Use Microsoft Word, Microsoft Excel, and engineering, design, modeling, settings, automation, and document-control tools applicable to the assigned technical specialty. Experience may include AutoCAD, MicroStation, Bluebeam, ProjectWise, ETAP, SKM, CDEGS, ASPEN OneLiner, CAPE, PSS®E, PSCAD, PowerWorld, relay configuration software, SCADA platforms, and IEC 61850 engineering tools. The Key Responsibilities Of This Role Include Project Engineering and Collaboration: Complete assigned engineering tasks under the direction of a Project Engineer, Senior Engineering Designer, or responsible Professional Engineer while supporting successful project delivery. Apply established engineering execution plans, design criteria, technical approaches, deliverable requirements, review processes, and multidisciplinary workflows. Prepare assigned calculations, models, settings, databases, specifications, reports, drawings, equipment requirements, procurement documents, testing documentation, and bills of material applicable to the developing technical specialty. Support assigned interfaces among Substation Physical, Protection & Control, Substation Studies, Settings/SCADA, Civil, Structural, Geotechnical, Transmission Line, and other disciplines. Coordinate day-to-day assigned work with Engineers, Designers, CAD Technicians, specialty disciplines, vendors, and other project resources. Assist with technical coordination involving clients, utilities, vendors, contractors, and internal project leadership. Participate in technical, design, constructability, client, vendor, and interdisciplinary review meetings and document assigned actions. Assist with scope development, estimating, resource planning, technical approaches, proposals, and presentations as assigned. Collaborate effectively with Engineers, Designers, and CAD Technicians; receive coaching and review feedback; and share developing knowledge with teammates. Prepare assigned deliverables to meet KCI quality standards, client specifications, applicable codes, regulatory requirements, and professional engineering obligations. Ownership And Accountability Take ownership of assigned engineering tasks from planning through completion and comment resolution. Maintain accountability for the accuracy, completeness, coordination, quality, and compliance of assigned work. Identify questions, design conflicts, missing information, schedule impacts, quality concerns, and constructability issues early and communicate them to experienced technical staff. Document engineering assumptions, calculations, and decisions; apply established methods; seek guidance when needed; and escalate material technical or project risks appropriately. Address review comments completely and prepare assigned work for the required technical review and approval before issuance
- for clarity. However risk of altering meaning? The instruction says to use list for any list of duties/requirements/benefits. If we treat the content as a list, we should break into items. Might be okay.
Let's identify sections:
- About the role / Overview: The first paragraphs about company culture, mission, employee ownership, etc. Could be "About the role" or maybe "About the company". We'll use
- for any list of duties/requirements/benefits". So if the content is a list (like bullet points), we should format as list. The posting uses sentences with commas; not explicit bullet list. We could still treat as list? Safer to keep as prose (
- when there is a list explicitly. The instructions: "Use