Software Engineer II (Remote)

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Not present. Responsibilities? Yes. Requirements? Yes. Qualifications? Might be combined. Skills? Could be separate. Benefits? Yes. Pay? Yes. Schedule? Not present. We must not include sections without real content. Also we must not repeat job title heading. Remove boilerplate. Keep all substantive info. We need to parse the posting. Let's extract sections: - Intro about company: maybe not needed as a section? Could be "About the role"? Not exactly. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include sections that have content. We have: Job Summary & Responsibilities: includes description of role, responsibilities. Then "Duties & Responsibilities:" with bullet list. Then "Preferred Qualifications Education & Experience:" with bullet list. Then "Required Skills Technical Proficiency and Skills:" with bullet list. Then "Preferred Skills" bullet list. Then "Other Requirements" bullet list. Then "Pay Range $87,100-$111,000 per year" Then "Compensation & Benefits" paragraph. We need to map to headings: - Responsibilities: combine Job Summary & Responsibilities and Duties & Responsibilities. - Requirements: maybe combine Preferred Qualifications Education & Experience and Other Requirements? But we have separate sections: Qualifications, Skills. Could do Qualifications (education/experience), Skills (technical). Also maybe Requirements as a broader? The instruction says we can use those headings; we should only include if content. We have content for Qualifications (Education & Experience). Also for Skills (Technical Proficiency and Skills, Preferred Skills). Also for Benefits and Pay. We should not create sections with placeholder like "commensurate with experience". Not present. We need to output only HTML fragment. We'll structure:

Responsibilities

Job Summary & Responsibilities Software Engineer II will play a critical role in ensuring the reliability and efficiency of our systems, which in turn drives customer delight. The Support Engineer role will help Inspira maintain operational excellence. This role is an excellent opportunity for someone looking to gain hands-on technical experience while working across multiple teams, and will be at the intersection of engineering, operations, and customer success, helping to diagnose issues, triage requests, execute data corrections, and ensure our systems run smoothly. This role supports critical health benefits infrastructure such as HSA administration, banking integrations, and regulatory compliance. Support Software Engineer II work directly with production data involving real money movement, tax reporting, and multi-bank operations.

• Support Engineering and Operations
• Ability to independently handle escalations end-to-end without manager intervention
• Demonstrated judgement on when to escalate vs. resolve, especially around money movement and compliance-sensitive issues
• Track record of identifying recurring support patterns and proposing systemic improvements
• Coach and mentor less experienced teammates on troubleshooting approaches and best practices
• Respond to internal support requests from various teams and assist in troubleshooting and fixing technical issues such as executing data corrections, processing trustee-to-trustee transfers and settlements, and overseeing money movement and remediation efforts
• Identify and route unresolved issues to the appropriate engineering or product teams for further action
• Leverage AI as a tool, not a replacement - Candidates are expected to understand that AI is a power productivity multiplier while maintaining engineering judgment, and ensuring AI generated code meets quality standards
• System Monitoring and Incident Triage
• Monitor operational dashboards, error logs, and alerting systems to ensure system health and performance and address ongoing technical issues
• Identify and escalate any anomalies or critical system alerts that require immediate attention
• Monitor error reports, and logs and operational dashboards to help diagnose and address ongoing technical issues
• Ensure that critical alerts and operational failures are addressed by the relevant teams
• Cross-Team Collaboration and Learning
• Act as a liaison between engineering support and delivery teams, translating support trends into actionable requirements
• Ownership of runbook creation and maintenance, not just consumption
• Contribute to incident postmortems and driving follow-up action items
• Partner with engineering, product, treasury and operations teams to refine internal troubleshooting processes
• Continuously develop a deeper understanding of internal systems and tools such as HSA regulations, banking integrations, and investments
• Document troubleshooting procedures findings and contribute to knowledge-sharing efforts
• Identify patterns in support requests that could inform product or engineering improvements
• Actively participate in team discussions and process improvements
• Other duties as assigned

Then Qualifications:

Qualifications

• 2+ years of experience in software engineering or support engineering roles
• Strong analytical and problem-solving skills
• Practical AI experience required - Comfortable using tools such as Claude Code, GitHub Copilot, ChatGPT for prototyping, debugging, and problem-solving
• Bachelor’s degree in computer science or equivalent experience

Then Skills: We have Required Skills and Preferred Skills. Could combine under Skills heading.

Skills

