Founding AI Product Engineer
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We have content: "About the role" paragraph describing role. Then "What you’ll own" list of duties. That's responsibilities. Then "Required technical skills" with subcategories: Front-end engineering, Back-end development and API design, Databases and data modeling, Deployment and production operations, Testing, security, and code quality, AI-assisted software development, Product and design skills. Those are skills/requirements. Then "Experience we’re looking for" (experience). Then "Nice to have" (optional). Then "Why you'll love Inspira" includes benefits: health, dental, vision insurance, pre-tax benefits, flexible PTO, 401(k) match. Also maybe "Amazing people..." etc. No explicit Pay or Schedule. So we should not create Pay or Schedule sections. Benefits section we can include. Also maybe "About Inspira Education" is company description; we could put as a short paragraph maybe not a heading? The instruction: 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. We can include "About Inspira Education" maybe as a
not heading. But we could also treat as "About the company" but not in list; better to just include as a paragraph before sections. We need to preserve all substantive information, not invent. Remove boilerplate like EEO etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. The posting includes "For more information about our company, please visit our website: Inspira Education Group." That's maybe not needed but it's substantive? It's a link; we could keep as a
. Also the EEO statement at end should be removed. We need to output only HTML fragment, no markdown fences. Let's structure:
About Inspira Education ...
About the role
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.
Responsibilities
- 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.
Required Technical Skills
We could break into subheadings? The instruction only allows those specific headings; but we can still use for sections like Front-end engineering etc? It didn't forbid other headings, but said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. However we have a lot of skill categories; we could group under "Skills" heading and list items. But we need to preserve all detail; we can put a with each skill category as - containing sublist? That might be okay. Or we could create multiple
subsections like "Front-end engineering", but that deviates from prescribed headings but not prohibited. 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 other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. But we have many skill categories; we could put them under a single "Skills" heading and list them. That would lose some granularity but still preserve all info as list items. That's acceptable.
Similarly "Experience we’re looking for" could go under "Requirements" or "Qualifications". We have "Experience we’re looking for" and "Nice to have". Could put under "Requirements" and "Qualifications". But we need to avoid filler. Let's map:
- About the role: we have.
- Responsibilities: we have.
- Requirements: could include "Experience we’re looking for" (Typically 5+ years...).
- Qualifications: maybe "Nice to have" (optional).
- Skills: Required technical skills + Product and design skills.
- Benefits: Why you'll love Inspira (benefits).
- Pay: none -> omit.
- Schedule: none -> omit.
We also have "About Inspira Education" as company description; could be a
before sections.
Let's craft:
About Inspira Education 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).
About the role
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.
Responsibilities
- 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.
Requirements
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.
Qualifications
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.
Skills
- 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.
- Product and design skills: Product discovery: Speak with users, understand workflows, identify the underlying problem, and challenge assumptions constructively. Prioritization: Define a focused first release, make scope trade-offs, and connect engineering effort to business value. Interaction design: Create user flows and prototypes using Figma or code, including edge cases and failure states. Visual execution: Apply sound judgment around typography, spacing, hierarchy, consistency, and responsive behavior. Measurement: Instrument important user actions and combine analytics with feedback to guide improvements. Communication: Explain decisions clearly and coordinate with nontechnical stakeholders.
Benefits
- Health, dental, and vision insurance, base plans 100% employer paid
- Pre-tax benefits (FSA, DCFSA, HSA, Commuter)
- Flexible
- with each skill category as
- containing sublist? That might be okay. Or we could create multiple
subsections like "Front-end engineering", but that deviates from prescribed headings but not prohibited. 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 other headings if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. But we have many skill categories; we could put them under a single "Skills" heading and list them. That would lose some granularity but still preserve all info as list items. That's acceptable. Similarly "Experience we’re looking for" could go under "Requirements" or "Qualifications". We have "Experience we’re looking for" and "Nice to have". Could put under "Requirements" and "Qualifications". But we need to avoid filler. Let's map: - About the role: we have. - Responsibilities: we have. - Requirements: could include "Experience we’re looking for" (Typically 5+ years...). - Qualifications: maybe "Nice to have" (optional). - Skills: Required technical skills + Product and design skills. - Benefits: Why you'll love Inspira (benefits). - Pay: none -> omit. - Schedule: none -> omit. We also have "About Inspira Education" as company description; could be a
before sections. Let's craft:
About Inspira Education 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).
About the role
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.
Responsibilities
- 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.
Requirements
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.
Qualifications
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.
Skills
- 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.
- Product and design skills: Product discovery: Speak with users, understand workflows, identify the underlying problem, and challenge assumptions constructively. Prioritization: Define a focused first release, make scope trade-offs, and connect engineering effort to business value. Interaction design: Create user flows and prototypes using Figma or code, including edge cases and failure states. Visual execution: Apply sound judgment around typography, spacing, hierarchy, consistency, and responsive behavior. Measurement: Instrument important user actions and combine analytics with feedback to guide improvements. Communication: Explain decisions clearly and coordinate with nontechnical stakeholders.
Benefits
- Health, dental, and vision insurance, base plans 100% employer paid
- Pre-tax benefits (FSA, DCFSA, HSA, Commuter)
- Flexible