Software Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key content: - iFIT vision description (intro). Could be part of About the role? The posting says: "iFIT’s vision is to create the world's most holistic health and fitness platform..." That's about company. Could be part of About the role. - "We are currently seeking an ambitious pace-setter to join our team as a Software Engineer remotely in the US." That's about role. - "iFIT is looking for a mid-to-senior level Software Engineer to design and build the backend services powering iFIT's interactive fitness experiences." - "In this role, you will work on a service-oriented architecture in AWS, primarily using TypeScript and NestJS to create scalable microservices." - "Your contributions will directly impact millions of users worldwide, ensuring our platform remains reliable, performant, and primed for innovation." - "You will help drive the evolution of our APIs from REST to GraphQL, modernize legacy systems, and integrate with billing platforms such as Stripe, Apple, Google, and more." - "To facilitate collaboration, you must be available during core hours of 10 AM - 3 PM US Mountain Time, and will participate in a rotating on-call schedule approximately one week per rotation with the team." - Then "ROLE COMMITMENTS" bullet list: Develop and maintain backend microservices in TypeScript and NestJS deployed via AWS ECS, ensuring services are well-designed, scalable, and aligned with our service-oriented architecture and best practices. Design, implement, and document robust RESTful APIs that are secure, efficient, and easy for client teams to use. Help migrate legacy serverless functions from AWS Lambda into containerized services on ECS, refactoring and re-architecting older systems for improved performance, maintainability, and consistency across the platform. - Then "ESSENTIAL DUTIES AND RESPONSIBILITIES": Work closely with front-end and mobile teams, product managers, and designers to deliver end-to-end features, clarify requirements, review designs, and ensure seamless integration across multiple services. Write clean, well-tested code and participate in peer code reviews, maintaining comprehensive unit and integration tests and continuously improving CI/CD pipelines. Take ownership of the reliability of the services you build, monitor performance, troubleshoot production issues, and participate in a rotating 24/7 on-call schedule to quickly address critical incidents and minimize downtime. - Then "EDUCATION & EXPERIENCE": Education And Basic Qualifications list: 4+ years of professional software engineering experience building backend or full-stack applications in a cloud environment. Strong proficiency in TypeScript/JavaScript and Node.js with hands-on experience with backend frameworks — NestJS strongly preferred, or similar frameworks like Express/Koa with a willingness to learn NestJS. Solid knowledge of AWS services and architecture, with experience deploying and running containerized applications in AWS ECS, EKS, or similar, and familiarity with microservices, distributed systems, and event-driven architecture. Proven experience designing, building, and consuming RESTful APIs with a strong understanding of API security and performance considerations. Experience with relational and NoSQL databases such as PostgreSQL, MySQL, and MongoDB, as well as caching mechanisms such as Redis, with the ability to write efficient queries and optimize data access in a cloud environment. Comfortable with CI/CD pipelines and infrastructure-as-code tools such as Terraform or CloudFormation, and knowledge of monitoring and logging tools such as CloudWatch and Datadog. Ability to jump into unfamiliar projects quickly and work across different services and tech stacks as needed. Excellent communication and collaboration skills with a team-oriented mindset and a habit of knowledge sharing and proactive problem-solving. Authorized to work in the United States without sponsorship. - Preferred Qualifications: Deep understanding of microservice design patterns, inter-service communication including REST, gRPC, and message queues, and related tooling such as API gateways and service mesh. Familiarity with Claude Code or similar AI coding assistants. Experience with DevOps or Site Reliability Engineering practices including automated testing, continuous deployment, and infrastructure monitoring. Experience with Stripe's broad set of products and third-party subscription providers such as Apple App Store or Google Play subscription platforms. - Then DISCLAIMER: Compensation may vary based on the job level, your geographic work location, position incentive plan, and exemption status. Although we currently may consider hiring in the states listed below, not all positions are available in all locations, and work in a particular state is not guaranteed. Current list of states where iFIT may consider hiring: AK, AL, AR, AZ, CA, CO, CT, FL, GA, ID, IL, IN, KS, KY, LA, MA, MD, MI, MN, MO, MS, NC, NH, NJ, NV, NY, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VA, WA, WI, WY. Subject to applicable state laws, your employment at iFIT is "at-will". At-will employment means that you and the company each have the right to terminate the employment relationship at any time for any cause or for no cause at all. Pay Range: : $120,000 USD - $140,000 USD iFIT does not discriminate in employment opportunities or practices on the basis of race, color, religion, sex, national origin, age, ancestry, mental or physical disability, sexual orientation, gender identity, medical condition, genetic information, marital status, veteran status or any other characteristic protected by law. We need to remove boilerplate: legal, EEO, disclaimer about at-will, states list maybe considered metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The list of states could be considered metadata; we could fold into a short