• Working understanding of jsTypeScript and React
• Git Version Control System
• Database (e.g. Postgres SQL)
• Cloud Platform (e.g. GCP)
• Excellent communication and teamwork skills
• Great attention to detail and organizational skills
• Willingness to learn and adapt in a fast-paced environment
• Familiarity with observability tools (Data Dog or similar)
• Understanding of GraphQL
• Experience with writing and maintaining technical documentation
• Experience with banking/payment APIs such as Plaid (or similar)
• Experience with Google BigQuery or similar data warehousing tool
• Strong sense of ownership and follow-through
• Prior experience in a customer support or technical troubleshooting role

Other Requirements: travel, overtime, sitting. Could be under Requirements? But we already have Qualifications and Skills. Could add a section "Other Requirements". But instruction only lists example headings; we could still use other heading if content. But better to incorporate into Qualifications or Skills? Travel etc not exactly qualifications or skills. Could create a section "Requirements" for those. However we already used Qualifications. Maybe we should use "Requirements" heading for things like travel, overtime, sitting. But we also have Qualifications. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications. Let's do: - Requirements: includes Other Requirements (travel, overtime, sitting). - Qualifications: education/experience. - Skills: technical. Thus:

Requirements

• Infrequent travel (10%)
• Ability to occasionally work overtime or after hours
• Prolonged periods of sitting at a desk and working on a computer

Now Benefits:

Benefits

Inspira provides industry-leading benefits including, but not limited to: healthcare, 401K savings plan, company holidays, paid time off, parental leave and an employee assistance program.

Pay:

Pay

Pay Range $87,100-$111,000 per year

We also have mention about compensation varying depending on location, skills, experience and incentive/bonus opportunities. Could include in Pay section. Let's incorporate: "The compensation for this position will vary depending on factors such as your location, skills and experience. The compensation package may also include incentive and bonus opportunities." So include that in Pay section. Thus Pay section:

Pay

Pay Range $87,100-$111,000 per year. The compensation for this position will vary depending on factors such as your location, skills and experience. The compensation package may also include incentive and bonus opportunities.

Now ensure we didn't include any boilerplate like "Join Us! Take the next step..." etc. We removed intro fluff? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The intro about mission etc is not boilerplate but maybe considered fluff. However it's substantive about company. Should we keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The intro about mission, values, recognition is substantive. Should we include? Possibly under "About the role" or "About the company". But we have no heading for About the role; we could add an About the role section with that content. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role if there is real specific content. The intro includes mission, values, recognition. That's substantive. So we should add an About the role section. Thus:

About the role

Join Us! Take the next step in your journey at Inspira Financial. Guided by our mission to enable better health and greater wealth, we help businesses and individuals thrive today, tomorrow, and into retirement by strengthening and simplifying the health and wealth journey. Serving more than 7 million clients and representing over $62 billion in assets, Inspira partners with thousands of employers, plan sponsors, recordkeepers, TPAs, and other institutional partners to help the people they support plan, save, and invest for a brighter future. Through solutions including automatic rollover services, health savings accounts, emergency savings, and custody services, Inspira is focused on delivering better outcomes for all. Learn more at inspirafinancial.com. Our values shape how we show up every day. We Lead with Heart by acting with compassion, empathy, and doing what's right; Cultivate Trust through integrity, transparency, and accountability; Aim Higher by never settling for what's expected and continually raising the standard; and Win Together by collaborating inclusively to achieve the best outcomes. Our growth and culture haven't gone unnoticed -- we've been recognized on Crain's Fast 50 and Inc. 5000 for remarkable growth, and named to Built In's 2025 Best Places to Work and Gallagher's 2022 Best-In-Class Employer for our workplace culture and benefits.

We should remove fluff like "Don't meet every single requirement? That's okay..." maybe that's also substantive about encouragement. Could include in About the role or maybe separate. It's about encouraging applicants. Could be part of About the role. We'll keep it. Add after recognition: "Don't meet every single requirement? That's okay. We know growth comes from people who are willing to learn and challenge themselves, not just check every box. If you're energized and inspired by meaningful work, continuous development, and being part of a team that turns collective effort into real impact, we want to hear from you. We look forward to receiving your application." But note: we should remove application instructions? The instruction says remove application instructions. The line "We look forward to receiving your application." is arguably an application instruction. Might be considered boilerplate? It's encouraging to apply. Might be considered application instruction. Safer to remove that line. Also "Remote status and role locations are subject to change, and relocation is not provided." That's about location; could be under Requirements? It's not a requirement but a note. Could be under Requirements or