Staff Frontend 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. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About Monstro: description of company. Could be "About the role"? Actually "About Monstro" is about company. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for description of role? But we have "About Monstro" which is about company. Might be better to put under "About the role"? However we should not invent heading if not matching content. The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It implies we can use those headings if appropriate. If we have content about the company, we could still use "About the role" but that might be inaccurate. Better to use "About the role" for role description (What You'll Do). The "About Monstro" could be considered "About the role"? Not exactly. But we could treat "About Monstro" as part of role description? Might be okay. Alternatively we could create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. Thus we need to map content: - About the role: maybe include description of Monstro and the work? Could combine "About Monstro" and "The work". But we need to preserve all substantive info. Could put under "About the role" a paragraph describing Monstro and the work. - Responsibilities: "What You'll Do" section includes many bullet points (actually paragraphs). We can turn each bullet into

under

. The content includes multiple paragraphs under headings like Frontend Technical Leadership & Architecture, Hands-On Product Development, etc. Those could be list items. - Requirements: "What We're Looking For" list of bullet points. Those are requirements. - Qualifications: maybe "Nice to Have" could be qualifications? Actually qualifications could be required qualifications. The "What We're Looking For" are required qualifications. Nice to Have could be "Qualifications" or "Skills"? The instruction: Use sections only when posting has real specific content. We have both required and nice-to-have. Could put required under "Requirements" and nice-to-have under "Qualifications" or "Skills". But we also have "Skills" section for skills. Could separate: Requirements = required experience; Qualifications = nice-to-have; Skills = technical skills (React, TypeScript, etc). However the required list already includes many skills. Might be better to treat "What We're Looking For" as Requirements (including skills). Then we could have a separate "Skills" section for specific technical proficiencies (React, TypeScript, CSS, etc). But that would duplicate. Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But we need to follow headings list. Could have Requirements (required) and Qualifications (nice-to-have). Skills maybe not needed if covered. Benefits: we have "Compensation and benefits: Competitive cash compensation and meaningful equity, plus 100% employer-paid medical, dental, and vision coverage, disability coverage, flexible PTO, paid parental leave, and catered meals." Also "Base Compensation Range (New York City): $249,000 - $298,000". That's pay. So we have Benefits and Pay. Schedule: "We are headquartered at The Spiral in Hudson Yards and work in the office four days a week". That's schedule. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Benefits, Pay, Schedule. We must not include empty sections. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract About the role: combine "About Monstro" paragraph(s) and "The work" paragraph(s). Let's copy them. About Monstro paragraph: "Monstro provides the AI-powered Financial Intelligence System for regulated financial institutions. It enables banks and wealth managers to deliver continuous, personalized, governed Financial Guidance to every client, not just the top tier, across their entire financial life: saving, borrowing, investing, planning, protecting, and preparing. Meaningful Financial Guidance has only ever been available to a small portion of people. We are changing that, through the institutions people already trust. Institutions already have the relationships, the data, and the context to understand each client; Monstro turns that understanding into guidance that helps each person understand, decide, and act. For clients, that means clearer decisions, proactive support when life changes, and a better view of their financial lives. For institutions, it means deeper relationships, more clients served consistently, and more of each client’s financial life managed in one place. What makes this possible is how the system is built. Governance is not an added feature; it is foundational. Every recommendation reflects the institution’s own views, policies, and permissions. Every output can be audited, traced, and reversed, and client data stays under the institution’s control. Generative AI is used to build and configure the system; at runtime, execution is deterministic, so every output can be explained and stood behind, not just trusted." The work paragraph: "The work We are building for a high-stakes industry where the work has real consequences. Guidance only matters if people can trust it and institutions can govern it. The challenge is to make Financial Guidance more personal and more available without making it less trusted: to build AI that institutions can audit, explain, and reverse, in a domain where being wrong carries real cost. That is what makes the problem hard, and the work meaningful. This is not a simple AI problem; it takes product judgment, technical depth, regulatory discipline, design quality, and a team that moves quickly without lowering the bar. Monstro is moving from vision to market: launching with financial institutions, growing the team, and building for the enterprise in one of the most regulated industries. You will be expected to think clearly, communicate directly, move with urgency, hold a high standard, and take responsibility for work that matters. We are an early team building something ambitious, and what you do here will shape both the product and the company." We can combine into a paragraph or multiple paragraphs. Use

for prose. Now Responsibilities: "What You'll Do" includes several subheadings with paragraphs. We need to turn each bullet into list items. However the content is not bullet list but paragraphs under headings. We could treat each subheading as a list item? But instruction: Use

• for any list of duties/requirements/benefits. The responsibilities are effectively a list of duties. We can create
  with each duty as
  • . We need to capture all duties. Let's extract duties: From "Frontend Technical Leadership & Architecture": - Serve as the technical authority for frontend engineering at Monstro, owning the evolution of our frontend architecture as the product and engineering organization scale. - Assess the systems and patterns we have today, identify architectural gaps and risks, and proactively define what needs to change rather than waiting for requirements to be handed to you. - Own architectural decisions across our React and TypeScript stack, including application structure, component architecture, state and data management, navigation, API integration, performance, build tooling, and developer experience. - Establish clear architectural patterns, standards, and guardrails that enable engineers across the team to contribute safely and consistently. - Lead architectural changes from idea through adoption: develop the technical strategy, write RFCs where appropriate, build proofs of concept, earn buy-in, and drive implementation across the engineering team. From "Hands-On Product Development": - Remain deeply hands-on in the code, building and owning meaningful product experiences across our React applications. - Take complex frontend problems from ambiguity to production, balancing speed, maintainability, performance, user experience, and long-term architectural quality. - Build polished, responsive, accessible experiences that meet the quality bar expected of software used by leading financial institutions. - Work closely with product and design to influence solutions rather than simply implement specifications, bringing strong technical and UX judgment into product decisions. From "Component Systems & Scalable UI": - Define and evolve our approach to reusable components and frontend systems, creating foundations that can support multiple products, workflows, and customer experiences. - Establish scalable patterns for component architecture, theming, configuration, and reuse, including experiences that may ultimately be embedded or adapted within our customers' digital environments. - Partner closely with design to ensure our implementation patterns support consistency, flexibility, accessibility, and a high-quality user experience as the product grows. From "Quality, Testing & Engineering Guardrails": - Own the frontend quality strategy across unit, integration, and end-to-end testing, determining what should be tested, where, and how. - Build quality into the development lifecycle through automated testing, CI/CD checks, static analysis, observability, and other engineering guardrails. - Identify weaknesses in our existing frontend development practices and proactively introduce systems that prevent regressions and architectural degradation as more engineers contribute. - Treat accessibility, security, performance, and reliability as foundational engineering concerns rather than downstream checks. From "AI-Native Engineering": - Help define how Monstro uses modern AI development tools across frontend engineering, using tools such as Claude Code, Codex, and other emerging systems to improve development velocity and quality. - Go beyond individual AI-assisted coding by establishing reusable workflows, context, standards, and guardrails that help the broader engineering team use these tools effectively. - Continuously evaluate emerging tools and development practices and proactively introduce approaches that materially improve how the team builds software without lowering the quality bar. From "Technical Influence & Mentorship": - Raise the frontend capabilities of the broader engineering organization through technical leadership, code reviews, documentation, pairing, tooling, and mentorship. - Be willing to challenge existing approaches, surface technical debt and architectural risk, and advocate for better solutions even when doing so requires changing established patterns. - Partner closely with backend, platform, product, and design teams to define clean system boundaries, effective API contracts, and scalable product architecture. - Create an engineering environment where strong frontend practices are easy for other engineers to understand, adopt, and maintain. Now Requirements: "What We're Looking For" list. Let's extract each bullet: - Significant professional frontend engineering experience, including demonstrated success operating at Staff, Principal, Lead, or equivalent technical scope. - Deep expertise in React and TypeScript and a track record of architecting and shipping complex production web applications. - Demonstrated experience serving as a frontend technical authority: defining architecture, establishing standards, and influencing how multiple engineers or teams build frontend software. - Hands-on experience with modern AI-assisted software development tools and a thoughtful perspective on how AI can improve engineering workflows while maintaining quality and maintainability. - Experience taking an evolving or inconsistent frontend codebase and introducing scalable architecture, patterns, tooling, and engineering practices. - A track record of driving technical changes through adoption—not just identifying the right architecture, but building consensus, implementing it, and helping other engineers successfully follow it. - Strong experience designing reusable component systems, design systems, or shared frontend infrastructure. - Deep understanding of frontend testing strategy across unit, integration, and end-to-end testing, with experience establishing automated quality guardrails within CI/CD. - Strong knowledge of modern CSS, responsive design, performance, and accessibility standards. - Experience working across frontend and backend boundaries, including API contracts, authentication, state/data management, and system integrations. - Strong product and UX judgment and the ability to collaborate closely with product and design while independently identifying technical and user-experience improvements. - A proactive, opinionated, and pragmatic technical leader who is comfortable challenging assumptions, introducing new approaches, and raising the engineering bar.