Senior Architect
enGen · United States · 1 mo ago
RemoteRemoteArt & Creative$103k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes JOB SUMMARY, ESSENTIAL RESPONSIBILITIES, EDUCATION, EXPERIENCE, LICENSES AND CERTIFICATIONS, SKILLS, Additional Skills, Language, Travel Requirement, PHYSICAL, MENTAL DEMANDS and WORKING CONDITIONS, Pay Range, etc.
We must use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
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. 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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- JOB SUMMARY: includes US Citizen requirement, lead role description. Could be "About the role" or "Job Summary". Use
About the role
with prose.
- ESSENTIAL RESPONSIBILITIES: long list of duties. Use Responsibilities
with - each bullet.
- EDUCATION: Required Bachelor's Degree..., Preferred Master's Degree. Could be under "Qualifications" or "Education". The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Qualifications" for education and experience? Or separate sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose among those. We need to include sections only if there is real content. We have education, experience, licenses/certifications, skills, travel requirement, physical demands, pay range.
We could combine education, experience, licenses/certifications into "Qualifications". Or we could have separate sections: "Education", "Experience", "Licenses and Certifications", "Skills". But the allowed headings list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Education or Experience explicitly, but we could use "Qualifications" to cover education, experience, licenses/certs. Or we could use "Requirements" for education/experience/licenses. The instruction says e.g., not exhaustive. So we can use other headings if appropriate? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where applicable. So we can have:
- About the role (job summary)
- Responsibilities (essential responsibilities)
- Qualifications (education, experience, licenses/certs)
- Skills (skills list)
- Pay (pay range)
- Schedule? Not given. Travel requirement is 0%-25% travel. That's not schedule but maybe we could include under "Schedule"? Not exactly. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Travel requirement is not schedule; maybe we could include under "About the role" or a separate "Travel" but not allowed headings. Could fold into Qualifications? Probably better to include a short paragraph under About the role or Qualifications about travel requirement.
Physical demands etc: could be omitted? It's substantive but not in allowed headings. Could we create a section "Working Conditions"? Not in list but maybe allowed as e.g., not limited. The instruction says e.g., not exhaustive. So we could add a section "Working Conditions". But they said prefer a few substantive sections over many thin ones. Might combine physical demands into Qualifications? Not ideal.
Better to follow the instruction: Use headings from the list where appropriate. For physical demands, maybe we can omit because not in list? But we must preserve ALL substantive information. So we need to include it somewhere. Could add a section "Working Conditions" as a heading (though not in the example list). The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. But they also say prefer a few substantive sections over many thin ones. So we could combine physical demands and travel into a "Working Conditions" section.
Thus sections:
- About the role (job summary)
- Responsibilities
- Qualifications (education, experience, licenses/certs, maybe also skills? but skills separate)
- Skills
- Working Conditions (physical demands, travel requirement)
- Pay (pay range)
We must not include Benefits if not stated. There's no benefits mentioned. So omit.
Now we need to extract content.
Job Summary: "Company enGen Job Description JOB SUMMARY CANDIDATE MUST BE US Citizen (due to contractual/access requirements)*** This job takes a lead role, within area of responsibility, and (application, solution, information, technology, business) designs, develops, implements, supports, and optimizes more complex architecture strategy to meet business capabilities and needs. Takes a lead role to ensure completeness of more complex architecture by adequately addressing all the pertinent concerns of its stakeholders. Ensures integrity of more complex architecture by connecting various views of stakeholders, reconciling conflicting concerns, and showing the trade-offs made in so doing. Considers practicality and fitness for purpose in determining architecture to develop. Leverages business and technology knowledge to enable and/or alter business processes, practices, organizations and systems. Maintains knowledge of emerging technologies and best in class industry business trends and practices. May take on role of Project Lead for special assignments. May mentor less experienced team members."
We need to preserve all substantive info. Remove boilerplate like "Company enGen Job Description". Keep the summary.
We'll output About the role
...
Responsibilities: The long list starting with "ESSENTIAL RESPONSIBILITIES". We need to break into bullet points. The text is a run-on sentences separated by periods. We can split each sentence into a bullet. Must preserve all info. We'll create - each sentence.
We need to be careful not to lose any content. Let's copy the responsibilities text exactly as given (excluding the heading). It starts after "ESSENTIAL RESPONSIBILITIES". The text:
"Take a lead role to provide strategic consultation to business customers in defining or designing more complex business processes, functions and organizational structures, as well as in researching, identifying and internally marketing enabling technologies based on customer capability requirements. Facilitate development of more complex enterprise business solutions that combine knowledge of particular business processes and issues, general technological options, and process facilitation techniques. Participate in more complex enterprise strategy development, including environmental analysis, opportunity identification, value cases and business innovation portfolio development.Take a lead role to specify and design large or more complex systems, solutions, networks, infrastructure elements, or processes. Select appropriate design standards, methods and tools and ensure that they are applied effectively. Review others’ system design to ensure selection of appropriate technology, efficient use of resources and integration of multiple systems and technology. Establish policy for selection of more complex architecture components. Evaluate and undertake impact analysis on more complex major design options. Ensure that the system architecture balances functional, service quality and systems management requirements.Use appropriate tools, including models of components and interfaces, to contribute to the development of more complex architectures. Take a lead role to produce detailed component requirements, specifications and translates these into detailed solutions/designs for implementation using selected products. Provide advice on technical aspects of system development, integration (including requests for changes, deviations from specifications, etc.) and processes. Ensure that relevant technical and business strategies, policies, standards and practices are applied correctly.Select and use more complex tools and methods to establish, clarify, and communicate the functional and non-functional requirements of system users, their characteristics, and tasks. Take a lead role to identify the technical, organizational, and physical environment in which more complex products or systems will operate. Identify, propose, initiate, and lead significant improvement programs, taking responsibility for the quality and appropriateness of the work performed and the realization of measurable business benefits. Modify existing process improvement approaches and/or develop new approaches to achieve improvement.Take a lead role to ensure the resolution of a variety of more complex architecture and business problems and serve as a technical or business lead for highly complex project initiatives.Communicate effectively will all levels of organization.Manage expectations of customers, partners and management.Participate in customer walkthroughs and plans; design and technical walkthroughs; and problem resolution and decision making.Interact with departments across the organization as necessary, including the development and interpretation of highly complex requirements for peers and other staff.Maintain an in-depth knowledge of specific technical aspects in area of expertise and provides expert advice regarding their application. The area of specific expertise may be any aspect of information or communication technology, technique, method, process, product, or application area of a more complex nature.Take a lead role in providing leadership and mentoring in the areas of expertise and architecture to their peers, developers, management and business users including technical expertise, coaching, and ad-hoc training by preparing presentations on more complex issues on the area of expertise and presenting to their peers to ensure consistency to the Organization's strategic direction.Other duties as assigned or requested."
We need to split into sentences. Note some sentences lack spaces after periods (e.g., "development.Take"). We'll handle by splitting at periods followed by space or capital letter? For simplicity, we can manually split where we see a period and then a capital letter or start of new sentence. We'll produce bullet points accordingly.
Let's list them:
1. Take a lead role to provide strategic consultation to business customers in defining or designing more complex business processes, functions and organizational structures, as well as in researching, identifying and internally marketing enabling technologies based on customer capability requirements.
2. Facilitate development of more complex enterprise business solutions that combine knowledge of particular business processes and issues, general technological options, and process facilitation techniques.
3. Participate in more complex enterprise strategy development, including environmental analysis, opportunity identification, value cases and business innovation portfolio development.
4. Take a lead role to specify and design large or more complex systems, solutions, networks, infrastructure elements, or processes.
5. Select appropriate design standards, methods and tools and ensure that they are applied effectively.
6. Review others’ system design to ensure selection of appropriate technology, efficient use of resources and integration of multiple systems and technology.
7. Establish policy for selection of more complex architecture components.
8. Evaluate and undertake impact analysis on more complex major design options.
9. Ensure that the system architecture balances functional, service quality and systems management requirements.
10. Use appropriate tools, including models of components and interfaces, to contribute to the development of more complex architectures.
11. Take a lead role to produce detailed component requirements, specifications and translates these into detailed solutions/designs for implementation using selected products.
12. Provide advice on technical aspects of system development, integration (including requests for changes, deviations from specifications, etc.) and processes.
13. Ensure that relevant technical and business strategies, policies, standards and practices are applied correctly.
14. Select and use more complex tools and methods to establish, clarify, and communicate the functional and non-functional requirements of system users, their characteristics, and tasks.
15. Take a lead
for prose. Do NOT repeat the job title as a heading. 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - JOB SUMMARY: includes US Citizen requirement, lead role description. Could be "About the role" or "Job Summary". Use
About the role
with prose. - ESSENTIAL RESPONSIBILITIES: long list of duties. UseResponsibilities
with- each bullet.
- EDUCATION: Required Bachelor's Degree..., Preferred Master's Degree. Could be under "Qualifications" or "Education". The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Qualifications" for education and experience? Or separate sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose among those. We need to include sections only if there is real content. We have education, experience, licenses/certifications, skills, travel requirement, physical demands, pay range. We could combine education, experience, licenses/certifications into "Qualifications". Or we could have separate sections: "Education", "Experience", "Licenses and Certifications", "Skills". But the allowed headings list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Education or Experience explicitly, but we could use "Qualifications" to cover education, experience, licenses/certs. Or we could use "Requirements" for education/experience/licenses. The instruction says e.g., not exhaustive. So we can use other headings if appropriate? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where applicable. So we can have: - About the role (job summary) - Responsibilities (essential responsibilities) - Qualifications (education, experience, licenses/certs) - Skills (skills list) - Pay (pay range) - Schedule? Not given. Travel requirement is 0%-25% travel. That's not schedule but maybe we could include under "Schedule"? Not exactly. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Travel requirement is not schedule; maybe we could include under "About the role" or a separate "Travel" but not allowed headings. Could fold into Qualifications? Probably better to include a short paragraph under About the role or Qualifications about travel requirement. Physical demands etc: could be omitted? It's substantive but not in allowed headings. Could we create a section "Working Conditions"? Not in list but maybe allowed as e.g., not limited. The instruction says e.g., not exhaustive. So we could add a section "Working Conditions". But they said prefer a few substantive sections over many thin ones. Might combine physical demands into Qualifications? Not ideal. Better to follow the instruction: Use headings from the list where appropriate. For physical demands, maybe we can omit because not in list? But we must preserve ALL substantive information. So we need to include it somewhere. Could add a section "Working Conditions" as a heading (though not in the example list). The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. But they also say prefer a few substantive sections over many thin ones. So we could combine physical demands and travel into a "Working Conditions" section. Thus sections: - About the role (job summary) - Responsibilities - Qualifications (education, experience, licenses/certs, maybe also skills? but skills separate) - Skills - Working Conditions (physical demands, travel requirement) - Pay (pay range) We must not include Benefits if not stated. There's no benefits mentioned. So omit. Now we need to extract content. Job Summary: "Company enGen Job Description JOB SUMMARY CANDIDATE MUST BE US Citizen (due to contractual/access requirements)*** This job takes a lead role, within area of responsibility, and (application, solution, information, technology, business) designs, develops, implements, supports, and optimizes more complex architecture strategy to meet business capabilities and needs. Takes a lead role to ensure completeness of more complex architecture by adequately addressing all the pertinent concerns of its stakeholders. Ensures integrity of more complex architecture by connecting various views of stakeholders, reconciling conflicting concerns, and showing the trade-offs made in so doing. Considers practicality and fitness for purpose in determining architecture to develop. Leverages business and technology knowledge to enable and/or alter business processes, practices, organizations and systems. Maintains knowledge of emerging technologies and best in class industry business trends and practices. May take on role of Project Lead for special assignments. May mentor less experienced team members." We need to preserve all substantive info. Remove boilerplate like "Company enGen Job Description". Keep the summary. We'll output
About the role
...
Responsibilities: The long list starting with "ESSENTIAL RESPONSIBILITIES". We need to break into bullet points. The text is a run-on sentences separated by periods. We can split each sentence into a bullet. Must preserve all info. We'll create- each sentence. We need to be careful not to lose any content. Let's copy the responsibilities text exactly as given (excluding the heading). It starts after "ESSENTIAL RESPONSIBILITIES". The text: "Take a lead role to provide strategic consultation to business customers in defining or designing more complex business processes, functions and organizational structures, as well as in researching, identifying and internally marketing enabling technologies based on customer capability requirements. Facilitate development of more complex enterprise business solutions that combine knowledge of particular business processes and issues, general technological options, and process facilitation techniques. Participate in more complex enterprise strategy development, including environmental analysis, opportunity identification, value cases and business innovation portfolio development.Take a lead role to specify and design large or more complex systems, solutions, networks, infrastructure elements, or processes. Select appropriate design standards, methods and tools and ensure that they are applied effectively. Review others’ system design to ensure selection of appropriate technology, efficient use of resources and integration of multiple systems and technology. Establish policy for selection of more complex architecture components. Evaluate and undertake impact analysis on more complex major design options. Ensure that the system architecture balances functional, service quality and systems management requirements.Use appropriate tools, including models of components and interfaces, to contribute to the development of more complex architectures. Take a lead role to produce detailed component requirements, specifications and translates these into detailed solutions/designs for implementation using selected products. Provide advice on technical aspects of system development, integration (including requests for changes, deviations from specifications, etc.) and processes. Ensure that relevant technical and business strategies, policies, standards and practices are applied correctly.Select and use more complex tools and methods to establish, clarify, and communicate the functional and non-functional requirements of system users, their characteristics, and tasks. Take a lead role to identify the technical, organizational, and physical environment in which more complex products or systems will operate. Identify, propose, initiate, and lead significant improvement programs, taking responsibility for the quality and appropriateness of the work performed and the realization of measurable business benefits. Modify existing process improvement approaches and/or develop new approaches to achieve improvement.Take a lead role to ensure the resolution of a variety of more complex architecture and business problems and serve as a technical or business lead for highly complex project initiatives.Communicate effectively will all levels of organization.Manage expectations of customers, partners and management.Participate in customer walkthroughs and plans; design and technical walkthroughs; and problem resolution and decision making.Interact with departments across the organization as necessary, including the development and interpretation of highly complex requirements for peers and other staff.Maintain an in-depth knowledge of specific technical aspects in area of expertise and provides expert advice regarding their application. The area of specific expertise may be any aspect of information or communication technology, technique, method, process, product, or application area of a more complex nature.Take a lead role in providing leadership and mentoring in the areas of expertise and architecture to their peers, developers, management and business users including technical expertise, coaching, and ad-hoc training by preparing presentations on more complex issues on the area of expertise and presenting to their peers to ensure consistency to the Organization's strategic direction.Other duties as assigned or requested." We need to split into sentences. Note some sentences lack spaces after periods (e.g., "development.Take"). We'll handle by splitting at periods followed by space or capital letter? For simplicity, we can manually split where we see a period and then a capital letter or start of new sentence. We'll produce bullet points accordingly. Let's list them: 1. Take a lead role to provide strategic consultation to business customers in defining or designing more complex business processes, functions and organizational structures, as well as in researching, identifying and internally marketing enabling technologies based on customer capability requirements. 2. Facilitate development of more complex enterprise business solutions that combine knowledge of particular business processes and issues, general technological options, and process facilitation techniques. 3. Participate in more complex enterprise strategy development, including environmental analysis, opportunity identification, value cases and business innovation portfolio development. 4. Take a lead role to specify and design large or more complex systems, solutions, networks, infrastructure elements, or processes. 5. Select appropriate design standards, methods and tools and ensure that they are applied effectively. 6. Review others’ system design to ensure selection of appropriate technology, efficient use of resources and integration of multiple systems and technology. 7. Establish policy for selection of more complex architecture components. 8. Evaluate and undertake impact analysis on more complex major design options. 9. Ensure that the system architecture balances functional, service quality and systems management requirements. 10. Use appropriate tools, including models of components and interfaces, to contribute to the development of more complex architectures. 11. Take a lead role to produce detailed component requirements, specifications and translates these into detailed solutions/designs for implementation using selected products. 12. Provide advice on technical aspects of system development, integration (including requests for changes, deviations from specifications, etc.) and processes. 13. Ensure that relevant technical and business strategies, policies, standards and practices are applied correctly. 14. Select and use more complex tools and methods to establish, clarify, and communicate the functional and non-functional requirements of system users, their characteristics, and tasks. 15. Take a lead