Analyst Financial Planning and Analysis

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Essential Responsibilities, Minimum Experience And Qualifications, Preferred Experience And Qualifications, Crewmember Expectations, Equipment, Work Environment, Physical Effort, Compensation. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can map content to these headings. We need to decide which sections to include. We have Position Summary -> could be "About the role". Essential Responsibilities -> "Responsibilities". Minimum Experience And Qualifications -> could be "Requirements" or "Qualifications". Preferred Experience And Qualifications -> maybe "Skills" or additional qualifications. Crewmember Expectations maybe not needed? It's about safety etc. Could be omitted if not matching headings. Equipment, Work Environment, Physical Effort maybe not needed. Compensation -> "Pay". Benefits maybe not explicitly listed but compensation mentions benefits; we could include Benefits section if there is content about benefits. The posting mentions base pay range and mentions total compensation package includes healthcare, 401(k), etc. That's benefits info. So we can include Benefits. Schedule: not mentioned. So we should not include Schedule heading. We must not repeat job title as heading. Do not put Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting within appropriate sections. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  Position Summary ...

  Responsibilities

  • ... each responsibility as list item
  We need to split the Essential Responsibilities paragraph into list items. The paragraph is long with many responsibilities separated by commas and semicolons. We'll break into logical items. Similarly for Minimum Experience And Qualifications -> maybe

  Requirements

  with list. Preferred Experience And Qualifications -> maybe

  Preferred Qualifications

  but heading must be from list: Qualifications, Skills. Could use

  Qualifications

  for minimum and

  Skills

  for preferred? But we already used Qualifications maybe for minimum. Let's think: The instruction says use those headings as examples, not strict. We can use any of those headings. We'll include: - About the role (position summary) - Responsibilities - Requirements (minimum qualifications) - Preferred Qualifications (maybe as Skills) - Benefits - Pay We need to ensure we don't create empty sections. Now extract details. Position Summary paragraph: "The Analyst, Financial Planning & Analysis – Loyalty & Revenue supports JetBlue’s Loyalty and Revenue Management teams through financial planning, reporting, data analysis, and recurring FP&A processes. This role helps connect commercial performance, customer behavior, loyalty activity, and revenue trends to financial outcomes by preparing forecasts, variance analysis, dashboards, and business insights. The Analyst will partner closely with Commercial FP&A leadership, Loyalty, Revenue Management, Revenue Analytics, Revenue Management Data Science, Accounting, IT, and other Finance teams. The ideal candidate has a strong business foundation, analytical curiosity, and experience using SQL or similar tools to extract, validate, and analyze data. This role is well suited for someone who can work with large datasets, understand business drivers, support recurring forecast processes, and clearly communicate insights to finance and commercial stakeholders." We'll put that in

  . Responsibilities list: Let's parse the sentence: "Support recurring FP&A processes for Loyalty, including monthly close support, variance analysis, forecast updates, budget planning, OpEx tracking, CapEx tracking, and performance reporting Prepare monthly and quarterly reporting packages that explain financial performance, key business drivers, risks, opportunities, and variances to forecast, budget, and prior year Use Excel, Tableau, SQL, and other analytical tools to extract, validate, summarize, and analyze financial, commercial, loyalty, customer, and revenue data Analyze drivers of Loyalty and Revenue Management performance, including revenue trends, redemption activity, customer behavior, partner performance, forecast assumptions, investment activity, and cost trends Partner with Revenue Analytics, Revenue Management Data Science, Loyalty, and other Finance teams to understand analytical outputs and translate findings into financial implications, forecast updates, and business narratives Maintain, update, and improve recurring financial models, reporting templates, dashboards, and process documentation Support the development of financial forecasts, annual budgets, long-range plans, and business cases for Loyalty, Revenue Management, Paisly, and other Commercial initiatives Assist with ad hoc analysis requested by Commercial FP&A leadership and business partners, including opportunity sizing, sensitivity analysis, trend analysis, and scenario modeling Identify data quality issues, process gaps, and reporting inefficiencies; recommend improvements to increase accuracy, consistency, and automation. Prepare materials for leadership discussions, including charts, exhibits, variance explanations, and concise written commentary. Build strong working relationships across Commercial, Finance, Accounting, IT, Revenue Analytics, and Revenue Management Data Science teams. Other duties as assigned." We'll make each line a

