Product Engineer
or drop it." The company description is not a heading; we can include as a
before sections? Probably we can include a brief paragraph about the company as part of the content, but not as a heading. The rules: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need sections: About the role (we have that), Responsibilities (we have "What you’ll own"), Requirements (we have "Required technical skills" maybe also "Testing, security, and code quality" etc but that's part of technical skills; we can combine under Requirements), Qualifications (we have "Experience we’re looking for" and "Nice to have"), Skills (we have "Product and design skills"), Benefits (we have list), Schedule (we have in-person role requiring 5 day/week in NYC office). Pay not present, omit. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. At the end there is EEO statement; we should remove that. Also "For more information about our company, please visit our website: Inspira Education Group." That's maybe minor metadata; we can fold into a short
or drop. Probably we can keep a short
with that line? It's minor metadata; we can fold into a short
or drop. Safer to drop? The instruction: fold minor metadata into a short
or drop it. So we can include a short
with that line. We must output only HTML fragment, no /, no markdown fences. Let's craft:
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. This is an in-person role requiring 5 day/week in our NYC office.
But schedule is separate section; we might move schedule info to Schedule section. However the About the role includes schedule mention; we could keep it there but also have Schedule section. To avoid duplication, we could keep schedule mention in About the role and not create separate Schedule section? But rule: include a section ONLY when posting has real, specific content for it. The schedule content exists (in-person role requiring 5 day/week in NYC office). So we should have a Schedule section with that detail. Then we should not duplicate it in About the role. So we need to extract schedule info into its own section and remove from About the role. Thus About the role paragraph: remove schedule sentence. Let's rewrite 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." Now Schedule section:Schedule
This is an in-person role requiring 5 day/week in our NYC office.
Now Responsibilities: Use "What you’ll own" list. We need to convert each bullet into- . The bullet points:
- 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 put under
Responsibilities
- ...
? But only
allowed for section headings per instruction? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can keep them as
with bold? But we need to preserve content; we could keep subheadings as inside
or as
but not required. Safer to keep them as
...
then lists. Thus Requirements section:Requirements
then for each area:Front-end engineering
- ... etc.
We must include all bullet points exactly as given.
Let's extract each:
Front-end engineering bullets:
- 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 bullets:
- 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 bullets:
- 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 bullets:
- 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 bullets:
- 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 bullets:
- 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 Qualifications section: includes "Experience we’re looking for" and "Nice to have". We'll have
Qualifications
then maybe two subparts: Experience we’re looking for (list) and Nice to have (list). We'll preserve bullet points. Experience we’re looking for bullets: - 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 bullets: - 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. Now Skills section: "Product and design skills" with sub-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. We'll put underSkills
with- .
Now Benefits section: list:
- 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
We'll put under
Benefits
with- .
Now we need to include a short
for minor metadata: "For more information about our company, please visit our website: Inspira Education Group." Could be placed after Benefits or at end. We'll add a
at end. We must not include EEO statement. Now ensure we don't repeat any content inadvertently. Let's construct HTML. We'll start with maybe a
for company description? The initial "About Inspira Education" paragraph is descriptive; we could include that as a
before sections. It's substantive info about company. Not a heading. We'll include it as a
. Thus output:
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