or drop it. Probably drop it as it's not essential? But we need to preserve ALL substantive information; the list of states is substantive about where they may hire. Could be considered metadata but still substantive. However we can include as a short paragraph under maybe About the role or a separate section? There's no specific heading for location. Could include in About the role paragraph. Pay Range: we need to include Pay section only if posting actually states them. Yes, Pay Range: $120,000 USD - $140,000 USD. So we need a Pay section. Schedule: core hours of 10 AM - 3 PM US Mountain Time, rotating on-call schedule approx one week per rotation. Also mention rotating 24/7 on-call schedule in essential duties. So we have schedule info. So we need a Schedule section. Benefits: Not mentioned explicitly. No benefits listed. So we should not create Benefits section. Skills: Could be derived from qualifications; but we have a Skills section maybe we can include if there is specific content. The posting includes many skills: TypeScript, NestJS, AWS ECS, RESTful APIs, etc. Could put under Skills. However we also have Requirements and Qualifications sections. We need to decide which sections to include. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. We have About the role (intro + vision). Responsibilities (role commitments + essential duties). Requirements (education & basic qualifications). Qualifications (preferred qualifications). Skills maybe could be merged into Requirements/Qualifications. Pay. Schedule. We must not create sections with filler like "commensurate with experience". We have real content for each. Thus output:

About the role

iFIT’s vision is to create the world's most holistic health and fitness platform, integrating all elements of health - physical fitness, mental health, nutrition and active recovery - into a seamless interactive experience. We develop proprietary software that learns and adjusts to the habits of each person as it delivers immersive content that guides them on their own individual fitness journey. We are currently seeking an ambitious pace-setter to join our team as a Software Engineer remotely in the US. iFIT is looking for a mid-to-senior level Software Engineer to design and build the backend services powering iFIT's interactive fitness experiences.

Responsibilities

• Develop and maintain backend microservices in TypeScript and NestJS deployed via AWS ECS, ensuring services are well-designed, scalable, and aligned with our service-oriented architecture and best practices.
• Design, implement, and document robust RESTful APIs that are secure, efficient, and easy for client teams to use.
• Help migrate legacy serverless functions from AWS Lambda into containerized services on ECS, refactoring and re-architecting older systems for improved performance, maintainability, and consistency across the platform.
• Work closely with front-end and mobile teams, product managers, and designers to deliver end-to-end features, clarify requirements, review designs, and ensure seamless integration across multiple services.
• Write clean, well-tested code and participate in peer code reviews, maintaining comprehensive unit and integration tests and continuously improving CI/CD pipelines.
• Take ownership of the reliability of the services you build, monitor performance, troubleshoot production issues, and participate in a rotating 24/7 on-call schedule to quickly address critical incidents and minimize downtime.

Requirements

• 4+ years of professional software engineering experience building backend or full-stack applications in a cloud environment.
• Strong proficiency in TypeScript/JavaScript and Node.js with hands-on experience with backend frameworks — NestJS strongly preferred, or similar frameworks like Express/Koa with a willingness to learn NestJS.
• Solid knowledge of AWS services and architecture, with experience deploying and running containerized applications in AWS ECS, EKS, or similar, and familiarity with microservices, distributed systems, and event-driven architecture.
• Proven experience designing, building, and consuming RESTful APIs with a strong understanding of API security and performance considerations.
• Experience with relational and NoSQL databases such as PostgreSQL, MySQL, and MongoDB, as well as caching mechanisms such as Redis, with the ability to write efficient queries and optimize data access in a cloud environment.
• Comfortable with CI/CD pipelines and infrastructure-as-code tools such as Terraform or CloudFormation, and knowledge of monitoring and logging tools such as CloudWatch and Datadog.
• Ability to jump into unfamiliar projects quickly and work across different services and tech stacks as needed.
• Excellent communication and collaboration skills with a team-oriented mindset and a habit of knowledge sharing and proactive problem-solving.
• Authorized to work in the United States without sponsorship.

Qualifications

• Deep understanding of microservice design patterns, inter-service communication including REST, gRPC, and message queues, and related tooling such as API gateways and service mesh.
• Familiarity with Claude Code or similar AI coding assistants.
• Experience with DevOps or Site Reliability Engineering practices including automated testing, continuous deployment, and infrastructure monitoring.
• Experience with Stripe's broad set of products and third-party subscription providers such as Apple App Store or Google Play subscription platforms.

Pay

Pay Range: $120,000 USD - $140,000 USD

Schedule

Core collaboration hours: 10 AM - 3 PM US Mountain Time. Participate in a rotating on-call schedule approximately one week per rotation (including a rotating 24/7 on-call schedule for critical incidents).

We should not include any boilerplate like EEO, at-will, states list, disclaimer. We removed them. Check that we didn