Senior Budget Analyst

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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like background check, status of posted positions, contact email? Actually contact email maybe part of Agency Contact Name and Information - could be considered contact info but not required sections. The instructions: 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 (the page already shows it) and 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 extract sections: - About the role: The first paragraph: "In this role, you’ll support the financial backbone of DCY by planning, implementing, and monitoring a wide range of budgets and cost allocation activities. You’ll work with capital and operating budgets, operating budgets, division or program level budgets, federal and state funding streams, and cost pools that support DCY’s mission. Your work directly impacts how resources are distributed across the agency." - Responsibilities: The "What You’ll Do" bullet list: Budget Planning & Monitoring, Cost Accounting & Allocation, Data Analysis & Reporting, Tools & Technology, Collaboration & Continuous Improvement. Each with sub-bullets. We need to format as

  • for any list of duties/requirements/benefits. So we can have nested lists? Probably just top-level li with sub-bullets as separate li? Could embed
    inside
    • . Acceptable. - Requirements: The qualifications/experience: "4 yrs. experience in budgeting that included fiscal management & control involving use of quantitative/statistical analysis (e.g., probability statistics, linear regression, multiple variable regression, computer assisted regression analysis models, trend analysis, forecasting cost benefit analysis). Or completion of undergraduate core program in accounting, public finance, public administration or business administration; 24 mos. exp. in fiscal management & control involving use of quantitative/statistical analysis (e.g., probability statistics, linear regression, multiple variable regression, computer assisted regression analysis models, trend analysis, forecasting cost benefit analysis).Or completion of graduate core program in accounting, public finance, public administration or business administration; 12 mos. exp. in fiscal management & control involving use of quantitative/statistical analysis (e.g., probability statistics, linear regression, multiple variable regression, computer regression analysis models, trend analysis, forecasting cost benefit analysis).Or 12 mos. exp. as Budget Analyst, 63261.Or equivalent of Minimum Class Qualifications for Employment noted above." We can format as a list of options. - Qualifications: Might be same as Requirements? The posting also lists "Job Skills: Accounting and Finance". Could be Skills section. Also "Professional Skills Attention to Detail". Could be Skills. - Benefits: Not explicitly listed besides "generous benefit options" in Agency Overview. That's vague. Not specific. So we should not create Benefits section unless specific content. The posting mentions "generous benefit options and a flexible work life balance". That's somewhat specific but not detailed. Might be considered filler? The instruction: never create Benefits sections unless posting actually states them. It does state "generous benefit options". That's a statement but not detailed. Might be considered substantive? It's vague but still a statement. However they said prefer few substantive sections over many thin ones. Could include Benefits with that statement. But we need to decide. - Pay: The posting includes detailed Pay Information with table of hourly and annual wages across steps. That's specific. So we must include Pay section. - Schedule: The posting includes "Schedule Full-time Work Hours 8:00 AM - 5:00 PM" and also location requirements about core hours. So we have schedule specifics. So include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe Skills), Pay, Schedule. Possibly also Skills. Let's extract Skills: "Job Skills: Accounting and Finance" and "Professional Skills Attention to Detail". Also "Agency Overview About us ..." includes mission statement but that's not skills. Could include Skills section with those items. Qualifications: Might be separate from Requirements? The posting includes "4 yrs. experience..." etc. That's qualifications. Also "Job Skills: Accounting and Finance" could be skills. We'll treat Requirements as experience/education, Qualifications as skills? But the instruction list includes both Requirements and Qualifications as possible headings. We'll allocate: - Requirements: Experience/Education (the long or statements) - Qualifications: Skills (Accounting and Finance, Attention to Detail) - Skills maybe redundant. Could combine. Better: Use Requirements for experience/education, Qualifications for skills, and maybe not separate Skills. But we also have "Professional Skills Attention to Detail". That's a skill. Thus:

      About the role

      ...

      Responsibilities

      • Budget Planning & Monitoring
        ...
      ... etc. We need to preserve all substantive info. Let's extract each bullet. From text: Budget Planning & Monitoring - Assist in developing and implementing agency budgets, including biennium budget preparation. - Project, adjust, and monitor allocations for subdivisions, grants, and specific financial programs. - Track spending patterns to prevent deficits and propose corrective actions when risks arise. - Prepare periodic financial reports for senior management. Cost Accounting & Allocation - Calculate depreciation for DCY equipment and incorporate these values into financial analyses. - Apply cost distribution data to determine cost pool funding and ensure proper allocation across state and federal programs. - Participate in agency teams responsible for applying cost allocation methodologies. - Review, edit, and help maintain the Agency’s Cost Allocation Plan (CAP). - Analyze existing cost pool methodologies and develop new approaches when needed. Data Analysis & Reporting - Research, evaluate, and interpret financial and operational data using statistical and quantitative methods. - Develop forecast and projection models for programs with multiple funding sources. - Prepare specialized reports such as cost allocation summaries or funding split analyses. - Complete federal expenditure reports and analyze proposed legislation or policy changes for financial impact. Tools & Technology - You’ll frequently use spreadsheets, databases, and other software tools to: - Perform financial modeling and projections. - Generate reports and update critical financial data. - Support automation and technical improvements within budget operations. Collaboration & Continuous Improvement - Work directly with senior program and support staff to identify needed changes in cost allocation processes. - Participate as a team member or leader on projects involving data research, financial modeling, or operational reviews. - Develop procedures and guidelines to ensure compliance with state and federal regulations. We need to keep the "You’ll frequently use spreadsheets..." as a li maybe with sublist. Now Requirements: The long paragraph with options. We'll break into list items each option. Option 1: 4 yrs. experience in budgeting that included fiscal management & control involving use of quantitative/statistical analysis (e.g., probability statistics, linear regression, multiple variable regression, computer assisted regression analysis models, trend analysis, forecasting cost benefit analysis). Option 2: completion of undergraduate core program in accounting, public finance, public administration or business administration; 24 mos. exp. in fiscal management & control involving use of quantitative/statistical analysis (e.g., probability statistics, linear regression, multiple variable regression, computer assisted regression analysis models, trend analysis, forecasting cost benefit analysis). Option 3: completion of graduate core program in accounting, public finance, public administration or business administration; 12 mos. exp. in fiscal management & control involving use of quantitative/statistical analysis (e.g., probability statistics, linear regression, multiple variable regression, computer regression analysis models, trend analysis, forecasting cost benefit analysis). Option 4: 12 mos. exp. as Budget Analyst, 63261. Option 5: equivalent of Minimum Class Qualifications for Employment noted above. We'll list each as
      • . Qualifications/Skills: "Job Skills: Accounting and Finance" and "Professional Skills Attention to Detail". Also maybe "Agency Overview About us..." but that's not skill. We'll put Skills section with those two items. Pay: We need to include the table. Could represent as
        • ... but better as a table? The instruction says use
          • for any list of duties/requirements/benefits, and

            for prose. For pay table, it's not a list but could be presented as a

            with each step as li. Or we could keep as a

            with the table content. Probably better to use

            • for each step. We'll list each step with hourly and annual. Steps: Step 1: Hourly $34.53, Annual $71,822; Step 2: $36.20 / $75,296; Step 3: $38.01 / $79,061; Step 4: $39.86 / $82,909; Step 5: $41.81 / $86,965; Step 6: $43.90 / $91,312; Step 7: $46.00 / $95,680; Step 8: $48.28 / $100,422; Step 9: $50.66 / $105,373. Also note progression after 6 months etc. Could include that prose. Schedule: "Schedule Full-time Work Hours 8:00 AM - 5:00 PM". Also location requirements: core hours Mon-Fri 8:00am to 5:00pm, daily start/end may vary 7:00am-9:00am, on-site daily. We'll include that. Now we must not include boilerplate like background check, status of posted positions, contact email, unposting date, agency overview mission statement? The agency overview includes mission statement but that's not required sections; we could drop as it's not specific to role? It's generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The agency overview is not boilerplate but maybe considered generic. However it's substantive about agency mission. Could be considered part of About the role? Already we have About the role paragraph. The agency overview is separate; we could drop it as not directly about the role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The agency overview is substantive about the agency, but not about the role. Might be considered not required. However they said "Prefer a few substantive sections over many thin ones." Including agency overview would be extra section not in list of allowed headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not add extra headings. So we drop agency overview. Also drop "Location Requirements" maybe could be part of Schedule? It's about work location and hours. Could incorporate into Schedule section. Now we