Senior Frontend Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should produce those headings only if we have content.
We need to avoid repeating job title as heading.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). So we need to strip out EEO statement, accommodation contact, etc. Also remove "Export Control Requirement"? That's substantive? It's a requirement about citizenship; maybe it's a requirement. Could be included under Requirements or Qualifications. But we need to decide.
We also need to not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state Benefits (list), Compensation (salary range), Location (remote-first with preference). So we can include Benefits, Pay, maybe Location under something else? There's no Schedule mentioned. So we should not create Schedule section.
We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also Skills? The posting includes technical requirements (must have, highly valuable). Could map Must Have to Requirements, Highly Valuable to Qualifications or Skills. We need to decide.
We need to preserve all substantive information. So we need to include details: mission, Reflow product description, responsibilities list, technical requirements (must have, highly valuable), what we offer (benefits list), compensation and location, export control requirement, BIG payoff (ownership statement), maybe also "We want to work with people that reflect the communities..." which is EEO statement - should be removed as boilerplate. Also accommodation contact - remove.
We need to avoid duplication.
Let's extract substantive content:
Company mission: "At Re:Build, our mission is to ensure the next generation of important products are made, at scale, in America. We are laying the foundation for a better future for our customers, employees, and communities by revitalizing America's manufacturing base and creating meaningful jobs across the country, including in historically deindustrialized regions. We operate an advanced, end-to-end manufacturing platform that partners with industrial companies and innovators to take products from first concept to full-scale production in critical verticals including aerospace and defense, electrification, medical, energy and environment, and robotics and automation. The way we operate is as important as the work we do. It's guided by The Re:Build Way, 16 principles that shape how we collaborate with each other, partner with our customers and vendors, and contribute to the communities where we operate. (link to The Re:Build Way principles)". This is company overview; could be part of About the role? Might be okay.
The Opportunity: description of Reflow and role.
Who We're Looking For: description of ideal candidate.
What You'll Do: responsibilities list.
Technical Requirements: Must Have and Highly Valuable.
What We Offer: list of benefits.
Compensation & Location: salary range, location preference, equity, etc.
Export Control Requirement: citizenship requirement.
The BIG payoff: ownership statement.
We need to map to headings.
Let's decide:
- About the role: Could combine company overview + The Opportunity description (role description). Might be okay.
- Responsibilities: the "What You'll Do" list.
- Requirements: Must Have technical requirements.
- Qualifications: Highly Valuable items.
- Skills: maybe we could combine Requirements and Qualifications? But we need to follow instruction: use headings as appropriate. Could have both Requirements and Qualifications.
- Benefits: the "What We Offer" list.
- Pay: compensation details (salary range, bonus, equity, etc.)
- Schedule: not present, so omit.
We also need to include Export Control Requirement somewhere; maybe under Requirements or Qualifications as a requirement. Could add a bullet under Requirements.
Also include "The BIG payoff" maybe under Benefits? Or could be its own section? Not in list of headings; but we could include under Benefits? It's about ownership and financial rewards. Could be part of Benefits or maybe under Pay? It's about equity ownership. Could be under Pay as part of compensation. We'll include under Pay.
Also location info could be under Pay? Or maybe under Benefits? Could be under Pay as location preference. Or we could create a separate section? Not in list. Could put under Pay as note.
We need to preserve all substantive info, so we need to include location preference and remote-first.
Let's structure:
About the role
At Re:Build, our mission is to ensure the next generation of important products are made, at scale, in America. ... (company overview). The Opportunity: If you've worked alongside hardware teams, you know the damage that results from a missed change request or critical context that was never relayed to the right person. Reflow exists to close that gap. We're building the first AI-powered platform purpose-built for hardware product development, one that listens across the tools teams already use, maintains a structured picture of every program, and proactively coordinates across disciplines when things inevitably change. This is a ground-floor opportunity for a hands-on frontend engineer to shape the user experience of a high-potential product with the support of a parent company leading innovation in engineering and manufacturing.
That seems okay.
Responsibilities
- Building production-grade React applications with TypeScript
- Developing and maintaining a shared component library
- Building rich interfaces for structured engineering data: requirements with traceability, phase/gate tracking, dependency graphs, task boards with discipline tags, and version-controlled project plans
- Building interfaces for AI agent interactions including streaming chat, proactive coordination alerts, and AI-generated status summaries and deliverables (proposals, SOWs, reports)
- Implementing portfolio-level dashboards for engineering leaders and executives showing cross-project cost, schedule, and risk
- Writing well-tested code with unit and end-to-end tests
- Collaborating with backend engineers on API integration and client SDK usage
- Contributing to frontend architecture decisions, code reviews, and engineering best practices
Requirements
- 5+ years building production web applications, with 3+ years focused on React
- Demonstrated proficiency using AI coding tools (Cursor, Copilot, Claude, etc.) to accelerate development
- Expert-level expertise with React, TypeScript, and modern JavaScript
- Strong experience with component-driven development, design systems, and tools like Storybook
- Proficiency with CSS frameworks (Tailwind CSS preferred) and responsive design
- Experience with modern build tools (Vite, esbuild, or similar)
- Understanding of API integration patterns (REST, OpenAPI, generated clients)
- Ability to balance rapid iteration with maintainable, well-tested code
- U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum (export control requirement)
Qualifications
- Have worked in early-stage 0 to 1 startup environments
- Familiarity with hardware development, engineering workflows, or project management processes
- Experience building UIs for AI/LLM-powered features (streaming responses, chat interfaces, structured AI output)
- Familiarity with headless component libraries (Base UI, Radix, Headless UI)
- Background in data visualization or dashboard-heavy applications
- Understanding of authentication/authorization patterns (OIDC, JWT)
- Experience with end-to-end testing frameworks (Playwright, Cypress)
- Background in B2B SaaS platforms, project management tools, or technical collaboration products
Benefits
- Full health/dental/vision
- Bonus program
- Generous 401K
- Paid time off
- Annual learning stipend
- Participation in Re:Build's LTIP equity program and opportunity for founder equity in potential spin-out
Pay
The base salary range for this position is $165,000 – $200,000 per year. This range represents the Company’s good faith estimate of the base compensation for this role at the time of posting. Actual compensation will be determined based on several factors, including but not limited to relevant experience, skills, qualifications, internal equity, and geographic location. In addition to base salary, this role may be eligible for annual incentive compensation and/or long-term incentives, subject to Company plans. The Company offers a comprehensive benefits package including medical, dental, vision, retirement, paid time off, and other benefits. Potential equity stake under independent spinout scenario. Location: Remote-first, with preference for candidates in Boston, Seattle, Los Angeles, or other cities with Re:Build offices.
We should not include Schedule.
We need to ensure we didn't include any boilerplate like EEO statement, accommodation contact, duplicated lines. We removed those.
Check for any leftover boilerplate: The "BIG payoff" paragraph about ownership and sharing financial rewards - we included that in Benefits? Actually we included equity opportunity in Benefits list. The BIG payoff also includes: "We are a company who is going to make a difference in the industries and the communities in which we choose to operate. Every employee of Re:Build will share ownership in the company and will share in the financial rewards of the success we achieve together, at all levels of the company! We want to work with people that reflect the communities in which we operate". The latter sentence is EEO-ish but also about community reflection. Might be considered boilerplate? It's not a standard EEO but still about diversity. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. That sentence about wanting to work with people that reflect the communities could be considered EEO-related. Safer to remove it. We already omitted that sentence. We kept the ownership statement part in Benefits? Actually we put equity opportunity in Benefits list. The ownership statement about sharing ownership and financial rewards is covered by equity mention. We could keep a short sentence about ownership in Benefits or Pay. But we already have equity in Benefits list. The BIG payoff also includes "Every employee of Re:Build will share ownership in the company and will share in the financial rewards of the success we achieve together, at all levels of the company!" That's essentially same as equity. We can keep that as part of Benefits description maybe. But we already have equity bullet.
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). So we need to strip out EEO statement, accommodation contact, etc. Also remove "Export Control Requirement"? That's substantive? It's a requirement about citizenship; maybe it's a requirement. Could be included under Requirements or Qualifications. But we need to decide. We also need to not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state Benefits (list), Compensation (salary range), Location (remote-first with preference). So we can include Benefits, Pay, maybe Location under something else? There's no Schedule mentioned. So we should not create Schedule section. We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also Skills? The posting includes technical requirements (must have, highly valuable). Could map Must Have to Requirements, Highly Valuable to Qualifications or Skills. We need to decide. We need to preserve all substantive information. So we need to include details: mission, Reflow product description, responsibilities list, technical requirements (must have, highly valuable), what we offer (benefits list), compensation and location, export control requirement, BIG payoff (ownership statement), maybe also "We want to work with people that reflect the communities..." which is EEO statement - should be removed as boilerplate. Also accommodation contact - remove. We need to avoid duplication. Let's extract substantive content: Company mission: "At Re:Build, our mission is to ensure the next generation of important products are made, at scale, in America. We are laying the foundation for a better future for our customers, employees, and communities by revitalizing America's manufacturing base and creating meaningful jobs across the country, including in historically deindustrialized regions. We operate an advanced, end-to-end manufacturing platform that partners with industrial companies and innovators to take products from first concept to full-scale production in critical verticals including aerospace and defense, electrification, medical, energy and environment, and robotics and automation. The way we operate is as important as the work we do. It's guided by The Re:Build Way, 16 principles that shape how we collaborate with each other, partner with our customers and vendors, and contribute to the communities where we operate. (link to The Re:Build Way principles)". This is company overview; could be part of About the role? Might be okay. The Opportunity: description of Reflow and role. Who We're Looking For: description of ideal candidate. What You'll Do: responsibilities list. Technical Requirements: Must Have and Highly Valuable. What We Offer: list of benefits. Compensation & Location: salary range, location preference, equity, etc. Export Control Requirement: citizenship requirement. The BIG payoff: ownership statement. We need to map to headings. Let's decide: - About the role: Could combine company overview + The Opportunity description (role description). Might be okay. - Responsibilities: the "What You'll Do" list. - Requirements: Must Have technical requirements. - Qualifications: Highly Valuable items. - Skills: maybe we could combine Requirements and Qualifications? But we need to follow instruction: use headings as appropriate. Could have both Requirements and Qualifications. - Benefits: the "What We Offer" list. - Pay: compensation details (salary range, bonus, equity, etc.) - Schedule: not present, so omit. We also need to include Export Control Requirement somewhere; maybe under Requirements or Qualifications as a requirement. Could add a bullet under Requirements. Also include "The BIG payoff" maybe under Benefits? Or could be its own section? Not in list of headings; but we could include under Benefits? It's about ownership and financial rewards. Could be part of Benefits or maybe under Pay? It's about equity ownership. Could be under Pay as part of compensation. We'll include under Pay. Also location info could be under Pay? Or maybe under Benefits? Could be under Pay as location preference. Or we could create a separate section? Not in list. Could put under Pay as note. We need to preserve all substantive info, so we need to include location preference and remote-first. Let's structure:
About the role
At Re:Build, our mission is to ensure the next generation of important products are made, at scale, in America. ... (company overview). The Opportunity: If you've worked alongside hardware teams, you know the damage that results from a missed change request or critical context that was never relayed to the right person. Reflow exists to close that gap. We're building the first AI-powered platform purpose-built for hardware product development, one that listens across the tools teams already use, maintains a structured picture of every program, and proactively coordinates across disciplines when things inevitably change. This is a ground-floor opportunity for a hands-on frontend engineer to shape the user experience of a high-potential product with the support of a parent company leading innovation in engineering and manufacturing.
That seems okay.Responsibilities
- Building production-grade React applications with TypeScript
- Developing and maintaining a shared component library
- Building rich interfaces for structured engineering data: requirements with traceability, phase/gate tracking, dependency graphs, task boards with discipline tags, and version-controlled project plans
- Building interfaces for AI agent interactions including streaming chat, proactive coordination alerts, and AI-generated status summaries and deliverables (proposals, SOWs, reports)
- Implementing portfolio-level dashboards for engineering leaders and executives showing cross-project cost, schedule, and risk
- Writing well-tested code with unit and end-to-end tests
- Collaborating with backend engineers on API integration and client SDK usage
- Contributing to frontend architecture decisions, code reviews, and engineering best practices
Requirements
- 5+ years building production web applications, with 3+ years focused on React
- Demonstrated proficiency using AI coding tools (Cursor, Copilot, Claude, etc.) to accelerate development
- Expert-level expertise with React, TypeScript, and modern JavaScript
- Strong experience with component-driven development, design systems, and tools like Storybook
- Proficiency with CSS frameworks (Tailwind CSS preferred) and responsive design
- Experience with modern build tools (Vite, esbuild, or similar)
- Understanding of API integration patterns (REST, OpenAPI, generated clients)
- Ability to balance rapid iteration with maintainable, well-tested code
- U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum (export control requirement)
Qualifications
- Have worked in early-stage 0 to 1 startup environments
- Familiarity with hardware development, engineering workflows, or project management processes
- Experience building UIs for AI/LLM-powered features (streaming responses, chat interfaces, structured AI output)
- Familiarity with headless component libraries (Base UI, Radix, Headless UI)
- Background in data visualization or dashboard-heavy applications
- Understanding of authentication/authorization patterns (OIDC, JWT)
- Experience with end-to-end testing frameworks (Playwright, Cypress)
- Background in B2B SaaS platforms, project management tools, or technical collaboration products
Benefits
- Full health/dental/vision
- Bonus program
- Generous 401K
- Paid time off
- Annual learning stipend
- Participation in Re:Build's LTIP equity program and opportunity for founder equity in potential spin-out
Pay
The base salary range for this position is $165,000 – $200,000 per year. This range represents the Company’s good faith estimate of the base compensation for this role at the time of posting. Actual compensation will be determined based on several factors, including but not limited to relevant experience, skills, qualifications, internal equity, and geographic location. In addition to base salary, this role may be eligible for annual incentive compensation and/or long-term incentives, subject to Company plans. The Company offers a comprehensive benefits package including medical, dental, vision, retirement, paid time off, and other benefits. Potential equity stake under independent spinout scenario. Location: Remote-first, with preference for candidates in Boston, Seattle, Los Angeles, or other cities with Re:Build offices.
We should not include Schedule. We need to ensure we didn't include any boilerplate like EEO statement, accommodation contact, duplicated lines. We removed those. Check for any leftover boilerplate: The "BIG payoff" paragraph about ownership and sharing financial rewards - we included that in Benefits? Actually we included equity opportunity in Benefits list. The BIG payoff also includes: "We are a company who is going to make a difference in the industries and the communities in which we choose to operate. Every employee of Re:Build will share ownership in the company and will share in the financial rewards of the success we achieve together, at all levels of the company! We want to work with people that reflect the communities in which we operate". The latter sentence is EEO-ish but also about community reflection. Might be considered boilerplate? It's not a standard EEO but still about diversity. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. That sentence about wanting to work with people that reflect the communities could be considered EEO-related. Safer to remove it. We already omitted that sentence. We kept the ownership statement part in Benefits? Actually we put equity opportunity in Benefits list. The ownership statement about sharing ownership and financial rewards is covered by equity mention. We could keep a short sentence about ownership in Benefits or Pay. But we already have equity in Benefits list. The BIG payoff also includes "Every employee of Re:Build will share ownership in the company and will share in the financial rewards of the success we achieve together, at all levels of the company!" That's essentially same as equity. We can keep that as part of Benefits description maybe. But we already have equity bullet.