Staff Full Stack Software Engineer, Tapestry

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

for each heading. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content sections: - About Tapestry (intro) maybe not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting includes "About Tapestry" (company description). Not one of the listed headings; maybe we can include as part of "About the role"? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid other headings, but they gave examples. Likely we should only use those headings if content exists. The "About Tapestry" could be considered "About the role"? Actually "About the role" is separate. The posting has "About The Role" heading. So we can use that. Thus sections: - About the role: content from "About The Role" paragraph(s). That includes description of role, impact, etc. - Responsibilities: from "How You Will Make 10X Impact" bullet list (though it's prose sentences). We'll turn each sentence into

. - Requirements: from "What You Should Have" bullet list. - Qualifications: maybe from "It’d Be Great If You Also Had These" (nice-to-have). Could be Qualifications or Skills. We'll treat as "Qualifications" (preferred). Or "Skills". We'll decide. - Skills: maybe from mastery of TypeScript etc. But that's already in Requirements. Could split. - Benefits: from "What We Offer" bullet list. - Pay: from salary range sentence. - Schedule: maybe not present; there is mention of flexible hybrid work model but not schedule specifics. Could include schedule under Benefits? The instruction: only include section if posting has real specific content. There's no explicit schedule (like full-time, hours). It says full-time position. Could include schedule as "Full-time". Might be considered schedule content. But they said never emit heading followed by filler/placeholder text like "not specified". "Full-time" is specific. Could include Schedule section with "Full-time". However they said prefer a few substantive sections over many thin ones. Might be okay to include Schedule. But we need to decide. Let's extract content. About Tapestry intro: Could be part of About the role? Actually About the role section should contain description of role. The intro about Tapestry is company overview; maybe we can include as a paragraph before About the role? But instruction: use headings for sections; we can have a

before first heading? Probably okay. But they said output ONLY the HTML fragment; we can include a

for the company description if we want. Not required to wrap in heading. We'll include it as a

before the first heading. Now parse sections. About The Role: Text: "As a Staff Frontend Engineer, you will define the architectural vision for how the world visualizes and interacts with the future of the electric grid. You will lead the technical roadmap for our web platforms, bridging the gap between complex power-system AI and intuitive, high-performance user experiences that enable global energy leaders to make trillion-dollar decisions." Then "How You Will Make 10X Impact" list: - Lead the design and evolution of a highly performant, enterprise grade frontend architecture capable of visualizing massive, real-time geospatial and time-series data sets. - Establish engineering excellence across the organization by defining best practices for state management, testing, and component-driven development. - Define the next generation of Human-AI Interaction for the energy sector. Architect agentic workflows and ML-powered interfaces that move the platform from passive visualization to proactive decision support, allowing users to navigate high-stakes complexity through predictive automation and natural language reasoning. - Partner with AI Research and Power Systems teams to translate complex algorithmic outputs into actionable, streamlined, AI-assisted experiences and radical simplifications for our users. - Influence the multi-year product roadmap, identifying technical risks and opportunities. - Optimize the "Critical Rendering Path" for high-stakes environments, ensuring our tools remain responsive while handling millions of data points via WebGL or Canvas. - Raise the bar for the entire engineering org through deep technical mentorship, code reviews, and fostering a culture of rigorous craftsmanship. We'll make each bullet as

. Now Requirements: "What You Should Have" - 10+ years of experience in frontend or fullstack engineering, with a history of leading the technical vision for complex, large-scale platforms. - Proven experience building enterprise applications that leverage Large Language Models (LLMs), agentic frameworks, or predictive ML models. You understand the nuances of non-deterministic UIs, including handling streaming responses, state management for long-running agentic tasks, and building robust feedback loops. - A deep understanding of next-generation interaction patterns. You have experience moving beyond traditional "point-and-click" dashboards toward intent-based interfaces and generative user interfaces that adapt to user goals in real-time. - Mastery of TypeScript and modern frameworks (React/Angular), paired with a solid grasp of how to interface with shared services and orchestration layers. - The ability to design for the "Human-in-the-loop." You can architect systems where AI suggestions are seamlessly integrated with human expertise, ensuring clarity, trust, and safety in high-stakes energy planning. - A track record of taking "impossible" levels of complexity and distilling them into intuitive workflows that feel effortless to the end user. Now nice-to-have: "It’d Be Great If You Also Had These" - Experience with power systems, GIS (Geographic Information Systems), or climate-tech applications. - Familiarity with Kotlin, Java, Python or Go, and the ability to contribute to the backend services that power your frontends. - Experience working in high-growth or "zero-to-one" environments. We could put these under "Qualifications" or "Skills". Since they are additional qualifications, maybe "Qualifications". We'll decide to put them under "Qualifications". The "Skills" could be the mastery of TypeScript etc but that's already in Requirements. Could split but we can keep Requirements as hard requirements, Qualifications as nice-to-have. Benefits: "What We Offer" - A culture that supports growth, ownership, and meaningful impact, along with: - Competitive salary and equity - Medical, dental, and vision coverage - Generous PTO and flexible hybrid work model - 401(k) with employer contribution - Professional development - The ability to work on important real-world problems within an Alphabet-backed environment We need to capture as list items. The first bullet is a culture statement; we can include as

A culture that supports growth, ownership, and meaningful impact, along with:

then sublist? But we can just flatten. Simplify: each benefit as

. Pay: "The US base salary range for this full-time position is $207,000 - $300,000 + bonus + equity + benefits. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Your recruiter can share more about the specific salary range for your location during the hiring process. Please note that the compensation details listed in US role postings reflect the base salary only, and do not include bonus, equity, or benefits." We'll put that in

under Pay heading. Schedule: The posting mentions "full-time position". Also "flexible hybrid work model". Could include schedule as "Full-time, flexible hybrid". We'll create Schedule section with

Full-time position with flexible hybrid work model.

Now we need to ensure we don't include boilerplate like EEO, legal, etc. Remove those. Now produce HTML fragment: Start with a

for company description: "Tapestry is a group within Google working to build the AI-powered electric grid. We are tackling one of the world’s most important infrastructure challenges: helping the energy system become more visible, understandable, reliable, affordable, abundant, and clean. Originally born at X, Alphabet’s moonshot factory, Tapestry brings together experts in energy, AI, software engineering, and products to build tools that help the electricity ecosystem plan smarter, move faster, and operate more efficiently. This is a global effort. Tapestry supports partners across the U.S., U.K., Chile, New Zealand, Australia, and Brazil as they work toward a cleaner, more resilient energy future. Joining Tapestry means doing high-impact work with a multidisciplinary team tackling a problem that matters at global scale." Then headings. We'll wrap each section in appropriate tags. Structure:

About Tapestry...

About the role

As a Staff Frontend Engineer, you will define the architectural vision for how the world visualizes and interacts with the future of the electric grid. You will lead the technical roadmap for our web platforms, bridging the gap between complex power-system AI and intuitive, high-performance user experiences that enable global energy leaders to make trillion-dollar decisions.

Responsibilities

• Lead the design and evolution of a highly performant, enterprise grade frontend architecture capable of visualizing massive, real-time geospatial and time-series data sets.
• Establish engineering excellence across the organization by defining best practices for state management, testing, and component-driven development.
• Define the next generation of Human-AI Interaction for the energy sector. Architect agentic workflows and ML-powered interfaces that move the platform from passive visualization to proactive decision support, allowing users to navigate high-stakes complexity through predictive automation and natural language reasoning.
• Partner with AI Research and Power Systems teams to translate complex algorithmic outputs into actionable, streamlined, AI-assisted experiences and radical simplifications for our users.
• Influence the multi-year product roadmap, identifying technical risks and opportunities.
• Optimize the "Critical Rendering Path" for high-stakes environments, ensuring our tools remain responsive while handling millions of data points via WebGL or Canvas.
• Raise the bar for the entire engineering org through deep technical mentorship, code reviews, and fostering a culture of rigorous craftsmanship.

Requirements

• 10+ years of experience in frontend or fullstack engineering, with a history of leading the technical vision for complex, large-scale platforms.
• Proven experience building enterprise applications that leverage Large Language Models (LLMs), agentic frameworks, or predictive ML models. You understand the nuances of non-deterministic UIs, including handling streaming responses, state management for long-running agentic tasks, and building robust feedback loops.
• A deep understanding of next-generation interaction patterns. You have experience moving beyond traditional "point-and-click" dashboards toward intent-based interfaces and generative user interfaces that adapt to user goals in real-time.
• Mastery of TypeScript and modern frameworks (React/Angular), paired with a solid grasp of how to interface with shared services and orchestration layers.
• The ability to design for the "Human-in-the-loop." You can architect systems where AI suggestions are seamlessly integrated with human expertise, ensuring clarity, trust, and safety in high-stakes energy planning.
• A track record of taking "impossible" levels of complexity and distilling them into intuitive workflows that feel effortless to the end user.

Qualifications

• Experience with power systems, GIS (Geographic Information