Senior Software Engineer, Frontend

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. Must not repeat job title. No metadata like Job ID. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Sections present: - About Base (company description) - not a required heading; maybe we can include as a paragraph before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Probably we should include a brief intro paragraph about Base before sections? The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings like "About Base". But they gave examples of section headings; we could include "About Base" as a

maybe. Safer to include as a

before sections. We need sections: - About the role: we have "About The Role" paragraph. So we can put that as

About the role

then

with content. - Responsibilities: "What You'll Do" list. So

Responsibilities

then

• items. - Requirements/Qualifications/Skills: The posting has "What You'll Bring" which includes experience, expertise, etc. Could split into Requirements, Qualifications, Skills. But we need to avoid thin sections. Perhaps combine into one section "Requirements" with all. Or we could have "Qualifications" and "Skills". The instruction: Prefer a few substantive sections over many thin ones. So maybe one section "Requirements" covering all. But they also list "Skills" as possible heading. We could put "What You'll Bring" under "Requirements". That seems fine. - Benefits, Pay, Schedule: Not mentioned explicitly. There's no mention of benefits, pay, schedule. So we should NOT include those sections. Thus we will have sections: About the role, Responsibilities, Requirements (or Qualifications). Possibly also "About the team" but not required heading. Could include as a

  after sections? The instruction: "Prefer a few substantive sections over many thin ones." Including "About the team" as a section might be thin but it's substantive. However they didn't list "About the team" as example heading; but we could still include as a

  not heading. Safer to include as a

  after sections, not as heading. Thus output:

  About Base ...

  About the role

  ... (the About The Role paragraph)

  Responsibilities

  • Lead frontend development of the customer experience across Base web and mobile applications.
  ... etc each bullet from "What You'll Do".

  Requirements

  • 7+ years of experience building production frontend or full-stack software, with deep expertise in TypeScript and modern web frameworks such as React or Next.js.
  • Strong experience designing frontend architecture for complex web applications, including systems used by other engineers or teams, along with a track record of owning products or platforms from concept through launch and iteration - including at least one system you architected from scratch.
  • Comfort working across the stack and collaborating closely with backend engineers on APIs and data models.
  • Strong product judgment and the ability to translate complex systems into simple user experiences.
  • Experience using product analytics, experimentation, and data to guide decisions.
  • Real technical depth - you've gone deep on hard frontend problems (performance, state management, cross-platform architecture, design systems, etc.).
  • Experience mentoring engineers and influencing technical direction beyond your own team.
  • First principles thinking, grit, and a bias toward shipping.
  We could also include "About the team" as a

  after sections. Check for any duplicated lines: The posting includes "About Base Base is America’s next-generation power company..." We'll include that as a paragraph. We must not include boilerplate like "Please note: Base is a startup..." That's actually substantive? It's about role flexibility. Might be considered part of responsibilities? It's a note about role may expand. Could be included in About the role paragraph? It's after "About The Team". Actually after "About The Team" there is a note: "Please note: Base is a startup..." That's a note about the role. Could be included in About the role or Responsibilities? It's more about the role nature. Might be okay to include in About the role paragraph as a sentence. But we already have About the role paragraph from earlier; we could append that note. But the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The note about startup is not boilerplate; it's substantive about role flexibility. So we keep. Also "Our Values" section: list of values. That's substantive but not a heading we have. Could be included as a

  after sections maybe as "Our Values". But we don't have a heading for values; we could include as a

  but it's a list. Could make a

  under a heading "Values"? Not in allowed headings but we could still use

  Values? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those examples. Safer to not add extra headings; we could embed values in a

  paragraph. But we need to preserve ALL substantive information. If we omit values, we lose info. So we should include them somewhere. Could add a

  Values

  but that's not in the list; risk of violating instruction? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. So we can use other headings as long as we use

  . Probably okay. But to be safe, we could include values as a

  with a brief sentence summarizing? But that would lose the list detail. Better to include as a

  under a heading "Values". I'll do that. Similarly "About The Team" is substantive; we can make a

  About the team

  . Thus final sections: About Base (maybe as

  ), About the role, Responsibilities, Requirements, About the team, Values. Also maybe "What You'll Bring" we already put in Requirements. We must not include Pay/Benefits/Schedule. Now craft HTML. Let's extract exact text. About Base paragraph: "About Base Base is America’s next-generation power company. We’re rebuilding the foundation of modern civilization–electricity–by deploying a vast network of distributed batteries that is transforming today’s fragile, centralized grid into a resilient and abundant system. We are engineers, operators, and creatives solving some of the most complex, interdisciplinary challenges of our time." Note duplication: "About Base Base". We'll just write "Base is America’s next-generation power company..." We'll keep the content. About The Role paragraph: "We're looking for a senior or staff-level frontend engineer to lead development of the customer experience at Base. Our apps help members understand their energy usage, manage outages, and track the performance of the battery powering their home. You will set the architecture and technical direction of the interfaces that connect real-world energy systems with a clear, simple digital experience - and you'll be the technical anchor others build on. You'll join a small, high-impact team responsible for the digital front door of Base. In this role, you will lead development of major product surfaces across web and mobile, set frontend architecture and technical direction across the org, partner closely with product and design to shape the roadmap, and ensure we ship fast, reliable software. This role requires deep frontend expertise, technical leadership, and the ability to translate complex systems into simple experiences that millions of households can rely on." Responsibilities bullets from "What You'll Do": - Lead frontend development of the customer experience across Base web and mobile applications. - Set frontend architecture and technical strategy across multiple product surfaces, not just your own, and define the patterns, tooling, and standards that let the whole org build faster. - Own major product surfaces end-to-end, from initial concept through production and iteration, including systems you architect from scratch. - Work closely with backend engineers to design APIs and data models that support product features. - Translate complex energy systems into clear, intuitive user experiences. - Partner with product and design to shape the roadmap and deliver high-impact features. - Establish frontend engineering standards and improve developer experience across the stack, including build tooling, testing, and component architecture. - Mentor engineers and raise the bar for frontend craft across the team. - Act as a technical lead on cross-team initiatives, weighing in on frontend architecture decisions beyond your immediate team. - Use analytics and experimentation to improve the member experience over time. Requirements from "What You'll Bring": - 7+ years of experience building production frontend or full-stack software, with deep expertise in TypeScript and modern web frameworks such as React or Next.js. - Strong experience designing frontend architecture for complex web applications, including systems used by other engineers or teams, along with a track record of owning products or platforms from concept through launch and iteration - including at least one system you architected from scratch. - Comfort working across the stack and collaborating closely with backend engineers on APIs and data models. - Strong product judgment and the ability to translate complex systems into simple user experiences. - Experience using product analytics, experimentation, and data to guide decisions. - Real technical depth - you've gone deep on hard frontend problems (performance, state management, cross-platform architecture, design systems, etc.). - Experience mentoring engineers and influencing technical direction beyond your own team. - First principles thinking, grit, and a bias toward shipping. About The Team paragraph: "America's power grid is failing - electricity costs have risen even as generation gets cheaper, and blackouts are becoming more common. We're building the software that fixes it. Our team owns the entire stack: firmware that controls batteries in thousands of homes, trading algorithms that buy and sell power in real-time markets, distributed commanding systems that orchestrate a growing fleet as a single grid asset, factory software for our Austin manufacturing line, and the product experience that makes it all invisible to homeowners. If you want to write code that physically moves electrons, ships hardware, and reshapes critical infrastructure, this is the job." Note about startup: "Please note: Base is a startup, which means priorities shift and evolve quickly. Your role may expand or change based on the needs of the business at any given time, so the responsibilities listed may not be exhaustive." Could add to About the role paragraph or as its own note. I'll add as a sentence at end of About the role paragraph. Our Values list: - First Principles Thinking: Question assumptions. Principles > rules. - Operate at Base Pace: Focus on what matters, act quickly, and learn by doing. - Give & Get Feedback: Be direct, be humble, and maintain a growth mindset. - Everyone’s an Owner: Follow through on commitments and own results. - Strong Opinions, Loosely Held: Drive clarity and make calls with imperfect information. - Committed to the Mission: Rebuilding the grid is a big challenge. We work hard because we care deeply about the impact we’re creating. We work in-person. It’s not a 9-to-5. We are all-in. - Fun & Optimism Coexist with Grit: Collaboration and celebration coincide with the intensity of building real things. Do the best work of your life at Base. We'll put as <