Senior Finance Analyst

We need to output HTML fragment with sections: About the role? Actually we have Division Overview and Job Overview. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. 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. 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. We need to decide which sections to include. The posting includes: - Division Overview (company description) - Job Overview (summary) - Responsibilities (list) - Qualifications - Skills & Requirements (list) - Education & Experience (list) - Benefits (list of benefits) - Compensation (Pay) (Min/Max) - Physical Requirements (list) - Additional Physical Requirements (list) - Blood/Fluid Exposure Risk Category (list) - Technical Skills repeated (duplicate) - Communication repeated (duplicate) - Responsibilities repeated (duplicate) - etc. We need to remove duplicates and boilerplate. We need to decide sections: maybe "About the Company" (Division Overview) could be under "About the role"? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can also include other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use those headings as appropriate. Probably we should map content to those headings. We have: - About the role: could combine Division Overview and Job Overview? Or maybe "About the role" is job overview. Division Overview could be considered "About the company". Not listed but maybe we can include as a paragraph under About the role? The instruction says 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. It doesn't forbid other headings besides those examples. But they say "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for sections. So we should produce sections with those headings only if we have content. Thus we need to map: - About the role: Job Overview (summary) maybe plus Division Overview? Could be combined. - Responsibilities: list of responsibilities. - Requirements: maybe Education & Experience? Or Qualifications? The instruction includes both Requirements and Qualifications as separate headings. We need to decide what goes where. Typically Requirements could be education/experience, Qualifications could be skills. But they also have Skills heading. So we have three: Requirements, Qualifications, Skills. Might be overlapping. We need to avoid thin sections. Perhaps we can combine into Qualifications (skills) and Requirements (education/experience). Skills heading maybe not needed if we put skills under Qualifications. But we have a separate Skills heading in examples; we could use it for technical skills. Let's think: The posting has: - Technical Skills; Advanced Microsoft Excel skills (vlookups, index-match, complex modeling); familiarity with BI tools (Power BI, Tableau) and ERP systems (SAP, Oracle). - Communication: Exceptional verbal and written communication skills with a proven ability to present financial data to non-financial stakeholders. - Education & Experience: Bachelor’s degree ... Experience: 2-3 years ... Operational and conceptual understanding of Gross-to-Net (GTN) mechanics... etc. Thus we could map: - Skills: Technical Skills + Communication (maybe combine) - Qualifications: Education & Experience (maybe also includes GTN understanding) - Requirements: maybe nothing else? Could be left out. But we need to avoid empty headings. So we should only include headings where we have substantive content. We also have Benefits section: list of benefits. Pay: Compensation Min/Max. Schedule: Not mentioned; we should not create Schedule section. Thus sections: About the role, Responsibilities, Skills, Qualifications, Benefits, Pay. We might also include "Requirements" if we have something like "Operational and conceptual understanding of Gross-to-Net (GTN) mechanics." That could be a requirement. But we already have education/experience under Qualifications. Could move that to Requirements. Better: Use Requirements for education/experience and maybe GTN understanding. Use Qualifications for skills? But the examples list Qualifications separate from Skills. Usually Qualifications includes education/experience, Skills includes technical abilities. Let's follow that: - Qualifications: Education & Experience (Bachelor’s degree, 2-3 years relevant pharma experience, understanding of GTN mechanics, ability to model net revenue impacts, etc.) - Skills: Technical Skills (Excel, BI tools, ERP) + Communication (verbal/written) - Responsibilities: list. - Benefits: list. - Pay: Min/Max. - About the role: Division Overview + Job Overview. We must not repeat duplicated lines. Ensure we preserve all substantive info. Let's extract content. Division Overview text: "Division Overview Aurobindo Pharma USA, Inc. is a generic pharmaceutical manufacturer and distributor and is a wholly owned subsidiary of Aurobindo Pharma Limited, a leading generic pharmaceutical company based in India. Headquartered in HITEC City, Hyderabad, India, founded in 1986 and becoming a public company in India in 1992. Aurobindo Pharma USA, Inc. is committed to delivering a broad portfolio of quality, affordable generic pharmaceuticals to pharmacists and patients. Aurobindo Pharma USA, Inc. adds value through superior customer service in the distribution of a broad line of generic pharmaceuticals, leveraging vertical integration and efficient controlled processes. Aurobindo has business operations in more than 125 countries around the world. Aurobindo is a global pharmaceutical company with a broad portfolio of generic drugs that includes more than 180 product families and 450 individual product packages. Aurobindo markets over 80% of the top 100 most prescribed products in the world. In past years, Aurobindo has received more ANDA approvals than any of our competitors. Aurobindo is now ranked 2nd among pharmaceutical companies based on Total Prescriptions Dispensed. (We are#27 in 2010)" Job Overview: "Job Overview The Senior Financial Analyst supports commercial reporting and performance insights for the sales and marketing teams. You translate complex financial data into clear, actionable stories. You partner with commercial leaders to track key performance indicators (KPIs) and manage forecasting cycles." Responsibilities list (from first occurrence): "Commercial Reporting: Build and deliver accurate monthly, quarterly, and annual commercial performance reports, tracking revenue, gross margins, and customer profitability. Variance Analysis: Conduct in-depth actual-versus-budget/forecast analyses to explain volume, price, and mix variances. Forecasting & Budgeting: Lead the financial forecasting, annual budgeting, and strategic planning processes for commercial business units. Business Partnering: Work directly with sales and marketing leaders to provide decision support, track pipeline health, and evaluate commercial initiatives. Financial Modeling: Develop dynamic financial models to assess pricing scenarios, customer contract profitability, and go-to-market strategies. Process Improvement: Automate and streamline reporting workflows using modern business intelligence and ERP tools to improve data accuracy and turnaround time." Qualifications - Skills & Requirements (first occurrence): "Technical Skills; Advanced Microsoft Excel skills (vlookups, index-match, complex modeling); familiarity with BI tools (Power BI, Tableau) and ERP systems (SAP, Oracle). Communication: Exceptional verbal and written communication skills with a proven ability to present financial data to non-financial stakeholders. Education & Experience Education:Bachelor’s degree in accounting, Finance, Business, Supply Chain, Data/Analytics, or related field. Experience:2-3 years of relevant pharma experience, with a focus on commercial, sales, or FP&A reporting. Operational and conceptual understanding of Gross-to-Net (GTN) mechanics. The ability to model and assess net revenue impacts in the generic pharmaceutical market including an understanding of discounts, rebates, chargebacks, fees, and pricing programs and be able to predict the financial impact of those changes." Then benefits list: "Annual Bonus Long-term Incentive Plan Medical and Rx Benefits choice of four medical plans through Horizon. Rx automatically provided with medical benefits Dental Benefits with three dental plan options through CIGNA Vision Plan with two plan options through VSP Life Insurance, Basic Life and AD&D and Supplemental Life Insurance Disability Insurance, Voluntary Short-Term Disability and State Disability Long-Term Disability (LTD), State (short term) disability – where applicable FSA (Flexible Spending Accounts) – Both Health Care & Dependent Care Available HSA (Health Savings Account) 401(k) Plan - Through Fidelity / Employer Match / fully vested after 3 years Employee Assistance Program (EAP) - 100% Confidential and 100% company paid Critical Illness and Accidental Insurance Legal and Identity Theft Insurance Paid Time Off - Paid vacation, PTO, Holiday" Compensation: "Compensation Min USD $80,000.00/Yr. Max USD $95,000.00/Yr." Physical Requirements list (first occurrence): "Physical Requirements OFFICE POSITION - While performing the duties of this job the employee is required to: Stand, sit; talk, hear, and use hands and fingers to operate a computer and telephone keyboard reach, stoop kneel to install computer equipment Specific vision abilities required by this job include close vision requirements due to computer work Light to moderate lifting is required Moderate noise (i.e. business office with computers, phone, and printers, light traffic). Ability to sit at a computer terminal for an extended period of time Sedentary work Exerting up to 10 pounds of force occasionally and/or negligible amount of force frequently or constantly to lift, carry, push, pull or otherwise move objects, including the human body. Sedentary work involves sitting most of the time. Jobs are sedentary if walking and standing are required only occasionally and all other sedentary criteria are met." Additional Physical Requirements: "Additional Physical Requirements No Additional Requirements Blood/Fluid Exposure Risk Category III: Tasks involve no exposure to blood, body fluids or tissues. Category I tasks are not a condition of employment." We should include Physical Requirements? The instruction didn't list Physical Requirements as an example heading, but we could include it if we have content. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They didn't forbid other headings, but they said "Prefer a few substantive sections over many thin ones." Physical Requirements could be a section but maybe it's thin? It's fairly detailed. Could be included as a section "Physical Requirements". But not in examples. However we could incorporate into "Requirements" maybe? But Requirements likely refers to job requirements (education/experience). Physical requirements are separate. Might be better to include as its own section,