• . Now Minimum Experience And Qualifications: "Bachelor’s degree in Finance, Economics, Business, Accounting, Mathematics, Statistics, Analytics, Engineering, or another related field; OR demonstrated capability to perform job responsibilities with a combination of a High School Diploma/GED and previous relevant work experience. Two (2) years of experience in Finance, Commercial, Revenue Management, Loyalty, Analytics, Consulting, Accounting, or another business-oriented analytical role. Experience performing financial analysis, variance analysis, forecasting, budgeting, reporting, business-case support, or performance analysis. Experience writing SQL queries or using SQL-based tools to extract, join, validate, and analyze data. Strong Excel and PowerPoint skills, including ability to organize data, build analysis, summarize findings, and prepare clear presentation materials. Strong analytical skills, including ability to evaluate datasets, identify trends, connect analysis to business drivers, and communicate implications clearly. Ability to work with analysis produced by other teams, understand core assumptions, identify key takeaways, and translate findings into financial impact. Strong attention to detail and ability to maintain recurring processes with accuracy, consistency, and timeliness. Ability to manage multiple priorities, recurring deadlines, and ad hoc requests in a fast-paced environment. Ability to interact with stakeholders at different levels of the organization and build effective cross-functional relationships. Proficient with the Microsoft Office suite. Available for occasional overnight travel (10%) Must pass a pre-employment drug test. Must be legally eligible to work in the country in which the position is located. Authorization to work in the United States is required; this position is not eligible for visa sponsorship." We'll list each as
• . Preferred Experience And Qualifications: "Experience supporting Commercial, Loyalty, Revenue Management, airline, travel, subscription, marketplace, customer economics, or revenue-focused business functions. Experience using Snowflake, Tableau, Python, Alteryx, Power BI, or similar analytical and visualization tools. Experience building or maintaining dashboards, recurring reports, forecast templates, or automated data processes. Familiarity with airline commercial metrics, loyalty economics, revenue forecasting, redemption behavior, customer profitability, or partner economics. Experience translating complex analysis into concise business commentary, executive materials, or forecast recommendations. Demonstrated curiosity about business performance, customer behavior, revenue drivers, and financial outcomes." We'll list as
• under maybe

  Skills

  or

  Preferred Qualifications

  . Since we have Qualifications already used for minimum, we can use Skills for preferred. Crewmember Expectations etc: Not needed for headings; we could omit as not matching headings. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". We could still include them as

  without heading? But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We'll omit Crewmember Expectations, Equipment, Work Environment, Physical Effort as they don't map to those headings and could be considered filler? But they contain substantive info. However we could incorporate them into a general

  under maybe "About the role" or separate sections not using those headings? The instruction says use those headings for section headings; doesn't forbid other headings but suggests using them. Safer to include only those headings and put other info maybe as

  under appropriate sections? But we must preserve ALL substantive information. If we drop Crewmember Expectations etc, we lose info. So we need to include them somewhere. Could we put them under a generic

  About the role? Already used for position summary. Could add another

  like "Additional Information" but not in list. Might be okay but instruction says use those headings for section headings (e.g...). It doesn't say you cannot use other headings, but "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections. It doesn't forbid other headings but suggests using those. To be safe, we could incorporate Crewmember Expectations etc into a

  under "About the role" or maybe under a new heading like "Additional Details" but that deviates. Perhaps we can treat them as part of "Requirements" or "Skills"? Not really. Better to create sections for each of those using appropriate headings from list if they map: Equipment maybe not; Work Environment maybe not; Physical Effort maybe not; Crewmember Expectations maybe could be under "Requirements"? Not exactly. Given the instruction to preserve ALL substantive information, we need to include them. We could add a

  section like "Additional Information" but that is not from the list. Might be considered violating the rule to use those headings for section headings. However the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, just that you should use h3 for headings, and gives examples. So using other headings is okay as long as they are h3. But they also say "Prefer a few substantive sections over many thin ones." So we could combine some. We could create a section "Additional Information" with h3 and include Crewmember Expectations, Equipment, Work Environment, Physical Effort as list items. That would preserve info. But maybe better to incorporate them under "About the role" as extra paragraphs. That would keep few sections. Let's do: After position summary paragraph, add another paragraph covering Crewmember Expectations, Equipment, Work Environment, Physical Effort. That preserves info without extra heading. Thus sections: About the role (includes position summary + additional info), Responsibilities, Requirements (minimum qualifications), Skills (preferred qualifications), Benefits, Pay. Now Benefits: we need to extract from Compensation paragraph: "Base pay is one component of JetBlue’s total compensation package, which may also include access to healthcare benefits, a 401(k) plan and company match, crewmember stock purchase plan, short-term and long-term disability coverage, basic life insurance, free space available travel on JetBlue, and more." We'll make a Benefits section with list items. Pay: base pay range $67,000 to $101,000 per year. Now ensure we don't include filler like "commensurate with experience" etc