Jobs · Finance · Minnesota

Intern, Financial Planning and Analysis (Summer 2027)

Inspire Medical Systems · Minneapolis, MN · 1 mo ago
On-siteFinance$20–$22/hrVolunteer
We need to output only HTML fragment, no /, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse the posting. We have: - About Inspire Medical Systems (company description). This is not a section heading per list; but we could treat as "About the role"? Actually "About the role" is a heading for role description. The posting includes "Position Summary". That's about the role. So we can have

About the role

with the Position Summary paragraph(s). Also there is "WHY JOIN OUR FAST-GROWING TEAM" which is about benefits/culture; could be part of Benefits or maybe separate but we only have Benefits heading. We'll incorporate that into Benefits section. - Main Duties/Responsibilities: list of duties. We'll put under

Responsibilities

with
  • each duty. - There's also "Quality System Responsibilities" which seems like additional responsibilities; maybe part of Responsibilities as well. We'll include those as additional li items. - Qualifications: includes Educational Requirements, Required Experience, Preferred Experience. We'll put under

    Qualifications

    (or maybe Requirements?). The instruction list includes Requirements and Qualifications separate. We could put educational requirements under Requirements, and experience under Qualifications? But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications. We need to decide what goes where. Typically: Requirements = mandatory qualifications (education, GPA, experience). Qualifications = preferred or additional qualifications. Skills could be separate list of skills (Excel, etc). But we have both required and preferred experience; also skills like Excel, communication, etc. We could put required experience under Requirements, and preferred experience plus skills under Qualifications or Skills. Let's map: - Educational Requirements: Currently enrolled... GPA etc. That's a requirement. - Required Experience: Strong proficiency in Excel, foundational understanding..., analytical skills, ability to organize..., communication skills, comfort working independently. Those are requirements. - Preferred Experience: Prior internship..., strong communication..., comfort collaborative..., familiarity with BI tools..., interest in medical device. Those are preferred qualifications. - Skills: Could be list of skills like Excel, data analysis, communication, etc. But we already have those in required experience. Might be redundant. Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must use all; we include only when posting has real specific content. So we could have Requirements (covering education and required experience) and Qualifications (covering preferred experience). Skills maybe not needed separately if covered. We also have Benefits section: we have benefits described. Pay: The posting includes salary range $20—$22 USD. So we need Pay section. Schedule: Not mentioned; no schedule info. So we omit Schedule. We also need to include any other metadata like Job ID etc - we drop. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? We can paraphrase but must preserve all info. Safer to copy the sentences. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc; we must remove that. Also the "Inspire Medical Systems provides equal employment opportunity..." etc. Remove. Also remove the duplicated lines: The posting includes "WHY JOIN OUR FAST-GROWING TEAM" and later benefits description; we need to avoid duplication. We need to output only HTML fragment. Let's extract substantive content: Company description: "About Inspire Medical Systems Inspire is the first of its kind medical device designed to make a difference in the lives of those living with Obstructive Sleep Apnea (OSA). We are revolutionizing the sleep industry with our FDA-approved medical device, designed to reduce OSA severity for those who cannot tolerate or get consistent benefit from CPAP. Inspire Medical Systems is committed to enhancing patients’ lives through sleep innovation. We are steadfast in our commitment to prioritize patient outcomes, act with integrity and lead with respect. With positive persistence at our core, we are committed to all those we serve." But is this needed? It's about the company, not the role. The instruction says we should not repeat job title as heading, but we can include company description? It's substantive info about the employer. Might be okay to include under About the role? But About the role heading is for role description. However we could include a short paragraph about the company under About the role? Might be weird. Perhaps we can include a section "About the company"? Not in allowed headings. The allowed headings list does not include About the company. So we might omit company description to stay within allowed headings. However the instruction says "Prefer a few substantive sections over many thin ones." It didn't forbid including extra info not under those headings, but they said use those headings for section headings. It didn't say we cannot have other headings, but they gave examples. Safer to stick to allowed headings. Thus we will not include the company description; we will focus on role summary, responsibilities, qualifications, benefits, pay. Position Summary: The paragraph after "Position Summary". Let's capture: "The Summer FP&A Intern will join the Financial Planning & Analysis team for an immersive, hands-on experience supporting the analytical engine behind the company's revenue and growth strategy. Working alongside experienced financial analysts, the intern will contribute to building and refining models that quantify revenue growth drivers, evaluate account/physician-level performance to identify the qualities that most strongly correlate with growth, and connect leading and lagging key performance indicators (KPIs) to future financial outcomes. This role is ideal for a motivated student who wants to translate classroom finance and analytics into real business impact—partnering cross-functionally, wrangling and interpreting data, and presenting findings that inform forecasting, planning, and executive decision-making. Over the course of the internship, the intern will develop practical proficiency in financial modeling, data analysis, and business storytelling while gaining exposure to how a high-growth organization plans, measures, and drives sustainable performance." We'll put that under

    About the role

    as a

    . Responsibilities: list of duties: - Support revenue modeling: Assist in building and maintaining financial models that isolate and quantify the primary drivers of revenue growth (e.g., volume, mix, new-account contribution, and productivity). - Conduct account and physician analysis: Analyze data to identify the characteristics and behaviors that distinguish high-growth customers from stagnant ones and summarize the drivers behind the trends. - Link KPIs to forward performance: Help evaluate how leading indicators and operational KPIs (pipeline, productivity, utilization, etc.) factor into future revenue and forecast accuracy. - Prepare analysis and reporting: Compile data from multiple sources, perform variance and trend analysis, and build clear, accurate outputs (tables, charts, dashboards) for stakeholder review. - Contribute to planning cycles: Provide analytical support for forecasting, budgeting, and business review deliverables. - Ad hoc projects: Support special analyses and process-improvement initiatives as needed throughout the internship. Then Quality System Responsibilities: - Document product and therapy related field reports within the prescribed timelines and provide any necessary documents required to complete the investigation. - Provide follow-up reporting as needed. - Complete training requirements and competency confirmations as required for this position within the required timeline. - Comply with applicable quality system procedures/policies and make suggestions for continuous process improvement. We'll combine all as

    • under Responsibilities. Requirements: Education and GPA, plus required experience. Education: "Currently enrolled in an accredited undergraduate or graduate program, pursuing a degree in Finance, Accounting, Economics, Business Analytics, Data Science, or a related quantitative field. Expected graduation date following the completion of the internship (rising junior, rising senior, or graduate student preferred). Minimum cumulative GPA of 3.0 (or equivalent) preferred." Required Experience: "Strong proficiency in Microsoft Excel, including formulas, functions, and building or working within financial models. Foundational understanding of core financial and accounting concepts (revenue, margins, forecasting, variance analysis). Demonstrated analytical and quantitative problem-solving skills, with strong attention to detail and accuracy. Ability to organize, interpret, and draw insight from large data sets. Effective written and verbal communication skills and the ability to present findings clearly. Comfort working both independently and collaboratively in a fast-paced, deadline-driven environment." We'll put these under

      Requirements

      with maybe

      for each bullet? Could use

      • for each requirement. But the instruction says use
        • for any list of duties/requirements/benefits. So we should list each requirement as
        • . We'll break them into items. Qualifications: Preferred experience: "Prior internship, coursework, or project experience in FP&A, corporate finance, consulting, or data analytics. Strong communication and teamwork skills. Comfort working in a collaborative, cross-functional environment. Familiarity with data visualization or BI tools (e.g., Power BI, Tableau) and/or data tools such as SQL or Python. Interest in the medical device, healthcare, or life sciences industry." We'll put under

          Qualifications

          as
          • . Skills: Could be separate but we already covered skills in requirements and qualifications. Might not need separate. Benefits: The posting includes benefits description under "Benefits And Other Compensation". Also earlier "WHY JOIN OUR FAST-GROWING TEAM" mentions excellent benefits, 401k matching, ESPP, flexible time off (FTO), tuition reimbursement. We'll combine. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all benefit items listed: - Multiple health insurance plan options. - Employer contributions to Health Savings Account. - Dental, Vision, Life and Disability benefits. - 401k plan + employer match. - Identity Protection. - Flexible time off. - Tuition Reimbursement. - Employee Assistance program. - All employees have the opportunity to participate in the ownership and success of Inspire. Employees at all levels can participate through equity awards and the Employee Stock Purchase Program. Also earlier: "excellent benefits, 401k matching, ESPP, flexible time off (FTO), and tuition reimbursement." ESPP is Employee Stock Purchase Program, already covered. We'll list each as
          • under Benefits. Pay: Salary range $20—$22 USD. We'll put under

            Pay

            with

            maybe. Schedule: none. We must not include boilerplate like EEO statement etc. Now produce HTML fragment. We'll start with

            About the role

            ...

            Then

            Responsibilities

            • ...
            • ...
            Then

            Requirements

            • ...
            • ...
            Then

            Qualifications

            • ...
            • ...
            Then

            Benefits

            • ...
            • ...
            Then

            Pay

            Salary range: $20—$22 USD.

            Make sure to preserve the dash— it's an em dash? In text it's "$20—$22 USD". We'll keep that. Check for any duplicated lines: We

Similar jobs