SOLUTIONS ARCHITECT IV
Banda Group International, LLC · Albuquerque, NM · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like EEO, application instructions, etc. Also remove duplicated lines. Must not include sections with placeholder like "commensurate with experience". Pay section: we have "Pay depending on experience" which is vague; but we have also "competitive salary". The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention Pay depending on experience (not a specific number) and also mentions benefits details. It also mentions schedule? No schedule info. So we can include Benefits section (since they list many benefits). Pay section: they say "Pay depending on experience" which is vague but still a statement about pay. However the instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Pay depending on experience" is similar to "commensurate with experience" which is considered filler. So we should not create a Pay section. Benefits we have specific details: ESOP, dental, vision, life, STD/LTD, medical coverage, HSA, accident insurance, PTO, 11 paid holidays, 401(k) match, personal development reimbursement, corporate gym membership, veteran support, etc. Those are specific. So include Benefits.
Schedule: no info, so omit.
Skills: we could extract from Required Qualifications and Preferred Qualifications: expert knowledge, strong knowledge, etc. Could create Skills section summarizing those. But we must not invent or summarize away detail; we can list them as bullet points. That's okay.
Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine into Qualifications section with subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put Required Qualifications under Qualifications, and maybe Preferred Qualifications also under Qualifications or Skills? The instruction: Use headings for those categories. We'll put Required Qualifications under Qualifications, Preferred Qualifications maybe under Skills or also Qualifications? Better to put Preferred Qualifications under Skills? But they are qualifications not skills. However we can include both under Qualifications, separating required vs preferred via paragraphs or lists. That's fine.
About the role: we have Position Summary paragraph. So About the role section.
Responsibilities: Essential Duties and Responsibilities.
Requirements: maybe we could separate "Required Qualifications" as Requirements? But we already have Qualifications heading. The list includes Requirements as a possible heading. We could put Required Qualifications under Requirements, and Preferred under Qualifications? But we need to decide. The instruction: Use headings for those categories. It doesn't forbid using both Requirements and Qualifications. We'll include both if content exists. Let's map:
- About the role: Position Summary.
- Responsibilities: Essential Duties and Responsibilities.
- Requirements: Required Qualifications (maybe also include Physical Requirements? Those are more like abilities; could be under Requirements as well).
- Qualifications: Preferred Qualifications.
- Skills: maybe extract specific technical skills from Required/Preferred (expert knowledge of enterprise architecture, SQL Server, Oracle RDBMS, Oracle PIF, Oracle WebLogic, Oracle Primavera, etc.) Could be under Skills.
- Benefits: as described.
- Pay: omit.
- Schedule: omit.
We must not repeat job title as heading. Good.
We must not include boilerplate like EEO, application instructions, veteran support? Veteran support is part of benefits? It's under What We Offer: "Veteran Support -- Military Leave Program". That's a benefit, include.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content.
About the role (Position Summary):
"The Solutions Architect 4 serves as a principal architect for large, complex enterprise technology solutions supporting Laboratory-wide business and technical requirements. This senior-level role designs and integrates solutions spanning hardware, software, databases, networking, telecommunications, security, and enterprise web applications. Solutions may include commercial-off-the-shelf platforms such as Oracle Primavera P6, Oracle Project Integration Framework (PIF), and Oracle WebLogic, as well as internally developed systems. The position provides expert technical leadership and architectural direction for unusually significant and complex initiatives. The selected individual will work with a high degree of independence, apply strategic and creative problem-solving, and ensure that proposed architectures support both immediate requirements and long-term business objectives."
Responsibilities (Essential Duties and Responsibilities):
List each bullet:
- Lead the architecture and delivery of complex, cross-disciplinary enterprise technology solutions
- Gather, analyze, and translate customer and Laboratory-wide requirements into scalable technical architectures.
- Research and evaluate industry practices, emerging technologies, and regulatory changes affecting data management, security, networking, hardware, software development, systems programming, and telecommunications.
- Provide technical leadership and architectural direction across hardware, software, database, networking, security, and enterprise application environments.
- Develop solutions to complex technical problems that span multiple disciplines and require evaluation of competing requirements and long-term impacts.
- Integrate strategic business objectives into solution design to support sustainability, interoperability, scalability, and future capabilities.
- Manage complex projects from inception through implementation, including planning, schedules, budgets, resource utilization, documentation, training, and benefits realization, as assigned.
- Support the implementation, administration, maintenance, integration, and end-user use of enterprise platforms and applications.
- Lead and collaborate with technical teams, customers, stakeholders, system administrators, and other cross-functional partners.
- Maintain compliance with Laboratory safety, security, policies, procedures, and required training.
Requirements (Required Qualifications + Physical Requirements?):
Required Qualifications:
- Bachelor's degree in a relevant field and at least 12 years of related experience, or an equivalent combination of education and directly related experience.
- Expert knowledge of enterprise architecture across network, data management, security, hardware, software development, systems programming, and enterprise web application technologies.
- Expert-level experience with SQL Server and Oracle RDBMS implementation, administration, maintenance, and end-user support.
- Expert-level knowledge of Oracle Project Integration Framework (PIF).
- Strong knowledge of Oracle WebLogic and enterprise web application delivery.
- Strong knowledge of Oracle Primavera Portfolio Management and/or Primavera P6 environments.
- Experience maintaining environments that integrate project controls functions, including estimating, scheduling, and cost management.
- Demonstrated ability to architect complex solutions and understand how enterprise technologies interoperate.
- Excellent written and verbal communication, organizational, and project management skills.
- Demonstrated experience building and leading teams of technologists.
- Ability to work independently, exercise sound judgment, and provide solutions to complex, high-impact technical issues.
Physical Requirements:
- Ability to visually inspect and interpret data or details
- Ability to communicate effectively in both verbal and written formats
- Ability to remain in a stationary position (e.g., sitting or standing) for extended periods of time
- Ability to move throughout the work environment, including bending, reaching, walking, and climbing stairs
- Frequent use of hands to operate computer systems, tools, or equipment.
We could include Physical Requirements under Requirements as well.
Qualifications (Preferred Qualifications):
- Post-graduate coursework in a relevant technical or business discipline.
- Relevant professional certifications in enterprise architecture, Oracle technologies, project management, cybersecurity, cloud, or related areas.
- Experience supporting large-scale, highly regulated, government, DOE/NNSA, or national laboratory environments.
- Experience formally managing complex technology implementations, including documentation, training, schedules, budgets, and resource planning.
Skills: maybe we can list specific technical skills extracted: Expert knowledge of enterprise architecture across network, data management, security, hardware, software development, systems programming, enterprise web application technologies; Expert-level experience with SQL Server and Oracle RDBMS; Expert-level knowledge of Oracle PIF; Strong knowledge of Oracle WebLogic; Strong knowledge of Oracle Primavera Portfolio Management and/or Primavera P6; Experience maintaining environments that integrate project controls functions (estimating, scheduling, cost management); Ability to architect complex solutions and understand interoperability; Excellent written/verbal communication, organizational, project management skills; Experience building/leading teams; Ability to work independently, exercise sound judgment; etc. But many overlap with qualifications. To avoid duplication, we could keep Skills as a concise list of technical competencies: enterprise architecture, SQL Server, Oracle RDBMS, Oracle PIF, Oracle WebLogic, Oracle Primavera P6/Portfolio Management, project controls integration, etc. However we risk duplicating content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create Skills section, we must not omit any substantive info that belongs elsewhere. But we can still include the info in Skills as well as elsewhere? That would be duplication, which we should avoid. Better to not create Skills if it would duplicate. However the instruction allows us to create Skills section if we have specific content not covered elsewhere. But we already have Required Qualifications covering expertise. Could we treat Required Qualifications as Requirements and Preferred as Qualifications, and not have Skills? That seems acceptable. The instruction says we can use those headings; we don't have to use all. So we can omit Skills if no distinct content. Let's check: Are there any skills not captured in qualifications? The responsibilities also include skills like leadership, collaboration, etc. But those are covered. So we can skip Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Check Benefits section content: from "What We Offer" paragraph.
Extract:
- BGI offers a competitive salary and a comprehensive benefits package for eligible full-time employees, in accordance with plan documents, including:
- Pay depending on experience (we might omit as filler)
- Employee Stock Ownership Plan (ESOP) -- giving employees a direct stake in the company's long-term success
- 100% employer-paid Dental, Vision, Life, STD/LTD for all full-time employees; dependents can be added with payroll contributions
- Medical coverage -- PPO or HDHP plan options; dependents can be added with payroll contributions
- Abundant employer contribution for HSA enrollees
- Accident, Critical Illness, and Voluntary Life Insurance
- Robust PTO plan and 11 paid holidays per year
- Generous 401(k) with safe harbor program and up to 4% dollar-for-dollar match
- $1,500 yearly personal development reimbursement for all levels of employees
- Corporate gym membership rates at Orangetheory Fitness
- Veteran Support -- Military Leave Program
- Excellent working environment with team building and bonding events
We should exclude "Pay depending on experience" as filler. Also "competitive salary" is vague; but it's part of benefits intro. Could keep as part of benefits description: "BGI offers a competitive salary and a comprehensive benefits package..." That's okay.
We must not include boilerplate like EEO, application instructions, etc. Already removed.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Requirements
then two- or we can keep one list with all items. That's fine.
- ... ...
- ... ...