Business Analyst.
Bonneville Power Administration · Vancouver, WA · 1 mo ago
AnalystFull-time
We need to output HTML fragment with sections: Duties (maybe heading "Responsibilities"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content accordingly.
The posting includes "Duties" (list of duties). Also "Requirements Conditions of employment" includes conditions of employment (citizenship, e-verify, selective service, etc.) and "Key Requirements". Also "Qualifications" includes specialized experience, time-in-grade, etc. Also "Education" (none). Also "Additional information" includes EEO, reasonable accommodation, veterans, telework, etc. Also benefits mention: "A career with the U.S. government provides employees with a comprehensive benefits package." But no specific benefits details. We should not create Benefits section unless posting actually states them. It mentions benefits package generically but not specifics. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "A career with the U.S. government provides employees with a comprehensive benefits package." That's a statement about benefits but not specific. Might be considered stating benefits exist, but not details. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It might be okay to include a Benefits section with that statement? However they say prefer a few substantive sections over many thin ones. The benefits statement is vague; maybe we can omit Benefits section because no concrete details. Similarly Pay and Schedule not mentioned.
Thus sections: Responsibilities (duties), Requirements (conditions of employment + key requirements?), Qualifications (specialized experience, time-in-grade, etc.), maybe Additional Information (EEO, reasonable accommodation, veterans, telework, etc.) but we need to decide if we need a separate section for that. The instruction: include a section ONLY when the posting has real, specific content for it. The additional info includes EEO policy, reasonable accommodation, veterans, telework, etc. That's specific enough. Could be a section like "Additional Information". But the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Additional Information". However we can still use other headings? The instruction says use
? It's not a requirement but maybe okay. However better to follow instruction: include a section ONLY when posting has real, specific content for it. The allowed headings are examples; we could add a heading like "Additional Information" if we want, but they didn't forbid other headings. They said use with the full sentence(s). Could combine multiple sentences into one .
Requirements:
Conditions of employment:
- In accordance with Executive Order 14170, applicants are encouraged to respond to four short, free-response, essay questions in the questionnaire. Answer to these questions is not scored or rated. Your answers will be reviewed by the hiring manager and agency leadership if you are referred for selection consideration.
- When you apply you will be asked a series of questions to determine your eligibility for employment and your qualification for this position specifically. You must answer all of these questions completely and truthfully.
- Key Requirements:
- You must be a United States Citizen.
- This employer participates in the e-Verify program.
- Males must abide by Selective Service registration requirements.
- You will be required to report in person to the official duty location.
- Conditions of Employment: Selectee will be required to complete the Office of Government Ethics Standard of Confidential Financial Disclosure Report (OFGE450e) within 30 days of employment and annually.
- A preliminary background check must be completed before a new employee can begin work. Current Federal employees or other individuals with an existing completed background investigation may not be required to undergo another background check.
- Hiring incentives may be authorized for a highly qualified candidate based on budget availability and in accordance with federal regulations.
Qualifications:
SPECIALIZED EXPERIENCE REQUIREMENTS: A qualified candidate's online application and resume must demonstrate at least one year of specialized experience equivalent to the next lower grade level [GS-12] in the Federal service. Specialized experience for this position is defined as:
1) Aggregating, analyzing, and interpreting project, operational, and financial data to establish performance metrics, produce executive dashboards and status reports, and deliver data-backed recommendations
2) Leading matrix teams to manage program portfolios by performing risk assessments, financial planning, and operational capability evaluation to determine project initiation, redesign, or termination
3) Evaluating and reengineering business processes, designing future-state operational models, and leveraging conflict resolution techniques to gain leadership approval for organizational changes.
"Experience" refers to paid and unpaid experience. Examples of qualifying unpaid experience may include: volunteer work done through National Service programs (such as Peace Corps and AmeriCorps); as well as work for other community-based philanthropic and social organizations. Volunteer work helps build critical competencies, knowledge, and skills; and can provide valuable training and experience that translates directly to paid employment. You will receive credit for all qualifying experience, including volunteer experience.
Time-in-Grade: Current Federal employees must meet time-in-grade requirements by the closing date of this announcement to receive consideration.
CTAP/ICTAP candidates: To be considered "well qualified" you must meet all of the requirements as described in this section. You must meet all qualifications and eligibility requirements by the closing date of this announcement.
Education: There are no specific education requirements or substitution of education for experience for this position.
We could include Education heading but content says none; we should not create a heading with filler like "not specified". So omit Education.
Additional information: "This job opportunity announcement may be used to fill additional similar vacancies across DOEAdditional positions may be filled from this announcement." That's a note. Could be included under Requirements as a bullet? It's not a requirement but maybe okay. However we could add a section "Additional Information" with that note. Since it's not in the examples but allowed, I'd include it.
But the instruction: "Prefer a few substantive sections over many thin ones." Adding a thin section for just that note might be thin. Could incorporate into Requirements as a bullet: "This announcement may be used to fill additional similar vacancies across DOE."
Thus final HTML:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content accordingly.
The posting includes "Duties" (list of duties). Also "Requirements Conditions of employment" includes conditions of employment (citizenship, e-verify, selective service, etc.) and "Key Requirements". Also "Qualifications" includes specialized experience, time-in-grade, etc. Also "Education" (none). Also "Additional information" includes EEO, reasonable accommodation, veterans, telework, etc. Also benefits mention: "A career with the U.S. government provides employees with a comprehensive benefits package." But no specific benefits details. We should not create Benefits section unless posting actually states them. It mentions benefits package generically but not specifics. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "A career with the U.S. government provides employees with a comprehensive benefits package." That's a statement about benefits but not specific. Might be considered stating benefits exist, but not details. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It might be okay to include a Benefits section with that statement? However they say prefer a few substantive sections over many thin ones. The benefits statement is vague; maybe we can omit Benefits section because no concrete details. Similarly Pay and Schedule not mentioned.
Thus sections: Responsibilities (duties), Requirements (conditions of employment + key requirements?), Qualifications (specialized experience, time-in-grade, etc.), maybe Additional Information (EEO, reasonable accommodation, veterans, telework, etc.) but we need to decide if we need a separate section for that. The instruction: include a section ONLY when the posting has real, specific content for it. The additional info includes EEO policy, reasonable accommodation, veterans, telework, etc. That's specific enough. Could be a section like "Additional Information". But the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Additional Information". However we can still use other headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Probably we should stick to those headings. So we need to map content to those headings.
We have Responsibilities (duties). Requirements (conditions of employment + key requirements). Qualifications (specialized experience, time-in-grade, etc.). Skills? Not explicitly listed. Could we infer skills from duties? But better not to create Skills unless explicit. So we may omit Skills.
Thus output:
Responsibilities
- ... each duty as li
Then Requirements
- ... conditions of employment and key requirements
Then Qualifications
- ... specialized experience, time-in-grade, etc.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, reasonable accommodation, etc? Actually those are part of Additional information; but we are not using Additional information heading. Should we include them under Requirements or Qualifications? They are not requirements or qualifications. They are more like policies. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO policy, reasonable accommodation policy, veterans info, telework, etc. That is considered boilerplate. So we omit those.
Thus we keep only duties, requirements (conditions of employment, key requirements), qualifications (specialized experience, time-in-grade, etc.), education (none, so we omit). Also maybe "Additional information" about filling additional similar vacancies across DOE - that's not boilerplate? It's substantive: "This job opportunity announcement may be used to fill additional similar vacancies across DOE". Could be included under Requirements? Not really. Could be a separate section but not in allowed headings. Perhaps we can include it under Requirements as a note? But it's not a requirement. Might be considered additional info but we could drop as it's not in allowed headings and may be considered boilerplate? It's not boilerplate but it's a note about usage. The instruction: Prefer a few substantive sections over many thin ones. Could we incorporate that note into Requirements as a
Responsibilities
- ... each duty as li
Requirements
- ... conditions of employment and key requirements
Qualifications
- ... specialized experience, time-in-grade, etc.
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 could add a heading like "Additional Information". But to be safe, maybe we stick to the given headings and put that note under Requirements or Qualifications as a bullet. Let's extract details: Duties list: - Lead High-Impact, Cross-Functional Initiatives: Head collaborative teams of multi-disciplinary experts to evaluate, shape, and execute complex business and infrastructure proposals. Serve as driving force behind projects from early-stage concepts to successful, long-term implementation. - Drive Prosci-Aligned Change Management: Design and execute comprehensive organizational change strategies utilizing the industry-standard Prosci methodology. Build and implement tailored plans for training, communication, and coaching to minimize disruption and ensure team buy-in across departmental lines. - Design and Reengineer Business Processes: Serve as trusted advisor in analyzing workflows, identifying operational bottlenecks, and designing modern, technology-enabled processes. Work will directly enhance organizational efficiency, resource utilization, and decision-making capabilities. - Perform Advanced Risk and Financial Analysis: Conduct deep-dive risk assessments and financial evaluations to predict project outcomes, optimize resource allocation, and implement project controls. Provide critical insights to ensure projects are delivered on time, within scope, and on budget. - Direct End-to-End Project and Portfolio Execution: Take ownership of project milestones, schedules, and deliverables. Seamlessly integrate active initiatives into broader organizational portfolio and develop performance metrics to track and evaluate success over time. - Coach and Advise Leadership at All Levels: Provide expert guidance and coaching to managers and senior executives to build strong leadership sponsorship for strategic transitions. Empower leaders to effectively guide their teams through complex organizational shifts. - Integrate Cutting-Edge Technology Solutions: Collaborate with technology teams to identify, adopt, and integrate modern software applications and systems. Ensure digital tools are seamlessly incorporated into daily workflows to support grid operations and physical infrastructure projects. - Champion Stakeholder Engagement and Influence: Build consensus, resolve conflicts, and cultivate collaborative relationships across agency and with external partners. Present compelling, data-driven findings to executives, persuading decision-makers to adopt solutions that align with region's energy strategy. We need to preserve all substantive information; we can break each bullet into
Responsibilities
- Lead collaborative teams of multi-disciplinary experts to evaluate, shape, and execute complex business and infrastructure proposals; serve as the driving force behind projects from early-stage concepts to successful, long-term implementation.
- Design and execute comprehensive organizational change strategies utilizing the industry-standard Prosci methodology; build and implement tailored plans for training, communication, and coaching to minimize disruption and ensure team buy-in across departmental lines.
- Serve as a trusted advisor in analyzing workflows, identifying operational bottlenecks, and designing modern, technology-enabled processes; work will directly enhance organizational efficiency, resource utilization, and decision-making capabilities.
- Conduct deep-dive risk assessments and financial evaluations to predict project outcomes, optimize resource allocation, and implement project controls; provide critical insights to ensure projects are delivered on time, within scope, and on budget.
- Take ownership of project milestones, schedules, and deliverables; seamlessly integrate active initiatives into the broader organizational portfolio and develop performance metrics to track and evaluate success over time.
- Provide expert guidance and coaching to managers and senior executives to build strong leadership sponsorship for strategic