Software Engineering Specialist - Signals & Communications
Burns Engineering, Inc. · Pittsburgh, PA · 4 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Burns" description, then "Summary", "Essential Job Responsibilities", "Education Requirements", "Experience Requirements", "Certification Or License Requirements", "Preferred Experience". Also maybe "Supervisory Responsibilities". We need to use for section headings. Do not repeat job title. Do not include Job ID etc. Remove boilerplate like EEO, privacy notice, etc. Also remove duplicated lines. Must preserve all substantive info.
We need to decide which sections to include: About Burns (company description) maybe as a paragraph before sections? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to be safe we can include a heading "About the company" maybe not in list. But they said "e.g." meaning examples, not exhaustive. So we could add a heading "About Burns". However they might expect only those headings. Safer to follow examples: Use "About the role" for summary of role and maybe include company description there? Could combine.
Better: Use
for section headings. Do not repeat job title. Do not include Job ID etc. Remove boilerplate like EEO, privacy notice, etc. Also remove duplicated lines. Must preserve all substantive info.
We need to decide which sections to include: About Burns (company description) maybe as a paragraph before sections? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also have other headings if content matches? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those typical headings. But we can also include other headings if needed? Probably they want to map content to those headings. For example: "About Burns" could be "About the role"? Actually "About the role" is a summary of the role. The posting has "Summary". That could be placed under About the role
. Then responsibilities under Responsibilities
. Education and experience under Requirements
or Qualifications
. Preferred experience could be Skills
. Certification Or License Requirements maybe under Requirements as well. Supervisory responsibilities maybe under Responsibilities.
We must not create sections with filler like "Pay", "Schedule", "Benefits" if not present. The posting does not mention pay, schedule, benefits. So we omit those sections.
We must not repeat job title. The job title is "Software Engineering Specialist". Not to be used as heading.
We must preserve all substantive information. So we need to include the company description (About Burns) maybe as a paragraph before sections? The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Probably they expect we use those headings for the sections we have. The company description could be placed under About the role
? But that is more about the role, not company. However we could treat "About Burns" as a paragraph before any heading, maybe as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those typical headings. But we can also include other headings if needed? Probably they want to map content to those headings. For example: "About Burns" could be "About the role"? Actually "About the role" is a summary of the role. The posting has "Summary". That could be placed under About the role
. Then responsibilities under Responsibilities
. Education and experience under Requirements
or Qualifications
. Preferred experience could be Skills
. Certification Or License Requirements maybe under Requirements as well. Supervisory responsibilities maybe under Responsibilities.
We must not create sections with filler like "Pay", "Schedule", "Benefits" if not present. The posting does not mention pay, schedule, benefits. So we omit those sections.
We must not repeat job title. The job title is "Software Engineering Specialist". Not to be used as heading.
We must preserve all substantive information. So we need to include the company description (About Burns) maybe as a paragraph before sections? The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Probably they expect we use those headings for the sections we have. The company description could be placed under About the role
? But that is more about the role, not company. However we could treat "About Burns" as a paragraph before any heading, maybe as a
About the role
? But that is more about the role, not company. However we could treat "About Burns" as a paragraph before any heading, maybe as a. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to be safe we can include a heading "About the company" maybe not in list. But they said "e.g." meaning examples, not exhaustive. So we could add a heading "About Burns". However they might expect only those headings. Safer to follow examples: Use "About the role" for summary of role and maybe include company description there? Could combine.
Better: Use About the role
for the Summary paragraph (the role summary). Then maybe a separate About Burns
not in examples but okay. But risk.
Let's read instruction again: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests they want those headings if applicable. It doesn't forbid other headings, but they gave examples. I'd stick to those headings for clarity.
Thus we need to map content:
- About the role: Could include the summary paragraph: "The Engineering Specialist will be responsible for performing technical engineering tasks, technical studies and investigations, and designs on assigned solar projects, while also supporting both small and large-scale Battery Energy Storage System (BESS) initiatives. The Engineering Specialist will be mentored by senior level engineering staff, will work with more autonomy, and will complete engineering tasks of moderate complexity."
- Responsibilities: The long list of essential job responsibilities (including supervisory responsibilities). We'll put them in - .
- Requirements: Could include Education Requirements, Experience Requirements, Certification Or License Requirements. Possibly combine.
- Qualifications: Could include Preferred Experience (skills). Or we could treat Preferred Experience as Skills.
- Skills: Could include the bullet points under Preferred Experience.
We must not create sections with filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO, California Privacy Notice, etc.
Also remove duplicated lines: The posting repeats "Consult with senior technical staff when needed." many times; we should keep each occurrence? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep each bullet as is, even if repeated. However we can combine duplicates? That would be summarizing away detail. So we must keep each line as appears. However we can format as list items; duplicates will appear multiple times.
We need to extract the responsibilities list exactly as in the posting. Let's copy the responsibilities section:
"Essential Job Responsibilities Complete discipline specific engineering for systems and designs of moderate complexity.Sign and seal engineering drawings.Assist in developing design approaches and concepts on projects with moderate complexity. Consult with senior technical staff when needed.Assist in the development of proposals and presentations to clients.Perform specific engineering studies and design analyses and assist the Project Manager in establishing budgets, cost estimates, and project schedules.Review drawings, RFIs, and records of changes and communicate directly with suppliers, contractors, and client representatives as required. Consult with senior technical staff when needed.Perform on-site surveys and inspections during design and construction stages and issue written reports noting deficiencies. Consult with senior technical staff when needed.Assist in the coordination of project designs with other disciplines and teams.Attend client and/or project meetings when requested.Write technical specifications with oversight from senior technical staff.Assist Project Manager with the delegation, collaboration, and review of project work tasks of CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates.May lead development of design approaches and concepts on projects of low complexity. Consult with senior technical staff when needed.Perform all tasks in compliance with Burns (and, when applicable, a client’s) standards, policies, procedures, and engineering codes.Perform all tasks efficiently, accurately, within the allotted project hours, and complete tasks on or before the due date.Observe, understand, apply and retain Burns technical policies, procedures, design analyses, calculations, engineering methodology and codes, and equipment selection criteria of low to moderate complexity.Complete special tasks as assigned. SUPERVISORY RESPONISBILTIES No formal supervisory responsibilities. Under the oversight of the Project Manager, the Engineering Specialist may provide direction to CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates."
We need to split into sensible list items. The original text has no punctuation between items; we need to infer where each responsibility ends. Usually each sentence ends with a period. Let's split by periods.
I'll rewrite each sentence as a list item.
Sentences:
1. Complete discipline specific engineering for systems and designs of moderate complexity.
2. Sign and seal engineering drawings.
3. Assist in developing design approaches and concepts on projects with moderate complexity.
4. Consult with senior technical staff when needed.
5. Assist in the development of proposals and presentations to clients.
6. Perform specific engineering studies and design analyses and assist the Project Manager in establishing budgets, cost estimates, and project schedules.
7. Review drawings, RFIs, and records of changes and communicate directly with suppliers, contractors, and client representatives as required.
8. Consult with senior technical staff when needed.
9. Perform on-site surveys and inspections during design and construction stages and issue written reports noting deficiencies.
10. Consult with senior technical staff when needed.
11. Assist in the coordination of project designs with other disciplines and teams.
12. Attend client and/or project meetings when requested.
13. Write technical specifications with oversight from senior technical staff.
14. Assist Project Manager with the delegation, collaboration, and review of project work tasks of CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates.
15. May lead development of design approaches and concepts on projects of low complexity.
16. Consult with senior technical staff when needed.
17. Perform all tasks in compliance with Burns (and, when applicable, a client’s) standards, policies, procedures, and engineering codes.
18. Perform all tasks efficiently, accurately, within the allotted project hours, and complete tasks on or before the due date.
19. Observe, understand, apply and retain Burns technical policies, procedures, design analyses, calculations, engineering methodology and codes, and equipment selection criteria of low to moderate complexity.
20. Complete special tasks as assigned.
21. SUPERVISORY RESPONISBILTIES No formal supervisory responsibilities.
22. Under the oversight of the Project Manager, the Engineering Specialist may provide direction to CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates.
Note: "SUPERVISORY RESPONISBILTIES" is a heading; we can treat as a sentence.
We'll keep them as list items.
Now Education Requirements: "Bachelor’s degree (B.S.) in Computer Science or Computer Engineering from an accredited four-year college or university, or a combination of relevant education and equivalent engineering experience."
Experience Requirements: "3-5 years of relevant experiencePrevious software work in the rail sectorExperience with ACSES PTC or CBTCExperience with Python, C or C++"
Note there is no spacing; we need to split: "3-5 years of relevant experience", "Previous software work in the rail sector", "Experience with ACSES PTC or CBTC", "Experience with Python, C or C++". We'll make list items.
Certification Or License Requirements: "N/A" - we should not create a section if it's just N/A? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So we should not include a section for Certification Or License Requirements if it's just N/A. So we omit that section.
Preferred Experience: list of bullet points:
- Progressive engineering experience working on tasks of moderate complexity.
- Strong knowledge in the use of engineering design software such as AutoCAD or Revit and other specialized design software as required.
- Strong critical thinking skills and the ability to solve problems of moderate complexity with minimum supervision from leaders or management.
- Progressive ability to perform technical calculations.
- Ability to research and interpret engineering discipline codes and standards.
- Ability to multi-task, organize, and prioritize work
- Ability to prioritize tasks, work on multiple assignments and manage changing assignments in a team environment.
- Proactive, good communicator (oral and written), and strong analytical and problem-solving skills to trouble shoot and assess key issues to address.
- Ability to collaborate, build relationships and work effectively with a team.
- Previous experience in consulting is highly preferred.
We'll put these under
Skills
maybe.
Now About Burns description: The initial paragraph about Burns Engineering. We'll put that under About the role
? Actually About the role is for role summary. But we have also a separate summary paragraph. Could combine company description under About the role? Might be odd. Perhaps we can add a heading "About Burns" even if not in examples; but risk. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It
- .
- Requirements: Could include Education Requirements, Experience Requirements, Certification Or License Requirements. Possibly combine.
- Qualifications: Could include Preferred Experience (skills). Or we could treat Preferred Experience as Skills.
- Skills: Could include the bullet points under Preferred Experience.
We must not create sections with filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO, California Privacy Notice, etc.
Also remove duplicated lines: The posting repeats "Consult with senior technical staff when needed." many times; we should keep each occurrence? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep each bullet as is, even if repeated. However we can combine duplicates? That would be summarizing away detail. So we must keep each line as appears. However we can format as list items; duplicates will appear multiple times.
We need to extract the responsibilities list exactly as in the posting. Let's copy the responsibilities section:
"Essential Job Responsibilities Complete discipline specific engineering for systems and designs of moderate complexity.Sign and seal engineering drawings.Assist in developing design approaches and concepts on projects with moderate complexity. Consult with senior technical staff when needed.Assist in the development of proposals and presentations to clients.Perform specific engineering studies and design analyses and assist the Project Manager in establishing budgets, cost estimates, and project schedules.Review drawings, RFIs, and records of changes and communicate directly with suppliers, contractors, and client representatives as required. Consult with senior technical staff when needed.Perform on-site surveys and inspections during design and construction stages and issue written reports noting deficiencies. Consult with senior technical staff when needed.Assist in the coordination of project designs with other disciplines and teams.Attend client and/or project meetings when requested.Write technical specifications with oversight from senior technical staff.Assist Project Manager with the delegation, collaboration, and review of project work tasks of CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates.May lead development of design approaches and concepts on projects of low complexity. Consult with senior technical staff when needed.Perform all tasks in compliance with Burns (and, when applicable, a client’s) standards, policies, procedures, and engineering codes.Perform all tasks efficiently, accurately, within the allotted project hours, and complete tasks on or before the due date.Observe, understand, apply and retain Burns technical policies, procedures, design analyses, calculations, engineering methodology and codes, and equipment selection criteria of low to moderate complexity.Complete special tasks as assigned. SUPERVISORY RESPONISBILTIES No formal supervisory responsibilities. Under the oversight of the Project Manager, the Engineering Specialist may provide direction to CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates."
We need to split into sensible list items. The original text has no punctuation between items; we need to infer where each responsibility ends. Usually each sentence ends with a period. Let's split by periods.
I'll rewrite each sentence as a list item.
Sentences:
1. Complete discipline specific engineering for systems and designs of moderate complexity.
2. Sign and seal engineering drawings.
3. Assist in developing design approaches and concepts on projects with moderate complexity.
4. Consult with senior technical staff when needed.
5. Assist in the development of proposals and presentations to clients.
6. Perform specific engineering studies and design analyses and assist the Project Manager in establishing budgets, cost estimates, and project schedules.
7. Review drawings, RFIs, and records of changes and communicate directly with suppliers, contractors, and client representatives as required.
8. Consult with senior technical staff when needed.
9. Perform on-site surveys and inspections during design and construction stages and issue written reports noting deficiencies.
10. Consult with senior technical staff when needed.
11. Assist in the coordination of project designs with other disciplines and teams.
12. Attend client and/or project meetings when requested.
13. Write technical specifications with oversight from senior technical staff.
14. Assist Project Manager with the delegation, collaboration, and review of project work tasks of CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates.
15. May lead development of design approaches and concepts on projects of low complexity.
16. Consult with senior technical staff when needed.
17. Perform all tasks in compliance with Burns (and, when applicable, a client’s) standards, policies, procedures, and engineering codes.
18. Perform all tasks efficiently, accurately, within the allotted project hours, and complete tasks on or before the due date.
19. Observe, understand, apply and retain Burns technical policies, procedures, design analyses, calculations, engineering methodology and codes, and equipment selection criteria of low to moderate complexity.
20. Complete special tasks as assigned.
21. SUPERVISORY RESPONISBILTIES No formal supervisory responsibilities.
22. Under the oversight of the Project Manager, the Engineering Specialist may provide direction to CAD Operators, CAD Technicians, Designers, Co-Ops, Interns, Engineering Design Associates, and Engineering Associates.
Note: "SUPERVISORY RESPONISBILTIES" is a heading; we can treat as a sentence.
We'll keep them as list items.
Now Education Requirements: "Bachelor’s degree (B.S.) in Computer Science or Computer Engineering from an accredited four-year college or university, or a combination of relevant education and equivalent engineering experience."
Experience Requirements: "3-5 years of relevant experiencePrevious software work in the rail sectorExperience with ACSES PTC or CBTCExperience with Python, C or C++"
Note there is no spacing; we need to split: "3-5 years of relevant experience", "Previous software work in the rail sector", "Experience with ACSES PTC or CBTC", "Experience with Python, C or C++". We'll make list items.
Certification Or License Requirements: "N/A" - we should not create a section if it's just N/A? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So we should not include a section for Certification Or License Requirements if it's just N/A. So we omit that section.
Preferred Experience: list of bullet points:
- Progressive engineering experience working on tasks of moderate complexity.
- Strong knowledge in the use of engineering design software such as AutoCAD or Revit and other specialized design software as required.
- Strong critical thinking skills and the ability to solve problems of moderate complexity with minimum supervision from leaders or management.
- Progressive ability to perform technical calculations.
- Ability to research and interpret engineering discipline codes and standards.
- Ability to multi-task, organize, and prioritize work
- Ability to prioritize tasks, work on multiple assignments and manage changing assignments in a team environment.
- Proactive, good communicator (oral and written), and strong analytical and problem-solving skills to trouble shoot and assess key issues to address.
- Ability to collaborate, build relationships and work effectively with a team.
- Previous experience in consulting is highly preferred.
We'll put these under
Skills
maybe. Now About Burns description: The initial paragraph about Burns Engineering. We'll put that underAbout the role
? Actually About the role is for role summary. But we have also a separate summary paragraph. Could combine company description under About the role? Might be odd. Perhaps we can add a heading "About Burns" even if not in examples; but risk. However the instruction says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It