Senior Engineer, Fullstack (Remote, US)

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "Role Summary", "What You Will Do", "Requirements", "Bonuses", "Benefits". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly. We need to include sections only when posting has real specific content. We have: - Who We Are: description of company. Could be "About the role"? Actually "Who We Are" is about company, not role. But we can treat as maybe "About the role"? Not exactly. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings: maybe "About the role" for Role Summary? Or "Responsibilities" for What You Will Do. "Requirements" for Requirements. "Skills" maybe for Bonuses? Or "Benefits" for Benefits. "Pay" for salary info. "Schedule" maybe not present (no schedule specifics). We should not create empty sections. We need to preserve all substantive info, remove boilerplate: EEO, visa sponsorship note, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, EEO, scam-warning, application instructions. Also remove "At this time, Renew Home is unable to sponsor..." etc. Also remove "EQUAL OPPORTUNITY EMPLOYER" block. Also remove "Please contact us to request accommodation." Also remove "We strongly encourage candidates to check out our website..." maybe keep as part of Who We Are? It's not boilerplate? It's promotional but maybe keep? It's not required to remove but it's not boilerplate; but it's a call to action. Might be considered promotional but not prohibited. However we can keep it as part of Who We Are. We need to output only HTML fragment, no /, no markdown fences. Let's extract sections: Who We Are: "Renew Home is on a mission to change how we power the world by making it easier for customers to save energy and money at home as part of the largest residential virtual power plant in North America. We partner with industry-leading brands to better manage residential energy for users by prioritizing efficiency, savings, and comfort — and cleaner energy for everyone. We are an Equal Opportunity employer striving to create a diverse, equitable, and inclusive work environment where everyone feels that they have a voice that is heard. We strongly encourage candidates to check out our website at www.renewhome.com to learn more about the world-changing work we are doing." We need to remove EEO boilerplate? The sentence "We are an Equal Opportunity employer striving to create a diverse, equitable, and inclusive work environment where everyone feels that they have a voice that is heard." is EEO boilerplate. Should be removed. Also "We strongly encourage candidates to check out our website..." maybe keep? It's not boilerplate but it's a call to action; maybe keep as it's substantive? It's not required but we can keep. Thus Who We Are after removal: "Renew Home is on a mission to change how we power the world by making it easier for customers to save energy and money at home as part of the largest residential virtual power plant in North America. We partner with industry-leading brands to better manage residential energy for users by prioritizing efficiency, savings, and comfort — and cleaner energy for everyone." We could also keep the website encouragement? Might be considered not essential but okay. I'd keep it as it's not EEO. But it's a call to action; maybe we can keep. Role Summary: "Renew Home is looking for a strong full stack Software Engineer to join our user Lifecycle & Engagement team and help build and support our consumer-facing platform. In this role, you will work with product, analytics, and the engineering team to develop new features that shape how customers can interact with our product." What You Will Do: list of duties: - Design, develop and build frontend and backend features to support a wide variety of Renew Home customer experiences to enable energy saving automation - Serve as the technical owner of critical product experience flows - Work with cross-functional teams consisting of engineering, analytics, and product management. - Work on many aspects of our stack: Typescript/React, Python, Nx, PostgreSQL, Celery, AWS/GCP (CDK, ECS/EKS, RDS, Redshift, S3, SQS, SES, or equivalent in GCP), Ubuntu, Apache, Redis, Git, Jira - Implement UI and API monitoring tools and proactively monitor performance and stability - Participate in our development process - regular team updates, standup meetings, 1-on-1's and peer code reviews Requirements: - 4+ years of industry experience building fullstack software services - Bachelors/Masters degree in computer science or demonstrated experience in the software industry - Experience building features for scale and performance - using scalable APIs, working with REST frameworks, leveraging components libraries and UI design/token systems - Strong UI development experience, proficiency with React or other modern UI frameworks - Strong SQL skills, proficiency with SQL and no-SQL databases (MySQL, Oracle, Postgres, Redshift, mongodb etc.) - Very strong software engineering background and proficiency in one or more of Typescript, Python, Java, PHP, Ruby - Ability to work through ambiguity, excellent problem solving skills, and attention to detail Bonuses: - Experience with Remix/React Router - Experience with scalable distributed data processing - Experience with AWS Lambda/Cloud functions, pub/sub, Prefect tools - Experience with cloud automation and infrastructure as code (IaC) tools such as Terraform or AWS CloudFormation, AWS CDK - Experience in the electric power industry - Experience working with external partners Benefits: - A full-time position, with a competitive salary based on experience. The base salary for this role is $160k - $200k. In addition to base compensation, this role is eligible for a target annual bonus of 10% of base salary, and participation in long-term incentive programs tied to company growth and performance. We use market data and consider your job family, background, skills, experience, and U.S. work location to determine compensation within our established pay range - Fully remote work environment with home office set-up allowance - Real and lived work-life balance - Company perks include no pre-set vacation limits (with a top-down culture of taking meaningful PTO every year!), parental leave benefits, and a corporate value of working sustainably and putting families first - Competitive benefits package that includes numerous health and wellness benefits - 401(k) plan, with employer contributions to the same. - Opportunity to work with amazing people who are passionate about their mission, thriving in a fully-remote work environment, and learning and growing every day We also have visa sponsorship note: "At this time, Renew Home is unable to sponsor or take over sponsorship of employment visas. Candidates must be authorized to work in the United States without current or future immigration from the company, including training plans for foreign students." This is boilerplate about visa; should be removed. Also EEO block at end: remove. Now we need to map to headings. Possible sections: - About the role? Could combine Who We Are and Role Summary? But we have separate headings: "About the role" maybe for Role Summary. "Who We Are" could be considered "About the company" but not in list. However we could still use "About the role" for Role Summary and maybe omit Who We Are? But we must preserve all substantive information. Who We Are is substantive about company mission. We could put it under a heading like "About the company" but not in allowed list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should use those headings only. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: could be Role Summary (maybe also include Who We Are? but that's about company). We'll put Role Summary under About the role. - Responsibilities: What You Will Do. - Requirements: Requirements list. - Qualifications: maybe education/degree? Could split but we have Bachelors/Masters degree etc. Could put under Qualifications. - Skills: maybe technical skills like UI, SQL, languages, etc. Could put under Skills. - Benefits: Benefits list. - Pay: salary info. - Schedule: maybe not present; we have fully remote work environment but not schedule specifics like hours. Could we treat "Fully remote work environment" as Schedule? Not really. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated; we should omit Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't create empty sections. Now we need to allocate content. About the role: Role Summary paragraph. Responsibilities: bullet list of duties. Requirements: maybe the years of experience, ability to work through ambiguity, etc. But we also have education etc. Could split. Qualifications: education degree. Skills: technical proficiencies (React, SQL, languages, etc.) Bonuses could be considered Skills? Or maybe we could add a "Skills" section that includes both required and bonus skills? But we need to preserve all info; we can include bonuses under Skills as "Preferred skills" or just list them under Skills. Better: Qualifications: education + years experience? Actually years experience is more requirement. Let's decide: - About the role: Role Summary. - Responsibilities: What You Will Do. - Requirements: 4+ years experience, ability to work through ambiguity, problem solving, attention to detail. - Qualifications: Bachelors/Masters degree in CS or demonstrated experience. - Skills: Strong UI development experience (React), Strong SQL skills (SQL and NoSQL), proficiency in Typescript/Python/Java/PHP/Ruby, experience building features for scale and performance (scalable APIs, REST frameworks, component libraries, UI design/token systems), experience with stack (Typescript/React, Python, Nx, PostgreSQL, Celery, AWS/GCP, Ubuntu, Apache, Redis, Git, Jira), implement UI and API monitoring tools, participate in development process (maybe that's responsibility). But we can keep. - Benefits: Benefits list. - Pay: salary range, bonus, long-term incentive, compensation determination. We also have "Fully remote work environment with home office set-up allowance" and other benefits like no preset vacation, parental leave, health wellness, 401k. Those go under Benefits. We need to ensure we don't repeat content. Let's craft HTML. We'll use

for each heading, then

for prose,

• for lists. We need to avoid repeating job title. Let's write. First, About the role:

  Renew Home is looking for a strong full stack Software Engineer to join our user Lifecycle & Engagement team and help build and support our consumer-facing platform. In this role, you will work with product, analytics, and the engineering team to develop new features that shape how customers can interact with our product.

  Responsibilities: list.
  • Design, develop and build frontend and backend features to support a wide variety of Renew Home customer experiences to enable energy saving automation
  • Serve as the technical owner of critical product experience flows
  • Work with cross-functional teams consisting of engineering, analytics, and product management
  • Work on many aspects of our stack: Typescript/React, Python,