FINANCIAL ANALYST III
City of Houston · Houston, TX · 3 wk ago
Finance$108/hrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Position Overview" and "Description Of Duties/Essential Functions". Also "WORKING CONDITIONS", "Minimum Requirements", "PREFERENCES", "GENERAL INFORMATION", "SALARY INFORMATION". We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We must not include filler like "commensurate with experience". We need to preserve all substantive info.
We need to map content to appropriate headings.
- About the role: could be "Position Overview" and maybe "Description Of Duties/Essential Functions". Could combine into About the role? Actually "About the role" is generic; we can put overview there. Then "Responsibilities" for duties list.
- Requirements: Minimum Requirements (education, experience, license). Also maybe "Qualifications" for preferences? But we can treat "Requirements" as mandatory qualifications, and "Preferences" as "Skills" or "Qualifications". The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content.
We have:
- Position Overview: location, division, workdays/hours. That's about the role.
- Description Of Duties/Essential Functions: list of duties (many bullet-like sentences). That's responsibilities.
- Minimum Requirements: education, experience, license. That's Requirements.
- PREFERENCES: list of preferred experience/skills. That could be Qualifications or Skills. Since we have both Qualifications and Skills headings, we could put preferences under Qualifications (preferred qualifications) and maybe Skills for specific skills like Advanced Microsoft Excel skills, etc. But we can also combine.
- WORKING CONDITIONS: not in headings list; we could maybe omit or put under About the role? But instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The headings list is suggested but not mandatory? It says "use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We must not include filler like "commensurate with experience". We need to preserve all substantive info.
We need to map content to appropriate headings.
- About the role: could be "Position Overview" and maybe "Description Of Duties/Essential Functions". Could combine into About the role? Actually "About the role" is generic; we can put overview there. Then "Responsibilities" for duties list.
- Requirements: Minimum Requirements (education, experience, license). Also maybe "Qualifications" for preferences? But we can treat "Requirements" as mandatory qualifications, and "Preferences" as "Skills" or "Qualifications". The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content.
We have:
- Position Overview: location, division, workdays/hours. That's about the role.
- Description Of Duties/Essential Functions: list of duties (many bullet-like sentences). That's responsibilities.
- Minimum Requirements: education, experience, license. That's Requirements.
- PREFERENCES: list of preferred experience/skills. That could be Qualifications or Skills. Since we have both Qualifications and Skills headings, we could put preferences under Qualifications (preferred qualifications) and maybe Skills for specific skills like Advanced Microsoft Excel skills, etc. But we can also combine.
- WORKING CONDITIONS: not in headings list; we could maybe omit or put under About the role? But instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The headings list is suggested but not mandatory? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings where applicable. If we have content that doesn't fit those, we could still create a heading but maybe not from list? The instruction says use those for section headings (e.g.) meaning those are examples; we can use other headings if needed? Safer to stick to those. Working conditions could be placed under About the role or maybe omitted? But we must preserve ALL substantive information. So we need to include working conditions somewhere. Could add a section "Working Conditions" as even though not in examples; but instruction says use for section headings (e.g. About the role, ...). It doesn't forbid other headings. So we can add a Working Conditions
.
- GENERAL INFORMATION: includes selection process, safety impact, etc. Could be placed under About the role or maybe a separate section "General Information". We'll add.
- SALARY INFORMATION: Pay Grade 21. That's Pay section.
- Benefits: not mentioned. So we should not create Benefits section.
- Schedule: workdays & hours given: Monday-Friday 8 am to 5 pm. That's schedule. So we can include Schedule section.
Thus sections: About the role (position overview + location + division + workdays/hours? Actually schedule separate). We'll put location, division, workdays/hours in About the role? But schedule separate. Let's put location, division, workdays/hours in About the role. Then schedule separate.
Responsibilities: list of duties.
Requirements: education, experience, license.
Qualifications: preferred qualifications list.
Skills: maybe specific skills like Advanced Microsoft Excel skills, experience with SAP, etc. But preferences list includes many skill-like items. Could split: Qualifications for preferred experience, Skills for specific technical skills. But we can also just put all preferences under Qualifications and omit Skills. However we need to preserve all info; we can put them under Qualifications as a list. That's fine.
Pay: Pay Grade 21.
Schedule: Monday-Friday 8 am to 5 pm.
Working Conditions: description.
General Information: selection process, safety impact, application procedures? Actually application procedures are separate but we must remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to remove application procedures lines. So we should not include application procedures. Also remove EEO etc. So we keep only substantive info: selection process will involve application review and/or interview; safety impact position yes (random drug testing); maybe also mention that selection process will involve application review and/or interview. Also maybe "GENERAL INFORMATION" includes selection/skills tests required, safety impact position. We'll keep those.
We must not include application procedures, EEO, etc.
Thus final HTML:
About the role
even though not in examples; but instruction says use for section headings (e.g. About the role, ...). It doesn't forbid other headings. So we can add a Working Conditions
.
- GENERAL INFORMATION: includes selection process, safety impact, etc. Could be placed under About the role or maybe a separate section "General Information". We'll add.
- SALARY INFORMATION: Pay Grade 21. That's Pay section.
- Benefits: not mentioned. So we should not create Benefits section.
- Schedule: workdays & hours given: Monday-Friday 8 am to 5 pm. That's schedule. So we can include Schedule section.
Thus sections: About the role (position overview + location + division + workdays/hours? Actually schedule separate). We'll put location, division, workdays/hours in About the role? But schedule separate. Let's put location, division, workdays/hours in About the role. Then schedule separate.
Responsibilities: list of duties.
Requirements: education, experience, license.
Qualifications: preferred qualifications list.
Skills: maybe specific skills like Advanced Microsoft Excel skills, experience with SAP, etc. But preferences list includes many skill-like items. Could split: Qualifications for preferred experience, Skills for specific technical skills. But we can also just put all preferences under Qualifications and omit Skills. However we need to preserve all info; we can put them under Qualifications as a list. That's fine.
Pay: Pay Grade 21.
Schedule: Monday-Friday 8 am to 5 pm.
Working Conditions: description.
General Information: selection process, safety impact, application procedures? Actually application procedures are separate but we must remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to remove application procedures lines. So we should not include application procedures. Also remove EEO etc. So we keep only substantive info: selection process will involve application review and/or interview; safety impact position yes (random drug testing); maybe also mention that selection process will involve application review and/or interview. Also maybe "GENERAL INFORMATION" includes selection/skills tests required, safety impact position. We'll keep those.
We must not include application procedures, EEO, etc.
Thus final HTML:
About the role
Working Conditions
. - GENERAL INFORMATION: includes selection process, safety impact, etc. Could be placed under About the role or maybe a separate section "General Information". We'll add. - SALARY INFORMATION: Pay Grade 21. That's Pay section. - Benefits: not mentioned. So we should not create Benefits section. - Schedule: workdays & hours given: Monday-Friday 8 am to 5 pm. That's schedule. So we can include Schedule section. Thus sections: About the role (position overview + location + division + workdays/hours? Actually schedule separate). We'll put location, division, workdays/hours in About the role? But schedule separate. Let's put location, division, workdays/hours in About the role. Then schedule separate. Responsibilities: list of duties. Requirements: education, experience, license. Qualifications: preferred qualifications list. Skills: maybe specific skills like Advanced Microsoft Excel skills, experience with SAP, etc. But preferences list includes many skill-like items. Could split: Qualifications for preferred experience, Skills for specific technical skills. But we can also just put all preferences under Qualifications and omit Skills. However we need to preserve all info; we can put them under Qualifications as a list. That's fine. Pay: Pay Grade 21. Schedule: Monday-Friday 8 am to 5 pm. Working Conditions: description. General Information: selection process, safety impact, application procedures? Actually application procedures are separate but we must remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to remove application procedures lines. So we should not include application procedures. Also remove EEO etc. So we keep only substantive info: selection process will involve application review and/or interview; safety impact position yes (random drug testing); maybe also mention that selection process will involve application review and/or interview. Also maybe "GENERAL INFORMATION" includes selection/skills tests required, safety impact position. We'll keep those. We must not include application procedures, EEO, etc. Thus final HTML:About the role
Location: 2999 S. Wayside Dr. Division: Management & Finance. Workdays & Hours: Monday-Friday 8 am to 5 pm (subject to change).
Responsibilities
- Analyze financial information, monitor budgets and expenditures, identify trends and variances, prepare financial projections and reports, and provide recommendations to support sound financial and operational decision-making.
- Serve as team lead in preparing the department's annual governmental funds budget, coordinating data collection and ensuring accuracy throughout the budget development process.
- Compile and analyze various financial reports and budget forecasts, presenting key findings to leadership for annual budget discussions.
- Prepare Monthly Financial Operating Reports (MFOR) for five funds using MFORPrep software and identify discrepancies by reconciling results against the Finance Department's straight-line projections.
- Prepare monthly Full-Time Equivalency (FTE) report that analyzes annual staffing metrics against planned projections, detailing variances in staffing levels and percentages.
- Develop quarterly financial projections for payroll and operating expenses, analyzing data for 5 funds totaling over $108 million.
- Monitor daily financial transactions in SAP, research discrepancies, and prepare journal entries to correct posting errors.
- Analyze utility data (electric, water/sewer, and natural gas) and prepare ad hoc financial reports and spreadsheets for end-users to support management decision-making.
- Serve as the backup Purchasing Card (P-Card) Coordinator by managing cardholder statements, updating transactions in JPMorgan PaymentNet based on submitted documentation, coordinating with the Strategic Procurement Division to resolve account coding, grant fund, and internal order discrepancies, and preparing year-end purchasing card accruals for processing.
- Serve as back-up Cost Center Approver ensuring expenditures comply with budgetary and financial policies. Prepare budget transfers, posting journal entries, and quarterly OBB performance submissions to the Financial Planning & Analysis Division.
- Collaborate with multiple departments to collect, analyze, and report financial data for capital and operating expenditures, including TPL survey reporting.
- Apply advanced analytical and problem-solving skills to resolve complex financial issues while maintaining compliance with governmental accounting standards.
- Communicate financial information clearly through written reports, presentations, and collaboration with divisions.
Requirements
- Bachelor's degree in Finance, Accounting, Business Administration or a closely related field.
- Three years of professional experience in finance, economics, budget analysis or a closely related area.
- Experience cannot be substituted for the Bachelor’s degree requirement.
- A Master's degree in Finance, Accounting, Business Administration or a closely related field may be substituted for two years of the above experience requirement.
- No license requirements.
Qualifications
- Eligible veteran applicants provided such persons possess the qualifications necessary for competent discharge of the duties involved in the position applied for, such persons are among the most qualified candidates for the position, and all other factors in accordance with Executive Order 1-6.
- Experience preparing financial forecasts and projections.
- Experience performing budget-to-actual and variance analysis.
- Experience using SAP or a comparable enterprise financial management system.
- Experience preparing monthly, quarterly, and annual financial reports.
- Experience with personnel expenditure and FTE analysis.
- Experience with purchasing, procurement, or Purchasing Card administration.
- Advanced Microsoft Excel skills.
- Experience presenting financial information and recommendations to management.
- Experience working with multiple divisions, departments, or stakeholders.
- Experience leading financial projects or process-improvement initiatives.
Pay
Pay Grade 21.
Schedule
Monday-Friday 8 am to 5 pm (subject to change).
Working Conditions
The position is physically comfortable; the individual has discretion about walking and standing. There are occasional minor discomforts from exposure to less-than-optimal temperature and air conditions. The position may involve dealing with modestly unpleasant situations, such as occasional exposure to office chemicals and/or extensive use of a video display terminal.
General Information
- Selection process will involve application review and/or interview.
- Safety Impact Position: YES – subject to random drug testing; if promotional, candidate must pass an assignment drug test.