Senior Software Engineer — Product

We need to output HTML fragment with sections: About the role (maybe as heading), Responsibilities (What you'll own), Requirements (Required technical skills maybe plus Experience we're looking for?), Qualifications? Skills? Benefits? Pay? Schedule? The posting includes: "This is an in-person role requiring 5 day/week in our NYC office." That's schedule info (in-person, 5 days/week). So we can include a Schedule section with that. Benefits: list of benefits (Health, dental, vision insurance, base plans 100% employer paid, Pre-tax benefits..., Flexible paid time off..., 401(k) with company match). Also maybe "Amazing people..." etc but that's more culture; could be part of Benefits? Not needed. We'll include Benefits section. Pay: not mentioned, so omit. We need headings:

for each section: About the role, Responsibilities, Requirements, Skills?, Benefits, Schedule. Possibly also Qualifications? The posting includes "Experience we’re looking for" and "Nice to have". Could treat as Requirements (required technical skills) and Qualifications (experience). But we can combine. The instruction: prefer few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements (technical skills + experience), Benefits, Schedule. We must not repeat job title. No Job ID. We must preserve all substantive information. So we need to include all bullet points from responsibilities, required technical skills, experience we're looking for, nice to have, benefits, schedule. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include boilerplate like EEO etc. Remove that. We must not include navigation/cookie etc. We must not include application instructions (like "For more information about our company, please visit our website:"). We must not include duplicated lines. We must not include placeholder text. We need to ensure we include all substantive info. Let's extract: About Inspira Education: description paragraph. That's about company, not role. Should we include? The instruction: "About the role" heading for role specifics. The company description may be considered part of About the role? Might be considered background. Could include as a

  under About the role? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role section containing both company description and role overview? The posting includes "About Inspira Education" then "About the role". We could combine company description into About the role as introductory prose. That seems okay. Thus About the role section:

  About the role

  then a

  containing the company description paragraph(s) and the role overview paragraph: "We’re looking for a strong full-stack engineer who can own the complete product development process..." etc. Then Responsibilities: heading

  Responsibilities

  then
  with each bullet from "What you’ll own". Those bullet points are: - Translate business needs and user feedback into product requirements, user flows, prototypes, and prioritized development plans. - Design and build polished applications across the front end, back end, database, and integrations. - Make architecture decisions and scope releases that balance speed, reliability, and future maintainability. - Use AI tools throughout development to accelerate implementation, testing, debugging, and documentation. - Own deployment, production monitoring, incident resolution, and ongoing improvements. - Measure whether your work improves adoption, conversion, operational efficiency, or another relevant business outcome. We'll list each as
  • . Then Requirements: heading

    Requirements

    . We need to include required technical skills (front-end, back-end, databases, deployment, testing/security/code quality, AI-assisted software development) plus experience we're looking for (Typically 5+ years..., track record..., examples..., experience taking loosely defined problems...). Also nice to have could be included but maybe as part of Requirements? Could be separate Skills? But we can include nice to have as part of Requirements as additional bullet points maybe under a sublist? However instruction: prefer few substantive sections. Could combine required and nice to have under Requirements, but we should differentiate? Not required. We'll just list all as bullet points under Requirements. We need to preserve all substantive info: So list each bullet from required technical skills categories. That's a lot. We'll need to break them into items. Let's extract required technical skills sections: Front-end engineering: - Strong proficiency in TypeScript, JavaScript, React, and Next.js, including component architecture, hooks, routing, and client/server rendering. - Strong HTML and CSS skills, with the ability to implement responsive layouts and consistent visual design. - Experience managing forms, validation, application state, asynchronous data, caching, and loading/error states. - Ability to diagnose rendering issues and improve page performance, bundle size, and unnecessary network requests. - Ability to build accessible interfaces with semantic markup, keyboard navigation, and appropriate focus management. Back-end development and API design: - Strong proficiency in Node.js and TypeScript, using a framework such as Express, NestJS, or an equivalent. - Experience designing and implementing REST APIs, including validation, pagination, consistent error handling, and API documentation. - Experience implementing authentication, authorization, role-based access, and third-party integrations. - Ability to build reliable background jobs and webhook processing, including retries, duplicate-event handling, and failure recovery. - Understanding of timeouts, rate limits, caching, and common application bottlenecks. Databases and data modeling: - Strong practical knowledge of PostgreSQL and SQL. - Ability to design relational schemas, relationships, constraints, and indexes. - Experience with database migrations, transactions, and investigating slow queries. - Familiarity with an ORM such as Prisma or Drizzle, along with the ability to inspect and optimize the underlying SQL. - Ability to handle data integrity, concurrent updates, and safe changes to production data. Deployment and production operations: - Experience independently deploying and operating applications on a cloud platform such as AWS, GCP, Azure, or Vercel. - Working knowledge of Git, pull requests, CI/CD pipelines, environment configuration, and secrets management. - Familiarity with Docker and reproducible development environments. - Ability to set up useful logs, error tracking, monitoring, and alerts. - Experience handling releases, database migrations, rollbacks, and production debugging. Testing, security, and code quality: - Ability to write meaningful unit, integration, and end-to-end tests using tools such as Vitest/Jest and Playwright/Cypress. - Strong debugging skills across browser behavior, API requests, application logs, and database queries. - Practical understanding of secure sessions, server-side permission checks, input validation, SQL injection, XSS, and protection of sensitive data. - Ability to structure maintainable code, review changes critically, and refactor without breaking existing behavior. AI-assisted software development: - Regular, hands-on use of tools such as Cursor, Claude Code, GitHub Copilot, or Codex. - Ability to give AI tools useful repository context, break complex work into verifiable tasks, and guide implementation across multiple files. - Ability to evaluate generated code for correctness, security, maintainability, and compatibility with the existing application. - Experience using tests, type checks, linting, and code review to validate AI-generated changes. - Ability to explain and debug the resulting code independently and recognize when an AI-generated approach should be revised or discarded. Experience we’re looking for: - Typically 5+ years of software engineering experience, or equivalent evidence of substantial independent ownership. - A track record of shipping and maintaining full-stack production applications. - Examples of features or products where you personally influenced the requirements, design, and implementation. - Experience taking loosely defined problems through to a working release. Nice to have: - Python and FastAPI. - Experience building AI features using model APIs, structured outputs, tool calling, or retrieval, with attention to evaluation, latency, and cost. - Experience integrating CRMs, payment systems, analytics platforms, or business workflow tools. - Experience as an early startup engineer or independent product builder. We'll include all these as bullet points under Requirements. Benefits: heading

    Benefits

    then
    with items: - Health, dental, and vision insurance, base plans 100% employer paid - Pre-tax benefits (FSA, DCFSA, HSA, Commuter) - Flexible paid time off (PTO) and paid holidays - 401(k) with company match Also maybe "Amazing people with a great vision and values..." but that's more culture; could be omitted as not a benefit. We'll keep only those. Schedule: heading

    Schedule

    then

    containing "This is an in-person role requiring 5 day/week in our NYC office." We must not include Pay section. Now ensure we don't repeat any heading without content. All sections have content. Now produce HTML fragment. We need to wrap each section in appropriate tags:

    About the role

    then

    ... maybe multiple paragraphs? We'll combine into one

    with line breaks? Could use multiple

    but instruction: use

    for prose. Could have multiple

    paragraphs. We'll do separate

    for company description and role overview. Let's craft:

    About the role

    Inspira Education Group is one of the fastest-growing edtech startups in the US. We started with a simple mission to democratize access to high-quality coaching so that every student in the world has an equal opportunity to access the best opportunities. As the world’s leading network of top admissions coaches in medical, legal, business, and college studies, we’re building software and services in one place—disrupting long-entrenched application processes with products and experiences that strive to provide an equal platform for candidates from diverse backgrounds worldwide. As one of the fastest-growing edtech firms in the world, we are backed by some of the leading venture capital firms and investors in the world, including Zeev Ventures, Quiet Capital, Craft Ventures and Jeff Fluhr (Founder of Stubhub).

    We’re looking for a strong full-stack engineer who can own the complete product development process: understand a business problem, define the solution, design the user experience, build the software, and improve it after launch. You’ll work closely with leadership and business teams, combining hands-on engineering with product management and design responsibilities. You should be highly effective with AI coding tools and have the technical depth to independently review, debug, secure, and maintain everything you ship. This is an in-person role requiring 5 day/week in our NYC office.

    But note schedule sentence appears also in the role overview; we might move schedule to its own section and not duplicate. However we need to preserve all substantive info; we can keep schedule sentence in About the role but also have Schedule section. That would duplicate. Better to remove schedule sentence from About the role and put it in Schedule section. But we must preserve all info; we can keep it in Schedule section and not repeat. So we should edit About the role paragraph to exclude the schedule sentence. Let's adjust. Thus About the role paragraph: remove "This is an in-person role requiring 5 day/week in our NYC office." from that paragraph. Now Schedule section will have that sentence. Now Responsibilities section as above. Now Requirements section: we need to list all bullet points. We'll create a
    with many
    • . Might be long but okay. We need to ensure we don't lose any nuance. Let's craft the Requirements
      with each bullet as a separate
      • . We'll group maybe by category but still each bullet as
      • . We'll keep the exact phrasing. Let's list them: Front-end engineering: - Strong proficiency in TypeScript, JavaScript, React, and Next.js, including component architecture, hooks, routing, and client/server rendering. - Strong HTML and CSS skills, with the ability to implement responsive layouts and consistent visual design. - Experience managing forms, validation, application state, asynchronous data, caching, and loading/error states. - Ability