Projects Engineering Architect
Y-12 National Security Complex · Oak Ridge, TN · 2 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role? The posting includes "What You'll Do" (responsibilities), "What You Can Expect" (benefits? Actually it's more about culture, maybe Benefits? but it's not explicit benefits). There's "Minimum Job Requirements", "Preferred Job Requirements", "Why Y-12?" (benefits and culture). Also location and job title given but we should not repeat job title as heading. We should not include metadata like Job ID etc. We need to include sections only when there is real specific content.
We need to decide headings: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate headings based on content.
We have:
- Responsibilities: "What You'll Do ..." includes duties. So we can have
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate headings based on content.
We have:
- Responsibilities: "What You'll Do ..." includes duties. So we can have Responsibilities
with - items.
- Requirements: Minimum Job Requirements (education, GPA, RA, DOE O 426.2A). Could be under
Requirements
.
- Preferred Job Requirements: could be under Preferred Qualifications
or Skills
. Since we have Skills heading available, we could put preferred qualifications there. But we also have "Qualifications" heading. Might be better to use "Qualifications" for minimum, and "Preferred Qualifications" maybe not in list but we can still use "Qualifications" for both? The instruction: Use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these.
We have location info but not needed as heading.
We have "What You Can Expect" which describes benefits and culture: could be Benefits section.
We have "Why Y-12?" which also describes benefits: medical plan etc. Could also be Benefits.
We have no explicit Pay or Schedule info, so we should not create those sections.
We have no explicit "About the role" summary separate from responsibilities; but we could use "About the role" for a brief overview paragraph (maybe first paragraph). However we must not create filler. The posting starts with location and job title then "What You'll Do". There's no separate "About the role". But we could still include an "About the role" paragraph summarizing the role from the first sentences? That might be considered summarizing but we can extract a short prose from the description: "As an projects engineering architect, the candidate will be responsible for developing high-quality architectural design packages and conceptual planning efforts for Projects Engineering." That is essentially part of responsibilities. Might be okay to put that as About the role.
But we need to avoid duplication. Perhaps better: Use "About the role" for a short paragraph summarizing the role (maybe first sentence). Then "Responsibilities" for the detailed list.
Let's extract responsibilities list:
From "What You'll Do As an projects engineering architect, the candidate will be responsible for developing high-quality architectural design packages and conceptual planning efforts for Projects Engineering. The candidate will also provide technical assessments, studies, programming, code reviews, MicroStation CAD work, oversight and review of outside AE designs, field work, preparation of equipment layouts and floor plans and equipment travel paths. The candidate will cooperatively work as a member of integrated project teams with the Project Engineer, other disciplines, outside contractors, construction forces, architecture engineering firms, customers and management. The successful candidate must apply an understanding of technical principles, theories and concepts in architecture. Provide technical solutions to a wide range of problems through design and design reviews. Architecture and design work will primarily focus on industrial buildings, project planning and oversight, equipment installations, building modifications, and roofing maintenance packages. The employee will be required to comply with Government, Company and departmental policy, procedures and requirements. Duties also include developing and implementing improvements to the department processes and references. This position requires self-motivation and skills in understanding and application of technical principles, theories, and concepts in the architectural field. Working knowledge of other related engineering disciplines and how those disciplines interface with architectural systems is also required."
We can break into bullet points.
Now Minimum Job Requirements:
- Bachelor of Architecture degree from an NAAB accredited school. OR Master of Architecture degree from an NAAB accredited school.
- Minimum GPA requirement up to 4 years post-graduation at time of offer and confirmed by transcript. Beyond four years from graduation, engineering experience will supersede GPA as a requirement for hire.
- 3.0/4.0 minimum cumulative GPA for Bachelor's degree. 3.3 minimum cumulative GPA for Master's degree.
- Being a Registered Architect (RA) or the ability to become an RA within 4 years is required.
- In addition, the applicant must meet the requirements of DOE O 426.2A (i.e., Baccalaureate in engineering or related scientific major 2 years job-related, and 1-year nuclear experience; or a DOE O 426.2A alternative). DOE 426.2A experience requirements can be satisfied following employment. In the interim, newly hired personnel will not be assigned duties that could impact the safety basis of nuclear facilities. (Ref. DOE O 426.2A)
We can list these as bullet points.
Preferred Job Requirements:
- Knowledge of related engineering disciplines
- Knowledge of architectural systems, applications of architectural and construction methods and materials, and application of computers
- Knowledge of industry regulatory standards and design criteria pertinent to various engineering and architecture disciplines
- Skills in effective planning, writing, organization, communication, schedule compliance, and design management
- Computer-literate and have good working knowledge of software tools that support architectural design activities including computer-aided design
- Ability to prepare, read, and/or interpret complex engineering/architecture drawings
- Ability to conduct formal presentations to plant personnel and other interested parties
- Ability to review projects for technical accuracy
- Ability to present information clearly and effectively through the oral and written word
We can put these under Skills heading.
Benefits: from "What You Can Expect" and "Why Y-12?":
What You Can Expect:
- Meaningful work and unique opportunities to support missions vital to national and global security
- Top-notch, dedicated colleagues
- Generous pay and benefits with a stable organization
- Career advancement and professional development programs
- Work-life balance fostered through flexible work options and wellness initiatives
Why Y-12?:
- You get #morethanajob. We encourage employees to achieve a healthy personal balance among home, work and the community.
- One of the ways we embrace work-life balance is by offering flexible work arrangements that provide alternatives to the traditional workweek, while still meeting business needs.
- Top talent and personal commitment mean more to our success than any other factors, so we reward our people with the kinds of benefits that make a positive difference in the quality of their lives.
- Benefits such as: medical plan, prescription drug plan, vision plan, dental plan, employer matched 401(k) savings plan, disability coverage, education reimbursement and many more.
- Want to stay healthy and fit but hate the cost of a gym membership? Take advantage of one of our onsite workout facilities and eat healthy in our onsite cafeterias.
- Much more than a workplace, at Y-12, you can build a career that lasts a lifetime.
We can combine into Benefits section bullet list.
We should not include Pay or Schedule sections because no explicit numbers.
We should not include About the role if we think it's redundant; but we could include a short paragraph summarizing role from first sentence. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine About the role and Responsibilities into one Responsibilities section? But we need to follow headings list; we can omit About the role if no specific content beyond responsibilities. The posting does not have a separate "About the role" paragraph; it's just the responsibilities. So we can skip About the role.
Thus sections: Responsibilities, Requirements, Skills, Benefits.
We need to output only HTML fragment, no /, no markdown.
We'll produce:
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Make sure to preserve all substantive information; not invent or summarize away detail. We need to keep details like specific software (MicroStation CAD), specific DOE O 426.2A details, etc.
We need to be careful not to include boilerplate like EEO, drug-free workplace, etc. The instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must exclude the EEO statements at the end, the drug-free workplace, clearance requirements, etc. Those are considered boilerplate? The instructions say remove EEO/equal-opportunity/scam-warning boilerplate. The posting includes a lot of clearance and security requirements, drug testing, etc. Those might be considered legal/boilerplate? They are not EEO but are security clearance requirements. The instruction didn't explicitly say to remove security clearance info, but they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The security clearance info might be considered legal? It's about DOE clearance, Q clearance, etc. Might be considered legal. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So legal boilerplate includes things like clearance requirements, drug testing, background investigation, etc. So we should exclude those. Also the "Notes" section about career level, Q clearance, etc. Should be removed.
Thus we should not include any of the Notes, clearance, drug testing, EEO, etc.
We must preserve all substantive information about job duties, requirements, preferred qualifications, benefits. So we keep those.
Now let's craft the bullet lists.
Responsibilities bullets:
- Developing high-quality architectural design packages and conceptual planning efforts for Projects Engineering.
- Providing technical assessments, studies, programming, code reviews, MicroStation CAD work.
- Oversight and review of outside AE designs.
- Field work, preparation of equipment layouts and floor plans and equipment travel paths.
- Working as a member of integrated project teams with the Project Engineer, other disciplines, outside contractors, construction forces, architecture engineering firms, customers and management.
- Applying understanding of technical principles, theories and concepts in architecture.
- Providing technical solutions to a wide range of problems through design and design reviews.
- Focusing architecture and design work on industrial buildings, project planning and oversight, equipment installations, building modifications, and roofing maintenance packages.
- Complying with Government, Company and departmental policy, procedures and requirements.
- Developing and implementing improvements to department processes and references.
- Requiring self-motivation and skills in understanding and application of technical principles, theories, and concepts in the architectural field.
- Requiring working knowledge of other related engineering disciplines and how those disciplines interface with architectural systems.
We could combine some but keep each as bullet.
Requirements bullets:
- Bachelor of Architecture degree from an NAAB accredited school, OR Master of Architecture degree from an NAAB accredited school.
- Minimum GPA requirement: up to 4 years post-graduation, confirmed by transcript; beyond four years, engineering experience supersedes GPA.
- 3.0/4.0 minimum cumulative GPA for Bachelor's degree; 3.3 minimum cumulative GPA for Master's degree.
- Being a Registered Architect (RA) or ability to become an RA within 4 years required.
- Must meet DOE O 426.2A requirements (Baccalaureate in engineering or related scientific major with 2 years job-related experience and 1-year nuclear experience, or a DOE O 426.2A alternative); experience can be satisfied following employment, with new hires not assigned duties impacting nuclear facility safety basis until requirements
Requirements
. - Preferred Job Requirements: could be underPreferred Qualifications
orSkills
. Since we have Skills heading available, we could put preferred qualifications there. But we also have "Qualifications" heading. Might be better to use "Qualifications" for minimum, and "Preferred Qualifications" maybe not in list but we can still use "Qualifications" for both? The instruction: Use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have location info but not needed as heading. We have "What You Can Expect" which describes benefits and culture: could be Benefits section. We have "Why Y-12?" which also describes benefits: medical plan etc. Could also be Benefits. We have no explicit Pay or Schedule info, so we should not create those sections. We have no explicit "About the role" summary separate from responsibilities; but we could use "About the role" for a brief overview paragraph (maybe first paragraph). However we must not create filler. The posting starts with location and job title then "What You'll Do". There's no separate "About the role". But we could still include an "About the role" paragraph summarizing the role from the first sentences? That might be considered summarizing but we can extract a short prose from the description: "As an projects engineering architect, the candidate will be responsible for developing high-quality architectural design packages and conceptual planning efforts for Projects Engineering." That is essentially part of responsibilities. Might be okay to put that as About the role. But we need to avoid duplication. Perhaps better: Use "About the role" for a short paragraph summarizing the role (maybe first sentence). Then "Responsibilities" for the detailed list. Let's extract responsibilities list: From "What You'll Do As an projects engineering architect, the candidate will be responsible for developing high-quality architectural design packages and conceptual planning efforts for Projects Engineering. The candidate will also provide technical assessments, studies, programming, code reviews, MicroStation CAD work, oversight and review of outside AE designs, field work, preparation of equipment layouts and floor plans and equipment travel paths. The candidate will cooperatively work as a member of integrated project teams with the Project Engineer, other disciplines, outside contractors, construction forces, architecture engineering firms, customers and management. The successful candidate must apply an understanding of technical principles, theories and concepts in architecture. Provide technical solutions to a wide range of problems through design and design reviews. Architecture and design work will primarily focus on industrial buildings, project planning and oversight, equipment installations, building modifications, and roofing maintenance packages. The employee will be required to comply with Government, Company and departmental policy, procedures and requirements. Duties also include developing and implementing improvements to the department processes and references. This position requires self-motivation and skills in understanding and application of technical principles, theories, and concepts in the architectural field. Working knowledge of other related engineering disciplines and how those disciplines interface with architectural systems is also required." We can break into bullet points. Now Minimum Job Requirements: - Bachelor of Architecture degree from an NAAB accredited school. OR Master of Architecture degree from an NAAB accredited school. - Minimum GPA requirement up to 4 years post-graduation at time of offer and confirmed by transcript. Beyond four years from graduation, engineering experience will supersede GPA as a requirement for hire. - 3.0/4.0 minimum cumulative GPA for Bachelor's degree. 3.3 minimum cumulative GPA for Master's degree. - Being a Registered Architect (RA) or the ability to become an RA within 4 years is required. - In addition, the applicant must meet the requirements of DOE O 426.2A (i.e., Baccalaureate in engineering or related scientific major 2 years job-related, and 1-year nuclear experience; or a DOE O 426.2A alternative). DOE 426.2A experience requirements can be satisfied following employment. In the interim, newly hired personnel will not be assigned duties that could impact the safety basis of nuclear facilities. (Ref. DOE O 426.2A) We can list these as bullet points. Preferred Job Requirements: - Knowledge of related engineering disciplines - Knowledge of architectural systems, applications of architectural and construction methods and materials, and application of computers - Knowledge of industry regulatory standards and design criteria pertinent to various engineering and architecture disciplines - Skills in effective planning, writing, organization, communication, schedule compliance, and design management - Computer-literate and have good working knowledge of software tools that support architectural design activities including computer-aided design - Ability to prepare, read, and/or interpret complex engineering/architecture drawings - Ability to conduct formal presentations to plant personnel and other interested parties - Ability to review projects for technical accuracy - Ability to present information clearly and effectively through the oral and written word We can put these under Skills heading. Benefits: from "What You Can Expect" and "Why Y-12?": What You Can Expect: - Meaningful work and unique opportunities to support missions vital to national and global security - Top-notch, dedicated colleagues - Generous pay and benefits with a stable organization - Career advancement and professional development programs - Work-life balance fostered through flexible work options and wellness initiatives Why Y-12?: - You get #morethanajob. We encourage employees to achieve a healthy personal balance among home, work and the community. - One of the ways we embrace work-life balance is by offering flexible work arrangements that provide alternatives to the traditional workweek, while still meeting business needs. - Top talent and personal commitment mean more to our success than any other factors, so we reward our people with the kinds of benefits that make a positive difference in the quality of their lives. - Benefits such as: medical plan, prescription drug plan, vision plan, dental plan, employer matched 401(k) savings plan, disability coverage, education reimbursement and many more. - Want to stay healthy and fit but hate the cost of a gym membership? Take advantage of one of our onsite workout facilities and eat healthy in our onsite cafeterias. - Much more than a workplace, at Y-12, you can build a career that lasts a lifetime. We can combine into Benefits section bullet list. We should not include Pay or Schedule sections because no explicit numbers. We should not include About the role if we think it's redundant; but we could include a short paragraph summarizing role from first sentence. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine About the role and Responsibilities into one Responsibilities section? But we need to follow headings list; we can omit About the role if no specific content beyond responsibilities. The posting does not have a separate "About the role" paragraph; it's just the responsibilities. So we can skip About the role. Thus sections: Responsibilities, Requirements, Skills, Benefits. We need to output only HTML fragment, no /, no markdown. We'll produce:Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...