Program Finance Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to include sections only when posting has real specific content. The posting includes: - About Integer Technologies (company description). Not a required heading but could be included as maybe "About the company"? Not in list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could include "About the role" (they have a section "About the role"). Also "What you'll do" corresponds to Responsibilities. "Required Qualifications" corresponds to Requirements. "Desired Qualifications" corresponds to Qualifications (or maybe Skills). Benefits section present. Pay: they mention "Base salaries which exceed local & national industry averages." and "Year-end performance-based bonuses." Also "401(k) with company matching that vest immediately". That's compensation/benefits. Pay section could include base salary info and bonuses. Schedule: not mentioned. So we should not include Schedule. We also have "Company Perks" which could be part of Benefits or maybe separate but not required heading. We'll include Benefits section covering medical, dental, vision, relocation assistance, base salaries, bonuses, 401k, paid vacation, sick leave, holidays. Also maybe include "Company Perks" as part of Benefits or separate? Since we only have Benefits heading allowed, we can include perks inside Benefits as list items. We need to avoid filler like "commensurate with experience". Not present. We must output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
... text from About the role section (the paragraph before "What you'll do") maybe combine. Then
Responsibilities
- ... list items from "What you'll do" sections (Program Finance & Execution, Mission Solutions Portfolio Finance, Process & Functional Development). We need to preserve all substantive info; we can break into list items for each bullet.
Then
Requirements
- ... from Required Qualifications.
Then
Qualifications
- ... from Desired Qualifications.
Then
Benefits
- ... list benefits: medical, prescription, vision, dental insurance fully covered; relocation assistance; base salaries exceeding local & national industry averages; year-end performance-based bonuses; 401(k) with company matching that vest immediately; paid vacation; paid sick leave; paid holidays; plus perks: startup culture with stability, direct access to leadership, prioritization of people over process, stellar team, friendly atmosphere.
We could also include "Company Perks" as list items.
Pay: we already included base salaries and bonuses in Benefits. Could also create a Pay section but we already covered. The instruction: only create Pay/Schedule/Benefits sections if posting actually states them. Benefits is stated. Pay is also stated (base salaries, bonuses). Should we create a separate Pay section? The list includes Pay as possible heading. We have salary info; we could create a Pay section with those details. But we also have benefits like insurance etc. Might be better to split: Benefits for insurance, relocation, PTO, etc. Pay for salary and bonuses and 401k. However 401k is a benefit but could be under Pay or Benefits. The instruction: prefer a few substantive sections over many thin ones. So maybe combine compensation and benefits into one Benefits section. That's fine.
We must not include Schedule.
Now we need to extract the exact text.
Let's copy relevant sections.
About Integer Technologies: we may not need to include as heading; but we could include as a short paragraph before About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Should we include the company description? It's substantive. There's no heading for it in the allowed list, but we could just put it as a
before the first heading. That's allowed: we can have prose
elements not under headings. The instruction: 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. So we can have a leading
with company description. Then
About the role
with prose. Then responsibilities as list. Then requirements as list. Then qualifications as list. Then benefits as list. Now let's extract the exact text. About Integer Technologies paragraph: "Integer Technologies is an applied research and product development company founded by scientists and engineers with a passion for protecting freedom with innovation. We perform R&D on next-generation systems and technologies for the Department of War and other U.S. Government agencies. We are hardware and software developers with experience transforming research into fieldable technology. Our core portfolio of research includes projects in power & energy systems, unmanned systems (with an emphasis on maritime systems), digital engineering, and cyber security. Our mission is to create a safer world by translating scientific discoveries into reliable products that address urgent national security needs… at the speed of relevance. Locations: Baton Rouge, LA (Preferred) | Columbia, SC | Durham, NH | Gulfport, MS" We should keep that as a paragraph. Now About the role section: "About the roleThe Program Finance Lead will serve as the primary financial partner to the Mission Solutions organization, supporting both individual program execution and portfolio-level financial management.This role will partner directly with Program Managers to establish credible program baselines, monitor performance against those baselines, maintain forecasts, identify variances, and provide the financial information necessary for effective program decisions. At the Mission Solutions portfolio level, the Program Finance Lead will consolidate program-level information into accurate revenue, margin, staffing, and financial forecasts for Mission Solutions leadership.This is a hands-on role suited for someone who can operate in the details of individual programs while also developing the processes, reporting, and financial discipline needed to support a rapidly growing business unit.As Mission Solutions grows, this role has the potential to evolve into broader leadership of the program finance function.Integer operates in Unanet, and this role will be expected to use the system extensively for program financial management, reporting, and forecasting. Prior Unanet experience is strongly preferred; however, candidates with substantial experience in comparable project accounting, ERP, or program finance systems will be considered if they demonstrate the ability to quickly develop proficiency in Unanet." We need to keep that as prose under About the role heading. Now Responsibilities: "What you'll do" section includes multiple sub-sections. We need to capture all bullet points. Let's extract: Program Finance & Execution - Serve as the primary finance partner to multiple Mission Solutions Program Managers. - Support establishment of executable program baselines, including: - Work Breakdown Structures (WBS) - Labor and non-labor budgets - Revenue and margin plans - Staffing assumptions - Periods of performance and program schedules - Translate proposal, contract, and capture assumptions into executable program financial plans. - Maintain and analyze program actuals, budgets, forecasts, Estimates to Complete (ETCs), and Estimates at Completion (EACs). - Monitor financial performance against approved program baselines. - Identify material cost, schedule, staffing, revenue, and margin variances and work with Program Managers to understand causes and impacts. - Provide Program Managers with clear, timely information that enables informed execution decisions. - Support program rebaselining and formal change-control activities when program assumptions materially change. - Prepare financial inputs for recurring program reviews and management reviews. - Ensure program financial data is accurate, timely, and appropriately maintained within Unanet. Mission Solutions Portfolio Finance - Consolidate individual program forecasts into the overall Mission Solutions financial outlook. - Maintain portfolio-level forecasts for: - Revenue - Margin - Program costs - Financial risks and opportunities - Provide Mission Solutions leadership with visibility into expected financial performance across awarded programs. - Reconcile program-level execution forecasts with Mission Solutions operating forecasts and annual planning. - Identify portfolio-level financial trends, risks, resource constraints, and forecast changes requiring leadership attention. - Support annual operating planning, quarterly forecasting, and other Mission Solutions financial-planning activities. - Help distinguish changes caused by program execution from changes caused by contract timing, funding, scope, staffing, or other business assumptions. - Develop scalable dashboards, reporting standards, and financial-management rhythms for Mission Solutions. Process & Functional Development - Help establish and mature Mission Solutions program-finance and project-controls processes. - Develop consistent expectations for program baselining, forecasting, variance analysis, and financial reporting. - Improve integration between Program Management, Finance, Accounting, Contracts, Engineering, and Mission Solutions leadership. - Help ensure continuity between proposal assumptions, awarded contracts, program baselines, and ongoing execution. - Identify opportunities to improve how Unanet and related systems are used for program and portfolio management. - As the organization grows, help define the structure, tools, and potentially the future team required to support the Mission Solutions program-finance function. We need to turn each bullet into - . For sub-bullets (like under Support establishment of executable program baselines, including:), we could either flatten them as separate
- items. The instruction: use
- for any list of duties/requirements/benefits. So we can treat each bullet as
- . Sub-bullets can be separate
- as well. Now Required Qualifications: "Required QualificationsU.S Citizenship5+ years of relevant experience in program finance, project controls, financial planning and analysis, or a related discipline supporting complex programs or projects.Bachelor’s degree in Finance, Accounting, Business, Economics, or a related field preferred. Equivalent relevant professional experience will also be considered.Demonstrated experience in program finance, project controls, FP&A, or a closely related discipline supporting complex projects or programs.Strong knowledge of budgeting, forecasting, variance analysis, ETC/EAC development, and financial performance reporting.Experience working directly with Program Managers or other accountable operational leaders.Experience consolidating program-level financial information into business-unit or portfolio-level forecasts.Ability to translate detailed financial information into clear analysis that supports management decisions.Strong analytical skills and attention to detail.Ability to manage financial activities across multiple programs simultaneously.Experience with Unanet, or substantial experience with a comparable project accounting, ERP, or program-finance platform and demonstrated ability to quickly learn Unanet.Advanced Excel and financial modeling skills.Strong communication skills and ability to work across Program Management, Engineering, Contracts, Accounting, Finance, and executive leadership." We need to split into list items. Each sentence separated by period. Let's extract: - U.S. Citizenship - 5+ years of relevant experience in program finance, project controls, financial planning and analysis, or a related discipline supporting complex programs or projects. - Bachelor’s degree in Finance, Accounting, Business, Economics, or a related field preferred. Equivalent relevant professional experience will also be considered. - Demonstrated experience in program finance, project controls, FP&A, or a closely related discipline supporting complex projects or programs. - Strong knowledge of budgeting, forecasting, variance analysis, ETC/EAC development, and financial performance reporting. - Experience working directly with Program Managers or other accountable operational leaders.
- for any list of duties/requirements/benefits, and
- ... list benefits: medical, prescription, vision, dental insurance fully covered; relocation assistance; base salaries exceeding local & national industry averages; year-end performance-based bonuses; 401(k) with company matching that vest immediately; paid vacation; paid sick leave; paid holidays; plus perks: startup culture with stability, direct access to leadership, prioritization of people over process, stellar team, friendly atmosphere.
We could also include "Company Perks" as list items.
Pay: we already included base salaries and bonuses in Benefits. Could also create a Pay section but we already covered. The instruction: only create Pay/Schedule/Benefits sections if posting actually states them. Benefits is stated. Pay is also stated (base salaries, bonuses). Should we create a separate Pay section? The list includes Pay as possible heading. We have salary info; we could create a Pay section with those details. But we also have benefits like insurance etc. Might be better to split: Benefits for insurance, relocation, PTO, etc. Pay for salary and bonuses and 401k. However 401k is a benefit but could be under Pay or Benefits. The instruction: prefer a few substantive sections over many thin ones. So maybe combine compensation and benefits into one Benefits section. That's fine.
We must not include Schedule.
Now we need to extract the exact text.
Let's copy relevant sections.
About Integer Technologies: we may not need to include as heading; but we could include as a short paragraph before About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Should we include the company description? It's substantive. There's no heading for it in the allowed list, but we could just put it as a
- ... from Desired Qualifications.
Then
- ... from Required Qualifications.
Then