Senior Product Engineer
or drop it." The company description is not a heading; we can include as a
before sections? The output should be only HTML fragment, no /. We can include a
for company overview then sections. We must include sections only when posting has real specific content. We have: - About the role: there is a paragraph "We’re looking for a strong full-stack engineer..." That's about the role. Use
About the role
thencontent. - What you’ll own: list of duties. Use
Responsibilities
then- each bullet.
- Required technical skills: many bullet points grouped under categories. Could be a
Requirements
then maybe sub-sections? But we can just list all as- . Might be long but okay.
- Experience we’re looking for:
Qualifications
then- .
- Nice to have: could be
Skills
then list. - Benefits: health insurance etc.Benefits
then- .
- Schedule: in-person role requiring 5 day/week in NYC office.
Schedule
thenIn‑person role, 5 days/week in the NYC office.
Pay: not present, omit. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from required technical skills, experience we’re looking for, nice to have, benefits. We must not include duplicated lines. Ensure we capture each bullet. Let's extract content. From posting: About Inspira Education paragraph: we can include as abefore sections. About the role paragraph: "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 schedule part we will separate; still include in About the role? Might duplicate. Better to keep About the role without schedule line, and schedule separate. But we must preserve all info; we can keep schedule mention in About the role but also separate schedule section? That would duplicate. Better to keep schedule only in Schedule section and remove from About the role. However the instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we remove schedule mention from About the role, we are not losing info because we put it in Schedule section. That's okay as long as we keep the info somewhere. So we can edit About the role paragraph to exclude the schedule sentence. Thus About the role paragraph: "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." Now Responsibilities (What you’ll own): list: - 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. Now Required technical skills: many bullet points grouped under headings. We'll just list each bullet as
- . Need to capture all.
Let's extract:
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.
Now Product and design skills (maybe under Skills? Actually they are separate bullet list under "Product and design skills". Could be part of Requirements or Skills. We'll treat as part of Requirements maybe under a subsection but we can just include as list under Requirements as well. However we have already a Requirements section; we could add these bullet points there. But we also have a separate "Experience we’re looking for" and "Nice to have". The product and design skills are likely part of Requirements. We'll include them under Requirements as well.
Product and design skills bullets:
- 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.
Now 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.
Benefits:
- 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
Now schedule: In‑person role, 5 days/week in the NYC office.
Now we need to output HTML fragment.
Structure:
About Inspira Education ...
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Schedule
In‑person role, 5 days/week in the NYC office.
We must not include any extra sections like Pay. Check for duplication: Ensure we didn't include schedule sentence elsewhere. Now we need to ensure we preserve all substantive information from the posting. Did we miss any? Let's verify. About Inspira Education paragraph: we included asbefore sections. About the role paragraph: we included. Responsibilities: we included all six bullets. Required technical skills: we included all bullet points under each subheading. Product and design skills: we included. Experience we’re looking for: included. Nice to have: included. Benefits: included. Schedule: included. We omitted the line "This is an in-person role requiring 5 day/week in our NYC office." from About the role, but we placed schedule separately. Good. We omitted the EEO boilerplate at end. We omitted the link "For more information about our company, please visit our website: Inspira Education Group." That's minor metadata; we could fold into short
or drop. We already have a paragraph about Inspira Education; we could keep that and drop the link. The link is minor; we can drop. We omitted "Inspira Education Group does not discriminate..." boilerplate. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now produce HTML. We need to ensure proper escaping of apostrophes etc. Use straight quotes. Let
- .
- Schedule: in-person role requiring 5 day/week in NYC office.
- .
- Nice to have: could be
- . Might be long but okay.
- Experience we’re looking for: