Sr. Oracle Fusion Financial Analyst
AV · San Diego, CA · 1 mo ago
On-siteSales$180k–$200k/yrFull-time
We need to output HTML fragment with sections: About the role (maybe from "Position Responsibilities"? Actually "Position Responsibilities" is a heading. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We have:
- Position Responsibilities: a list of bullet-like sentences (actually each line starts with a verb). We'll put under
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We have:
- Position Responsibilities: a list of bullet-like sentences (actually each line starts with a verb). We'll put under Responsibilities
with - each.
- Basic Qualifications (Required Skills & Experience): This is qualifications. Use
Qualifications
(or Requirements?). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications. Likely Requirements = basic qualifications? Qualifications = other qualifications & desired competencies? We'll split: Basic Qualifications -> Requirements (or Qualifications?). The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections. We'll put Basic Qualifications under Requirements. And Other Qualifications & Desired Competencies under Qualifications.
- Key Competencies: maybe Skills? We'll put under Skills.
- Physical Demands: maybe not a standard heading; we could fold into About the role? But we have About the role maybe from "Who We Are"? Actually there is "About AV:" and "Who We Are" and "What We Do". That's company description; we could put under About the role? The instruction: About the role section heading. Could include description of role and company? Probably we can put a brief About the role summarizing the position purpose. But we must not invent. We have "Position Responsibilities" already; we could treat that as Responsibilities. About the role could be a short paragraph from the job description overview: maybe the first lines: "Worker Type Regular Job Description Position Responsibilities Lead and support..." Not great. There's no explicit "About the role" paragraph. Could omit About the role if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have a clear About the role paragraph, we should not include it. We have "Position Responsibilities" which we will map to Responsibilities. We have "Basic Qualifications (Required Skills & Experience)" -> Requirements. We have "Other Qualifications & Desired Competencies" -> Qualifications. We have "Key Competencies" -> Skills. We have Benefits: there is a Benefits paragraph later: "Benefits: AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." Also repeated later. So we will include Benefits section with that content.
Pay: The posting includes "The Salary Range For This Role Is: $180,000 - $200,000". So we include Pay section with that.
Schedule: There's mention of "Hybrid work requirement: Onsite in AV locations, 1–2 days per week." and also "9/80 work schedule" in benefits. Schedule could be hybrid work requirement. We'll include Schedule section with that.
We must remove boilerplate: EEO, legal, application instructions, duplicated lines, etc.
We need to preserve all substantive information. So we need to include all responsibilities bullets, qualifications bullets, key competencies bullets, benefits, pay, schedule, maybe also note about ITAR requirement? That's a special requirement: "U.S. Citizen, U.S. Permanent Resident (Green Card holder) or asylee/refugee status as defined by 8 U.S.C. 1324b(a)(3) required." Also ITAR requirement. This is substantive; we should include maybe under Requirements or a separate section? There's no heading for that; we could fold into Requirements as a bullet. But we must not invent headings. We could add a bullet under Requirements: "U.S. Citizen, U.S. Permanent Resident (Green Card holder) or asylee/refugee status required (ITAR/EAR compliance)". That preserves info.
Also "Occasionally may be required to travel within the Continental U.S." Could be under Responsibilities or Schedule? Probably under Responsibilities as a bullet.
We need to avoid duplication: there are repeated Benefits and ITAR sections later; we will include only once.
Now construct HTML.
We'll have:
Responsibilities
- Lead and support Oracle Fusion Finance and Oracle EPM implementations, rollouts, enhancements, and production-support activities.
- Partner with Finance, Accounting, FP&A, Contracts, and IT stakeholders to translate business requirements into scalable ERP and EPM solutions.
- Provide functional expertise in Oracle Fusion Financials, including General Ledger, Accounts Payable, Accounts Receivable, Cash Management, Fixed Assets, Tax, Costing, and financial reporting.
- Support Oracle EPM capabilities, including planning, budgeting, forecasting, financial reporting, Smart View, data integration, management reporting, and variance analysis.
- Support integrated Finance and planning processes, including annual budgets, rolling forecasts, month-end close, financial consolidations, management reporting, and audit support.
- Collaborate with technical teams and implementation partners on integrations, data conversion, reporting, security, workflow, and testing.
- Apply GovCon knowledge to support compliant financial processes, indirect-rate planning, cost accounting, labor forecasting, contract reporting, and audit readiness.
- Support PPM-related Finance processes as needed, including project costing, project financial reporting, billing, revenue recognition, and interfaces with Finance.
- Drive process standardization, identify improvement opportunities, manage enhancements, and provide post-go-live support.
- Occasionally may be required to travel within the Continental U.S.
Requirements
- Bachelor’s degree in computer science, Finance, Information Systems, or a related field, or an equivalent combination of education and experience.
- 8–10+ years of experience in Finance systems, ERP implementations, business analysis, or enterprise applications.
- Strong hands-on experience with Oracle Fusion Financials, particularly General Ledger, Accounts Payable, Accounts Receivable, Cash Management, Fixed Assets, Tax, Costing, and financial reporting.
- Experience with Oracle EPM Cloud, including Planning, Budgeting, Forecasting, Financial Reporting, Smart View, data management, or ERP/EPM integrations.
- Strong Finance and Accounting knowledge, including financial close, budgeting, forecasting, cost accounting, internal controls, and management reporting.
- Government Contracting (GovCon) experience is required, including familiarity with government accounting, indirect rates, labor charging, cost structures, contract accounting, and audit/compliance requirements.
- Knowledge of FAR/DCAA compliance and controls in a GovCon environment.
- Experience with requirements gathering, functional design, testing, data conversion, integrations, reporting, and end-user support.
- Strong analytical, communication, stakeholder-management, and problem-solving skills.
- U.S. Citizen, U.S. Permanent Resident (Green Card holder) or asylee/refugee status as defined by 8 U.S.C. 1324b(a)(3) required (ITAR/EAR compliance).
Qualifications
- Advanced degree (MS, MBA, CPA).
- Experience with Oracle Fusion Projects (PPM), including project costing, billing, revenue recognition, or project financial reporting.
- Experience with Oracle EPM Planning, Financial Consolidation and Close (FCCS), Account Reconciliation, Enterprise Data Management, or Narrative Reporting.
- Experience with Oracle Integration Cloud, BI Publisher, OTBI, FBDI, REST/SOAP APIs, and Smart View.
- Experience with multi-entity, multi-ledger, global, or regulated business environments.
- Oracle Fusion Financials or Oracle EPM Cloud certifications.
- Skilled in problem-solving and influencing cross-functional teams.
- Excellent written and verbal communication skills, including presenting to leadership and collaborating across teams.
- Thrives in a fast-paced, deadline-driven environment with strong organizational skills.
- Demonstrates initiative, ownership, and accountability for results, driving continuous improvement.
- Team-oriented, focused on collaboration and putting team success above individual interests.
Skills
- Strong solutioning and implementation mindset
- Ability to drive end-to-end delivery and adoption
- Deep understanding of Finance and Project Accounting operations
- Strong communication skills across technical and business audiences
- Ability to balance speed, quality, and compliance during rollouts
Benefits
- Medical, dental, vision
- 401K with company matching
- 9/80 work schedule
- Paid holiday shutdown
Pay
The Salary Range For This Role Is: $180,000 - $200,000
Schedule
Hybrid work requirement: Onsite in AV locations, 1–2 days per week.
We need to ensure we didn't include any boilerplate like EEO, legal, etc. Also we removed duplicated benefits lines.
Check that we preserved all substantive info: Responsibilities all bullets captured. Requirements includes all basic qualifications plus US person requirement. Qualifications includes other qualifications & desired competencies. Skills includes key competencies. Benefits includes medical, dental vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown. Pay includes salary range. Schedule includes hybrid work requirement.
We also included travel bullet under Responsibilities.
We didn't include "Physical Demands" (sit/stand long periods, talk, hear, use hands). That's substantive; we missed it. Should we include? It's under Physical Demands heading in original. Could be placed under Schedule or maybe a separate section? There's no standard heading for Physical Demands; we could add a bullet under Schedule or maybe under Responsibilities? But it's not a responsibility. Could add a bullet under Schedule? Might be okay to add a bullet under Schedule: "Required to sit and stand for long periods; talk, hear, and use hands and fingers to operate a computer and telephone keyboard (Frequent)". That preserves info.
We should add that to Schedule section as another sentence.
Thus Schedule section could be:
Schedule
Hybrid work requirement: Onsite in AV locations, 1–2 days per week. Required to sit and stand for long periods; talk, hear, and use hands and fingers to operate a computer and telephone keyboard (Frequent).
Now check if any other substantive info missed: "Principals only need apply. NO agencies please." That's application instruction, remove. "Please understand that any job offer that requires approval of an export license will be conditional..." That's legal/boilerplate, remove. Also repeated ITAR sections removed.
"About AV:" and "Who We Are" and "What We Do" are company description; could be considered About the role? But we decided not to include About the role if no specific content. However we could include a short About the role paragraph from that description? It's more about company than role. The instruction says About the role section heading; we could put company description there but it's not about the role. Safer to omit About the role
Qualifications
(or Requirements?). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications. Likely Requirements = basic qualifications? Qualifications = other qualifications & desired competencies? We'll split: Basic Qualifications -> Requirements (or Qualifications?). The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections. We'll put Basic Qualifications under Requirements. And Other Qualifications & Desired Competencies under Qualifications.
- Key Competencies: maybe Skills? We'll put under Skills.
- Physical Demands: maybe not a standard heading; we could fold into About the role? But we have About the role maybe from "Who We Are"? Actually there is "About AV:" and "Who We Are" and "What We Do". That's company description; we could put under About the role? The instruction: About the role section heading. Could include description of role and company? Probably we can put a brief About the role summarizing the position purpose. But we must not invent. We have "Position Responsibilities" already; we could treat that as Responsibilities. About the role could be a short paragraph from the job description overview: maybe the first lines: "Worker Type Regular Job Description Position Responsibilities Lead and support..." Not great. There's no explicit "About the role" paragraph. Could omit About the role if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have a clear About the role paragraph, we should not include it. We have "Position Responsibilities" which we will map to Responsibilities. We have "Basic Qualifications (Required Skills & Experience)" -> Requirements. We have "Other Qualifications & Desired Competencies" -> Qualifications. We have "Key Competencies" -> Skills. We have Benefits: there is a Benefits paragraph later: "Benefits: AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." Also repeated later. So we will include Benefits section with that content.
Pay: The posting includes "The Salary Range For This Role Is: $180,000 - $200,000". So we include Pay section with that.
Schedule: There's mention of "Hybrid work requirement: Onsite in AV locations, 1–2 days per week." and also "9/80 work schedule" in benefits. Schedule could be hybrid work requirement. We'll include Schedule section with that.
We must remove boilerplate: EEO, legal, application instructions, duplicated lines, etc.
We need to preserve all substantive information. So we need to include all responsibilities bullets, qualifications bullets, key competencies bullets, benefits, pay, schedule, maybe also note about ITAR requirement? That's a special requirement: "U.S. Citizen, U.S. Permanent Resident (Green Card holder) or asylee/refugee status as defined by 8 U.S.C. 1324b(a)(3) required." Also ITAR requirement. This is substantive; we should include maybe under Requirements or a separate section? There's no heading for that; we could fold into Requirements as a bullet. But we must not invent headings. We could add a bullet under Requirements: "U.S. Citizen, U.S. Permanent Resident (Green Card holder) or asylee/refugee status required (ITAR/EAR compliance)". That preserves info.
Also "Occasionally may be required to travel within the Continental U.S." Could be under Responsibilities or Schedule? Probably under Responsibilities as a bullet.
We need to avoid duplication: there are repeated Benefits and ITAR sections later; we will include only once.
Now construct HTML.
We'll have:
Responsibilities
- Lead and support Oracle Fusion Finance and Oracle EPM implementations, rollouts, enhancements, and production-support activities.
- Partner with Finance, Accounting, FP&A, Contracts, and IT stakeholders to translate business requirements into scalable ERP and EPM solutions.
- Provide functional expertise in Oracle Fusion Financials, including General Ledger, Accounts Payable, Accounts Receivable, Cash Management, Fixed Assets, Tax, Costing, and financial reporting.
- Support Oracle EPM capabilities, including planning, budgeting, forecasting, financial reporting, Smart View, data integration, management reporting, and variance analysis.
- Support integrated Finance and planning processes, including annual budgets, rolling forecasts, month-end close, financial consolidations, management reporting, and audit support.
- Collaborate with technical teams and implementation partners on integrations, data conversion, reporting, security, workflow, and testing.
- Apply GovCon knowledge to support compliant financial processes, indirect-rate planning, cost accounting, labor forecasting, contract reporting, and audit readiness.
- Support PPM-related Finance processes as needed, including project costing, project financial reporting, billing, revenue recognition, and interfaces with Finance.
- Drive process standardization, identify improvement opportunities, manage enhancements, and provide post-go-live support.
- Occasionally may be required to travel within the Continental U.S.
Requirements
- Bachelor’s degree in computer science, Finance, Information Systems, or a related field, or an equivalent combination of education and experience.
- 8–10+ years of experience in Finance systems, ERP implementations, business analysis, or enterprise applications.
- Strong hands-on experience with Oracle Fusion Financials, particularly General Ledger, Accounts Payable, Accounts Receivable, Cash Management, Fixed Assets, Tax, Costing, and financial reporting.
- Experience with Oracle EPM Cloud, including Planning, Budgeting, Forecasting, Financial Reporting, Smart View, data management, or ERP/EPM integrations.
- Strong Finance and Accounting knowledge, including financial close, budgeting, forecasting, cost accounting, internal controls, and management reporting.
- Government Contracting (GovCon) experience is required, including familiarity with government accounting, indirect rates, labor charging, cost structures, contract accounting, and audit/compliance requirements.
- Knowledge of FAR/DCAA compliance and controls in a GovCon environment.
- Experience with requirements gathering, functional design, testing, data conversion, integrations, reporting, and end-user support.
- Strong analytical, communication, stakeholder-management, and problem-solving skills.
- U.S. Citizen, U.S. Permanent Resident (Green Card holder) or asylee/refugee status as defined by 8 U.S.C. 1324b(a)(3) required (ITAR/EAR compliance).
Qualifications
- Advanced degree (MS, MBA, CPA).
- Experience with Oracle Fusion Projects (PPM), including project costing, billing, revenue recognition, or project financial reporting.
- Experience with Oracle EPM Planning, Financial Consolidation and Close (FCCS), Account Reconciliation, Enterprise Data Management, or Narrative Reporting.
- Experience with Oracle Integration Cloud, BI Publisher, OTBI, FBDI, REST/SOAP APIs, and Smart View.
- Experience with multi-entity, multi-ledger, global, or regulated business environments.
- Oracle Fusion Financials or Oracle EPM Cloud certifications.
- Skilled in problem-solving and influencing cross-functional teams.
- Excellent written and verbal communication skills, including presenting to leadership and collaborating across teams.
- Thrives in a fast-paced, deadline-driven environment with strong organizational skills.
- Demonstrates initiative, ownership, and accountability for results, driving continuous improvement.
- Team-oriented, focused on collaboration and putting team success above individual interests.
Skills
- Strong solutioning and implementation mindset
- Ability to drive end-to-end delivery and adoption
- Deep understanding of Finance and Project Accounting operations
- Strong communication skills across technical and business audiences
- Ability to balance speed, quality, and compliance during rollouts
Benefits
- Medical, dental, vision
- 401K with company matching
- 9/80 work schedule
- Paid holiday shutdown
Pay
The Salary Range For This Role Is: $180,000 - $200,000
Schedule
Hybrid work requirement: Onsite in AV locations, 1–2 days per week.
We need to ensure we didn't include any boilerplate like EEO, legal, etc. Also we removed duplicated benefits lines. Check that we preserved all substantive info: Responsibilities all bullets captured. Requirements includes all basic qualifications plus US person requirement. Qualifications includes other qualifications & desired competencies. Skills includes key competencies. Benefits includes medical, dental vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown. Pay includes salary range. Schedule includes hybrid work requirement. We also included travel bullet under Responsibilities. We didn't include "Physical Demands" (sit/stand long periods, talk, hear, use hands). That's substantive; we missed it. Should we include? It's under Physical Demands heading in original. Could be placed under Schedule or maybe a separate section? There's no standard heading for Physical Demands; we could add a bullet under Schedule or maybe under Responsibilities? But it's not a responsibility. Could add a bullet under Schedule? Might be okay to add a bullet under Schedule: "Required to sit and stand for long periods; talk, hear, and use hands and fingers to operate a computer and telephone keyboard (Frequent)". That preserves info. We should add that to Schedule section as another sentence. Thus Schedule section could be:Schedule
Hybrid work requirement: Onsite in AV locations, 1–2 days per week. Required to sit and stand for long periods; talk, hear, and use hands and fingers to operate a computer and telephone keyboard (Frequent).
Now check if any other substantive info missed: "Principals only need apply. NO agencies please." That's application instruction, remove. "Please understand that any job offer that requires approval of an export license will be conditional..." That's legal/boilerplate, remove. Also repeated ITAR sections removed. "About AV:" and "Who We Are" and "What We Do" are company description; could be considered About the role? But we decided not to include About the role if no specific content. However we could include a short About the role paragraph from that description? It's more about company than role. The instruction says About the role section heading; we could put company description there but it's not about the role. Safer to omit About the role