Field Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include: "Who We Are" could be "About the Company" but not listed. Could be "About the role"? Actually "What You'll Do" is role description. Could be "Responsibilities". There's "Key Responsibilities". There's "Additional Information" (maybe not needed). There's "Requirements". There's "What You'll Bring". There's "Benefits". There's no Pay or Schedule specifics. So we should include sections: About the Company? Not required but we could include as a
maybe under a heading like "About Rising Edge Group"? The instruction says use headings for those examples, but we can also have other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they expect those categories. We can include "About the Company" as a heading? Might be okay but not in list. Safer to include "About the role" for the description of role (What You'll Do). Then "Responsibilities" for Key Responsibilities. Then "Requirements" for Requirements and What You'll Bring combined? Could separate "Qualifications" and "Skills". But we have both degree/diploma requirement and experience, plus skills. Could split: "Qualifications" for education/experience, "Skills" for technical skills. Then "Benefits" for the Benefits section.
We must not include empty sections. Ensure we preserve all substantive info.
Let's extract content:
Who We Are: Rising Edge Group is an electrical contracting company founded in 2002, specialization in high-voltage electrical solutions that power critical infrastructure across North America. With operations in both Canada and the United States, we partner with clients across the electrical utilities, renewable energy, and industrial sectors to design, build, and maintain the critical infrastructure systems communities and industries rely on. Driven by a clear vision to strengthen the stability, reliability, and advancement of energy infrastructure, we take pride in delivering work that matters. Guided by our STRIDE values - Safety, Teamwork, Responsibility, Integrity, Deliver, and Excellence - we foster a people focused on a culture of growth, mentorship and collaboration where safety always come first.
What You'll Do: Reporting to the Construction Manager, the role of Field Engineer will play a crucial role in overseeing construction projects from the ground up. You will collaborate closely with Project Managers, Construction Managers, Quality Officers, Safety, Fleet, subcontractors, and clients to ensure work is executed safely, on schedule, and in accordance with the project specifications. This position calls for a detail-oriented and proactive individual who can effectively tackle challenges and ensure high-quality outcomes
Key Responsibilities: list bullet points (the long list). We'll need to convert each line into
- .
Additional Information: As a condition of employment, candidates will be required to complete pre-employment screening including professional reference checks and a criminal record check
Requirements: heading "Requirements". Then "What You'll Bring" list.
Let's extract Requirements bullet points:
- A degree or diploma in Electrical Engineering or a related field is required, or 4+ years working in a similar role within the High Voltage Construction industry
- 1-3 years of experience in a field engineering or similar role
- Strong understanding of construction methods, materials, and safety standards
- Proficient in Microsoft Excel and comfortable working with large sets of data
- Experience with project management software such as Aconex is an asset
- Outstanding problem-solving abilities and adaptability in a dynamic work environment
- Excellent communication and interpersonal skills for effective team collaboration
- Capability to manage multiple priorities while maintaining attention to detail
- Willingness to travel to various job sites as required
- Possession of a valid driver's license and ability to work outdoors in varying conditions
Benefits: The "Why Rising Edge Group?" section with subpoints: Safety & Excellence, People-First Culture, Career Growth & Impact, Reward & Recognition. Each has prose. We'll need to capture all substantive info.
We should not include boilerplate like "As a condition of employment..." maybe that's part of Requirements? It's under Additional Information. We'll keep it as a
maybe under a heading like "Additional Information" but not in list. Could incorporate into Requirements? It's a condition, not a requirement per se. Could be its own section "Additional Information". The instruction says include a section ONLY when posting has real, specific content for it. This is specific. So we can add a heading "Additional Information". However the examples didn't list that, but it's okay to have other headings? Might be okay. Safer to fold into Requirements as a note? But it's not a requirement; it's a condition. Could be a
under Requirements heading without a list. But we need to preserve it. I'd add a heading "Additional Information" with a
.
Now Benefits: we have multiple paragraphs. We'll make a
- for each benefit point? The instruction says use
- for any list of duties/requirements/benefits. So we can list each benefit as
- . We'll need to capture the prose inside each.
Let's extract each benefit:
Safety & Excellence: "Safety is at the heart of everything we do. Every project is approached with diligence, strategic planning, and reliable execution practices to protect our teams and the clients we serve while delivering world-class high-voltage solutions. Our unwavering commitment to safety and quality drives excellence on every project, every day."
People-First Culture: "You're more than a job title. Every person contributes to powering essential energy infrastructure across North America. Our teams are built on collaboration, respect, and accountability. We support our employees through meaningful engagement initiatives, team events, and a culture that prioritizes wellbeing, inclusion, and genuine lasting connections."
Career Growth & Impact: "Your role is a path to a long-term career. We empower our employees with hands-on experience, exposure to diverse projects, and opportunities to advance across disciplines, locations, and career paths. Through continuous learning, mentorship, and professional development, you'll build lasting expertise while making a tangible impact in an environment where teamwork and integrity guide our work."
Reward & Recognition: "We believe skill, dedication, and excellence deserves recognition. Competitive compensation, comprehensive benefits, and a strong culture of appreciation ensure your achievements are celebrated, your growth is supported, and your work truly makes a difference. At Rising Edge Group, you're not just building projects, you're building a meaningful career where your work helps power the future, one project at a time."
We'll include these as list items.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the Role
... (What You'll Do)
Responsibilities
- ...
...
Additional Information
As a condition of employment, candidates will be required to complete pre-employment screening including professional reference checks and a criminal record check
Requirements
- ...
...
Skills
Maybe we can split some of the requirements into Skills: Proficient in Microsoft Excel, Experience with project management software such as Aconex, Strong understanding of construction methods, materials, and safety standards, Outstanding problem-solving abilities, Excellent communication and interpersonal skills, Capability to manage multiple priorities, Willingness to travel, Possession of valid driver's license, Ability to work outdoors. But we already have them in Requirements list. Could keep all under Requirements. But we could also have Qualifications (education/experience) and Skills. However we risk creating thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine all into Requirements. That's fine.
Thus we have sections: About the Role, Responsibilities, Additional Information, Requirements, Benefits.
Check if any section is empty: All have content.
Now we need to ensure we didn't miss any substantive info from "Who We Are". Should we include that? It's company description. Could be under "About the Company" but not required. The instruction says we can use headings for examples but not limited. However we might want to include it as a section "About the Company". But if we add another section, we increase number of sections. The instruction says prefer a few substantive sections over many thin ones. The "Who We Are" is substantive. Could we incorporate it into About the Role? Not really. Could we add a section "About the Company". That would be another heading. Might be okay but we risk many sections. However we already have 5 sections; adding another makes 6. Still not many. I'd include it as a section "About the Company". But the instruction examples didn't list that, but it's not prohibited. I'd include it to preserve all substantive info.
Thus sections: About the Company, About the Role, Responsibilities, Additional Information, Requirements, Benefits.
Now we need to format.
Let's craft the HTML.
We'll need to escape any special characters? Not needed.
Now produce:
About the Company
Rising Edge Group is an electrical contracting company founded in 2002, specialization in high-voltage electrical solutions that power critical infrastructure across North America. With operations in both Canada and the United States, we partner with clients across the electrical utilities, renewable energy, and industrial sectors to design, build, and maintain the critical infrastructure systems communities and industries rely on. Driven by a clear vision to strengthen the stability, reliability, and advancement of energy infrastructure, we take pride in delivering work that matters. Guided by our STRIDE values - Safety, Teamwork, Responsibility, Integrity, Deliver, and Excellence - we foster a people focused on a culture of growth, mentorship and collaboration where safety always come first.
About the Role
Reporting to the Construction Manager, the role of Field Engineer will play a crucial role in overseeing construction projects from the ground up. You will collaborate closely with Project Managers, Construction Managers, Quality Officers, Safety, Fleet, subcontractors, and clients to ensure work is executed safely, on schedule, and in accordance with the project specifications. This position calls for a detail-oriented and proactive individual who can effectively tackle challenges and ensure high-quality outcomes.
Responsibilities
- Provide technical support during the construction phase, ensuring compliance with project designs and specifications
- Review and interpret project drawings and specifications, offering feedback as necessary
- Coordinate with subcontractors to ensure proper execution of project tasks
- Support project managers in maintaining accurate documentation of project progress and challenges
- Conduct regular site inspections to monitor progress and resolve any issues that arise
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: "Who We Are" could be "About the Company" but not listed. Could be "About the role"? Actually "What You'll Do" is role description. Could be "Responsibilities". There's "Key Responsibilities". There's "Additional Information" (maybe not needed). There's "Requirements". There's "What You'll Bring". There's "Benefits". There's no Pay or Schedule specifics. So we should include sections: About the Company? Not required but we could include as a
maybe under a heading like "About Rising Edge Group"? The instruction says use headings for those examples, but we can also have other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they expect those categories. We can include "About the Company" as a heading? Might be okay but not in list. Safer to include "About the role" for the description of role (What You'll Do). Then "Responsibilities" for Key Responsibilities. Then "Requirements" for Requirements and What You'll Bring combined? Could separate "Qualifications" and "Skills". But we have both degree/diploma requirement and experience, plus skills. Could split: "Qualifications" for education/experience, "Skills" for technical skills. Then "Benefits" for the Benefits section. We must not include empty sections. Ensure we preserve all substantive info. Let's extract content: Who We Are: Rising Edge Group is an electrical contracting company founded in 2002, specialization in high-voltage electrical solutions that power critical infrastructure across North America. With operations in both Canada and the United States, we partner with clients across the electrical utilities, renewable energy, and industrial sectors to design, build, and maintain the critical infrastructure systems communities and industries rely on. Driven by a clear vision to strengthen the stability, reliability, and advancement of energy infrastructure, we take pride in delivering work that matters. Guided by our STRIDE values - Safety, Teamwork, Responsibility, Integrity, Deliver, and Excellence - we foster a people focused on a culture of growth, mentorship and collaboration where safety always come first. What You'll Do: Reporting to the Construction Manager, the role of Field Engineer will play a crucial role in overseeing construction projects from the ground up. You will collaborate closely with Project Managers, Construction Managers, Quality Officers, Safety, Fleet, subcontractors, and clients to ensure work is executed safely, on schedule, and in accordance with the project specifications. This position calls for a detail-oriented and proactive individual who can effectively tackle challenges and ensure high-quality outcomes Key Responsibilities: list bullet points (the long list). We'll need to convert each line into
maybe under a heading like "Additional Information" but not in list. Could incorporate into Requirements? It's a condition, not a requirement per se. Could be its own section "Additional Information". The instruction says include a section ONLY when posting has real, specific content for it. This is specific. So we can add a heading "Additional Information". However the examples didn't list that, but it's okay to have other headings? Might be okay. Safer to fold into Requirements as a note? But it's not a requirement; it's a condition. Could be a
under Requirements heading without a list. But we need to preserve it. I'd add a heading "Additional Information" with a
. Now Benefits: we have multiple paragraphs. We'll make a
- for each benefit point? The instruction says use
- for any list of duties/requirements/benefits. So we can list each benefit as
- . We'll need to capture the prose inside each.
Let's extract each benefit:
Safety & Excellence: "Safety is at the heart of everything we do. Every project is approached with diligence, strategic planning, and reliable execution practices to protect our teams and the clients we serve while delivering world-class high-voltage solutions. Our unwavering commitment to safety and quality drives excellence on every project, every day."
People-First Culture: "You're more than a job title. Every person contributes to powering essential energy infrastructure across North America. Our teams are built on collaboration, respect, and accountability. We support our employees through meaningful engagement initiatives, team events, and a culture that prioritizes wellbeing, inclusion, and genuine lasting connections."
Career Growth & Impact: "Your role is a path to a long-term career. We empower our employees with hands-on experience, exposure to diverse projects, and opportunities to advance across disciplines, locations, and career paths. Through continuous learning, mentorship, and professional development, you'll build lasting expertise while making a tangible impact in an environment where teamwork and integrity guide our work."
Reward & Recognition: "We believe skill, dedication, and excellence deserves recognition. Competitive compensation, comprehensive benefits, and a strong culture of appreciation ensure your achievements are celebrated, your growth is supported, and your work truly makes a difference. At Rising Edge Group, you're not just building projects, you're building a meaningful career where your work helps power the future, one project at a time."
We'll include these as list items.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the Role
... (What You'll Do)
Responsibilities
- ... ...
Additional Information
As a condition of employment, candidates will be required to complete pre-employment screening including professional reference checks and a criminal record check
Requirements
- ... ...
Skills
Maybe we can split some of the requirements into Skills: Proficient in Microsoft Excel, Experience with project management software such as Aconex, Strong understanding of construction methods, materials, and safety standards, Outstanding problem-solving abilities, Excellent communication and interpersonal skills, Capability to manage multiple priorities, Willingness to travel, Possession of valid driver's license, Ability to work outdoors. But we already have them in Requirements list. Could keep all under Requirements. But we could also have Qualifications (education/experience) and Skills. However we risk creating thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine all into Requirements. That's fine. Thus we have sections: About the Role, Responsibilities, Additional Information, Requirements, Benefits. Check if any section is empty: All have content. Now we need to ensure we didn't miss any substantive info from "Who We Are". Should we include that? It's company description. Could be under "About the Company" but not required. The instruction says we can use headings for examples but not limited. However we might want to include it as a section "About the Company". But if we add another section, we increase number of sections. The instruction says prefer a few substantive sections over many thin ones. The "Who We Are" is substantive. Could we incorporate it into About the Role? Not really. Could we add a section "About the Company". That would be another heading. Might be okay but we risk many sections. However we already have 5 sections; adding another makes 6. Still not many. I'd include it as a section "About the Company". But the instruction examples didn't list that, but it's not prohibited. I'd include it to preserve all substantive info. Thus sections: About the Company, About the Role, Responsibilities, Additional Information, Requirements, Benefits. Now we need to format. Let's craft the HTML. We'll need to escape any special characters? Not needed. Now produce:About the Company
Rising Edge Group is an electrical contracting company founded in 2002, specialization in high-voltage electrical solutions that power critical infrastructure across North America. With operations in both Canada and the United States, we partner with clients across the electrical utilities, renewable energy, and industrial sectors to design, build, and maintain the critical infrastructure systems communities and industries rely on. Driven by a clear vision to strengthen the stability, reliability, and advancement of energy infrastructure, we take pride in delivering work that matters. Guided by our STRIDE values - Safety, Teamwork, Responsibility, Integrity, Deliver, and Excellence - we foster a people focused on a culture of growth, mentorship and collaboration where safety always come first.
About the Role
Reporting to the Construction Manager, the role of Field Engineer will play a crucial role in overseeing construction projects from the ground up. You will collaborate closely with Project Managers, Construction Managers, Quality Officers, Safety, Fleet, subcontractors, and clients to ensure work is executed safely, on schedule, and in accordance with the project specifications. This position calls for a detail-oriented and proactive individual who can effectively tackle challenges and ensure high-quality outcomes.
Responsibilities
- Provide technical support during the construction phase, ensuring compliance with project designs and specifications
- Review and interpret project drawings and specifications, offering feedback as necessary
- Coordinate with subcontractors to ensure proper execution of project tasks
- Support project managers in maintaining accurate documentation of project progress and challenges
- Conduct regular site inspections to monitor progress and resolve any issues that arise