Sr. Product Reliability Engineer - MV Transformers
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: "Your Mission" (maybe About the role), "A Day in the Life" (maybe Responsibilities), "Who You Are" (maybe Qualifications/Skills), "What You’ll Be Doing" (Responsibilities), "What You’ll Need to Succeed" (Requirements/Qualifications), "Bonus Points If You Have..." (Skills?), "Compensation & Benefits" (Benefits, Pay?), "About the Company" (maybe not needed). Also "CORE Transformers manufactures..." intro paragraph maybe About the role.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO etc. Also remove application instructions (none). Remove navigation/legal etc.
We need to preserve all substantive info. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: maybe "About the role" (intro + mission), "Responsibilities" (A Day in the Life + What You’ll Be Doing), "Requirements" (What You’ll Need to Succeed), "Skills" (Bonus Points If You Have...), "Benefits" (Compensation & Benefits). Pay and Schedule: we have "Competitive base salary, commensurate with experience." That's pay info but it's vague "commensurate with experience" - we should not create Pay section if it's just placeholder? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state "Competitive base salary, commensurate with experience." That's somewhat vague but it's still stating compensation. However "commensurate with experience" is considered placeholder? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). So we should not create a Pay section with just that phrase. However we have other benefits details: quarterly bonus, medical etc. That's substantive. So we can have Benefits section with those details. Pay maybe omitted.
Schedule: "This role is an 'on-site' role from our Seneca, SC facility." That's schedule/location. Could be Schedule section? It's not exactly schedule but location. The rule: create Schedule section only if posting actually states them. It does state on-site role. Could be considered schedule/location. Might be okay to include a Schedule section with that line. But we need to avoid filler. It's specific: on-site role from Seneca, SC facility. That's substantive. So we can include Schedule.
We need to avoid duplication. Let's extract content.
Intro paragraph: "If you like being the person who makes a good design even better once it’s out in the field — chasing a field failure until you know exactly why it happened, tightening a tolerance that’s been costing installers time, or turning a one-off fix into a documented standard — this role is worth your full attention. CORE Transformers manufactures dry-type, pad mount, and substation transformers from 15 kVA to 30 MVA, up to 230 kV. We supply critical electrical infrastructure to AI-driven data centers, large-scale construction, and industrial operations nationwide. We’re tracking 3x annual revenue growth, which means more units in the field, more installers depending on our designs working the first time, and a real need for someone who owns the gap between a good design on paper and a good design in the field."
That's about the role/company. We'll put under About the role.
Your Mission paragraph: "You are joining as our first dedicated Sr. Product Reliability Engineer. Where our R&D team builds tomorrow’s product line, you own what’s already shipped and what’s in production today: field performance, installation issues, quality escapes, and the steady stream of engineering changes that keep our standard designs current and our manufacturing partners aligned to spec. You’ll work closely with our quality team, our overseas manufacturing partners, and our sales organization to close the loop between what customers experience in the field and what actually gets built. You will report directly to the VP of Engineering, with this role positioned to grow — and to grow a team — as CORE scales."
That's also about role.
A Day in the Life paragraph: detailed narrative. We'll treat as Responsibilities.
What You’ll Be Doing bullet list: list of duties. We'll make
- .
Who You Are paragraph: description of traits.
What You’ll Need to Succeed bullet list: requirements.
Bonus Points If You Have... bullet list: skills/bonus.
Compensation & Benefits: list: Competitive base salary, commensurate with experience. Quarterly bonus eligibility after 90 days employment. Medical, dental, vision, life insurance, disability coverage available. 401(k) with matching. PTO and paid holidays. This role is an "on-site" role from our Seneca, SC facility.
We'll separate Benefits (medical etc) and maybe Pay (base salary, quarterly bonus). But base salary phrase is placeholder; we might omit Pay section. However quarterly bonus is specific. Could include under Benefits as well. We'll just have Benefits section containing all those items except maybe base salary phrase? But we need to preserve all substantive info; we can include base salary phrase as part of Benefits? It's still compensation. The rule says avoid filler like "commensurate with experience". That phrase is filler. So we could omit that phrase? But we must preserve ALL substantive information; does that phrase count as substantive? It's vague but still info. However the rule explicitly says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). So if we include a Pay section with that phrase, it's violating. Better to not have a Pay section at all, and maybe incorporate the base salary phrase into Benefits? But that would still be filler. Perhaps we can omit the base salary phrase entirely? But that would be removing substantive info (though it's vague). The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The base salary phrase is not substantive detail; it's generic. Might be considered not substantive? Hard to judge. Safer to keep it but maybe we can incorporate it into a Benefits section but still it's filler. The rule about Pay/Schedule/Benefits sections: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info (base salary, quarterly bonus, benefits). So we can have a Benefits section that includes all compensation and benefits. The rule about filler only applies to headings followed by filler text. If we put a Benefits heading and then list items that include "Competitive base salary, commensurate with experience." that includes filler phrase but also substantive? Might be okay? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It seems they want to avoid sections that just have filler like "Pay: commensurate with experience". If we have a Benefits section with multiple items, some of which are filler, maybe still okay? But to be safe, we could omit the base salary phrase and keep the rest: quarterly bonus, medical etc. However that would be removing info (though it's generic). I'd lean to keep it but maybe rephrase to avoid filler? We cannot invent or summarize away detail; we must preserve. So we must keep the exact phrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't require verbatim, but we shouldn't lose detail. The base salary phrase is not really detail; it's generic. I'd keep it but maybe it's okay.
Schedule: "This role is an 'on-site' role from our Seneca, SC facility." We'll put under Schedule.
Now structure:
About the role
Intro + Mission combined? Could be two paragraphs.
Responsibilities
A Day in the Life paragraph
- ... from What You’ll Be Doing
Requirements
- ... from What You’ll Need to Succeed
Skills
- ... from Bonus Points If You Have...
Benefits
- Competitive base salary, commensurate with experience.
- Quarterly bonus eligibility after 90 days employment.
- Medical, dental, vision, life insurance, disability coverage available.
- 401(k) with matching.
- PTO and paid holidays.
Schedule
This role is an "on-site" role from our Seneca, SC facility.
We also have "Who You Are" paragraph; could be part of Requirements or Skills? It's more about personal traits; could be under Requirements as well. But we already have Requirements list; we could add a paragraph under Requirements before list. Or we could make a separate section "Qualifications". The instruction: use headings like Qualifications, Skills. We have Requirements (what you need to succeed) and Skills (bonus). Who You Are could be under Qualifications. Let's make a section "Qualifications" containing Who You Are paragraph plus maybe the requirements list? But we already have Requirements list. Better to follow typical: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities, Requirements (what you need to succeed), Qualifications (who you are), Skills (bonus), Benefits, Schedule. We'll omit Pay.
Thus:
Responsibilities
A Day in the Life paragraph
- What You’ll Be Doing items
Requirements
- What You’ll Need to Succeed items
Qualifications
Who You Are paragraph
Skills
- Bonus Points If You Have... items
Benefits
- Compensation & Benefits items
Schedule
This role is an "on-site" role from our Seneca, SC facility.
Now we need to extract list items precisely.
What You’ll Need to Succeed:
- Bachelor’s degree in electrical engineering, or equivalent hands-on experience in medium-voltage transformer or power systems engineering.
- 5+ years of engineering experience in power systems, medium-voltage electrical equipment, or transformer manufacturing, with real exposure to what happens after a unit ships.
- Working knowledge of liquid-filled and/or dry-type transformer design fundamentals: core and coil, winding configurations, insulation systems.
- Comfort with outside-the-tank systems: switchgear integration points, protection devices, CT configurations, and accessory hardware.
- Experience with root-cause analysis and corrective-action processes (8D, 5-Why, or similar) in a manufacturing environment.
- Ability to read and markup engineering drawings, and to write clear, field-usable documentation.
- Willingness to travel occasionally for on-site installation or field support.
- Willing and able to work on-site in Seneca, SC.
Bonus Points If You Have...:
- Experience coordinating quality or engineering specs with an overseas manufacturing partner.
- Experience in data center, hyperscale, or large-scale construction power systems.
- Familiarity with UL, IEEE, IEC, or NEC standards relevant to transformers.
- A quality-engineering background (CQE or equivalent experience
for prose. We need to decide sections: maybe "About the role" (intro + mission), "Responsibilities" (A Day in the Life + What You’ll Be Doing), "Requirements" (What You’ll Need to Succeed), "Skills" (Bonus Points If You Have...), "Benefits" (Compensation & Benefits). Pay and Schedule: we have "Competitive base salary, commensurate with experience." That's pay info but it's vague "commensurate with experience" - we should not create Pay section if it's just placeholder? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state "Competitive base salary, commensurate with experience." That's somewhat vague but it's still stating compensation. However "commensurate with experience" is considered placeholder? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). So we should not create a Pay section with just that phrase. However we have other benefits details: quarterly bonus, medical etc. That's substantive. So we can have Benefits section with those details. Pay maybe omitted. Schedule: "This role is an 'on-site' role from our Seneca, SC facility." That's schedule/location. Could be Schedule section? It's not exactly schedule but location. The rule: create Schedule section only if posting actually states them. It does state on-site role. Could be considered schedule/location. Might be okay to include a Schedule section with that line. But we need to avoid filler. It's specific: on-site role from Seneca, SC facility. That's substantive. So we can include Schedule. We need to avoid duplication. Let's extract content. Intro paragraph: "If you like being the person who makes a good design even better once it’s out in the field — chasing a field failure until you know exactly why it happened, tightening a tolerance that’s been costing installers time, or turning a one-off fix into a documented standard — this role is worth your full attention. CORE Transformers manufactures dry-type, pad mount, and substation transformers from 15 kVA to 30 MVA, up to 230 kV. We supply critical electrical infrastructure to AI-driven data centers, large-scale construction, and industrial operations nationwide. We’re tracking 3x annual revenue growth, which means more units in the field, more installers depending on our designs working the first time, and a real need for someone who owns the gap between a good design on paper and a good design in the field." That's about the role/company. We'll put under About the role. Your Mission paragraph: "You are joining as our first dedicated Sr. Product Reliability Engineer. Where our R&D team builds tomorrow’s product line, you own what’s already shipped and what’s in production today: field performance, installation issues, quality escapes, and the steady stream of engineering changes that keep our standard designs current and our manufacturing partners aligned to spec. You’ll work closely with our quality team, our overseas manufacturing partners, and our sales organization to close the loop between what customers experience in the field and what actually gets built. You will report directly to the VP of Engineering, with this role positioned to grow — and to grow a team — as CORE scales." That's also about role. A Day in the Life paragraph: detailed narrative. We'll treat as Responsibilities. What You’ll Be Doing bullet list: list of duties. We'll make
- .
Who You Are paragraph: description of traits.
What You’ll Need to Succeed bullet list: requirements.
Bonus Points If You Have... bullet list: skills/bonus.
Compensation & Benefits: list: Competitive base salary, commensurate with experience. Quarterly bonus eligibility after 90 days employment. Medical, dental, vision, life insurance, disability coverage available. 401(k) with matching. PTO and paid holidays. This role is an "on-site" role from our Seneca, SC facility.
We'll separate Benefits (medical etc) and maybe Pay (base salary, quarterly bonus). But base salary phrase is placeholder; we might omit Pay section. However quarterly bonus is specific. Could include under Benefits as well. We'll just have Benefits section containing all those items except maybe base salary phrase? But we need to preserve all substantive info; we can include base salary phrase as part of Benefits? It's still compensation. The rule says avoid filler like "commensurate with experience". That phrase is filler. So we could omit that phrase? But we must preserve ALL substantive information; does that phrase count as substantive? It's vague but still info. However the rule explicitly says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). So if we include a Pay section with that phrase, it's violating. Better to not have a Pay section at all, and maybe incorporate the base salary phrase into Benefits? But that would still be filler. Perhaps we can omit the base salary phrase entirely? But that would be removing substantive info (though it's vague). The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The base salary phrase is not substantive detail; it's generic. Might be considered not substantive? Hard to judge. Safer to keep it but maybe we can incorporate it into a Benefits section but still it's filler. The rule about Pay/Schedule/Benefits sections: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info (base salary, quarterly bonus, benefits). So we can have a Benefits section that includes all compensation and benefits. The rule about filler only applies to headings followed by filler text. If we put a Benefits heading and then list items that include "Competitive base salary, commensurate with experience." that includes filler phrase but also substantive? Might be okay? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It seems they want to avoid sections that just have filler like "Pay: commensurate with experience". If we have a Benefits section with multiple items, some of which are filler, maybe still okay? But to be safe, we could omit the base salary phrase and keep the rest: quarterly bonus, medical etc. However that would be removing info (though it's generic). I'd lean to keep it but maybe rephrase to avoid filler? We cannot invent or summarize away detail; we must preserve. So we must keep the exact phrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't require verbatim, but we shouldn't lose detail. The base salary phrase is not really detail; it's generic. I'd keep it but maybe it's okay.
Schedule: "This role is an 'on-site' role from our Seneca, SC facility." We'll put under Schedule.
Now structure:
About the role
Intro + Mission combined? Could be two paragraphs.
Responsibilities
A Day in the Life paragraph
- ... from What You’ll Be Doing
Requirements
- ... from What You’ll Need to Succeed
Skills
- ... from Bonus Points If You Have...
Benefits
- Competitive base salary, commensurate with experience.
- Quarterly bonus eligibility after 90 days employment.
- Medical, dental, vision, life insurance, disability coverage available.
- 401(k) with matching.
- PTO and paid holidays.
Schedule
This role is an "on-site" role from our Seneca, SC facility.
We also have "Who You Are" paragraph; could be part of Requirements or Skills? It's more about personal traits; could be under Requirements as well. But we already have Requirements list; we could add a paragraph under Requirements before list. Or we could make a separate section "Qualifications". The instruction: use headings like Qualifications, Skills. We have Requirements (what you need to succeed) and Skills (bonus). Who You Are could be under Qualifications. Let's make a section "Qualifications" containing Who You Are paragraph plus maybe the requirements list? But we already have Requirements list. Better to follow typical: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities, Requirements (what you need to succeed), Qualifications (who you are), Skills (bonus), Benefits, Schedule. We'll omit Pay. Thus:Responsibilities
A Day in the Life paragraph
- What You’ll Be Doing items
Requirements
- What You’ll Need to Succeed items
Qualifications
Who You Are paragraph
Skills
- Bonus Points If You Have... items
Benefits
- Compensation & Benefits items
Schedule
This role is an "on-site" role from our Seneca, SC facility.
Now we need to extract list items precisely. What You’ll Need to Succeed: - Bachelor’s degree in electrical engineering, or equivalent hands-on experience in medium-voltage transformer or power systems engineering. - 5+ years of engineering experience in power systems, medium-voltage electrical equipment, or transformer manufacturing, with real exposure to what happens after a unit ships. - Working knowledge of liquid-filled and/or dry-type transformer design fundamentals: core and coil, winding configurations, insulation systems. - Comfort with outside-the-tank systems: switchgear integration points, protection devices, CT configurations, and accessory hardware. - Experience with root-cause analysis and corrective-action processes (8D, 5-Why, or similar) in a manufacturing environment. - Ability to read and markup engineering drawings, and to write clear, field-usable documentation. - Willingness to travel occasionally for on-site installation or field support. - Willing and able to work on-site in Seneca, SC. Bonus Points If You Have...: - Experience coordinating quality or engineering specs with an overseas manufacturing partner. - Experience in data center, hyperscale, or large-scale construction power systems. - Familiarity with UL, IEEE, IEC, or NEC standards relevant to transformers. - A quality-engineering background (CQE or equivalent experience