Staff Frontend Engineer
Monstro · New York, NY · 3 wk ago
HybridEngineering$249k–$298k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "About Monstro", "The work", "What You'll Do", "What We're Looking For", "Nice to Have", "Why Monstro?" etc. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. The headings we can use: "About the role" (maybe corresponds to description of role), "Responsibilities" (What You'll Do), "Requirements" (What We're Looking For), "Qualifications" maybe same as Requirements? Could combine. "Skills" maybe from Nice to Have? "Benefits", "Pay", "Schedule". We need to preserve all substantive info, not invent. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to decide which sections to include based on content.
We have:
- About Monstro (company description) could be "About the role"? Actually "About the role" is about the job, not company. But we could treat "About Monstro" as "About the role"? Might be okay. The instruction: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. The headings we can use: "About the role" (maybe corresponds to description of role), "Responsibilities" (What You'll Do), "Requirements" (What We're Looking For), "Qualifications" maybe same as Requirements? Could combine. "Skills" maybe from Nice to Have? "Benefits", "Pay", "Schedule". We need to preserve all substantive info, not invent. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to decide which sections to include based on content.
We have:
- About Monstro (company description) could be "About the role"? Actually "About the role" is about the job, not company. But we could treat "About Monstro" as "About the role"? Might be okay. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. We have content for About the role? Could be the description of the role (the work). We have "The work" describing the challenge. That could be "About the role". We'll put that under About the role
.
Responsibilities: "What You'll Do" includes bullet points (multiple paragraphs). We'll convert each bullet to - .
Requirements: "What We're Looking For" list of bullet points. We'll put under
Requirements
.
Qualifications: maybe same as Requirements? Could skip if duplicate. But we could also put "Nice to Have" under Skills
or Qualifications
. The instruction: prefer few substantive sections over many thin ones. So we could combine Nice to Have into Skills section.
Benefits: "Why Monstro?" includes bullet points: Impact, Ownership, Experienced team, Principles-driven culture, In person, Compensation and benefits. That includes compensation details. We could split: Benefits section for non-compensation benefits (medical, dental, vision, disability, flexible PTO, paid parental leave, catered meals). Pay section for base compensation range. Schedule maybe not mentioned (in person 4 days a week). That's schedule info: "We are headquartered at The Spiral in Hudson Yards and work in the office four days a week". That's schedule. So we can include Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Skills (Nice to Have), Benefits, Pay, Schedule.
We must not include headings with filler like "commensurate with experience". We have specific content.
Now we need to preserve all substantive info, not invent or summarize away detail. So we need to include all bullet points from each section.
Let's extract content.
About Monstro description: paragraphs about Monstro providing AI-powered Financial Intelligence System etc. We'll keep as prose under About the role? Actually About the role should be about the job, but we can put company description there. Might be okay.
The work: paragraphs about challenge.
What You'll Do: multiple bullet-like paragraphs each starting with a bold heading? Actually they are headings: "Frontend Technical Leadership & Architecture", "Hands-On Product Development", "Component Systems & Scalable UI", "Quality, Testing & Engineering Guardrails", "AI-Native Engineering", "Technical Influence & Mentorship". Each followed by description paragraphs. We need to turn each into list items? The instruction: Use - for any list of duties/requirements/benefits. So we can treat each of these as a duty. So
- Frontend Technical Leadership & Architecture: ...
etc. Inside each li we can include the description as maybe? But we can just put text inside li. Simpler: each li contains the heading and description.
What We're Looking For: list of bullet points each starting with bold? Actually they are sentences. We'll make each a
- .
Nice to Have: list of bullet points.
Why Monstro?: bullet points: Impact, Ownership, Experienced team, Principles-driven culture, In person, in New York: ... Compensation and benefits: ... We'll separate.
Benefits: from Why Monstro: "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." Actually that includes compensation. We'll separate compensation into Pay. Benefits: medical, dental, vision, disability, flexible PTO, paid parental leave, catered meals. Also maybe "meaningful equity" is compensation? We'll treat equity as part of Pay? Could be part of compensation. We'll put equity in Pay.
Pay: Base Compensation Range (New York City): $249,000 - $298,000. Also mention competitive cash compensation and meaningful equity. We'll include that.
Schedule: "We are headquartered at The Spiral in Hudson Yards and work in the office four days a week". Also maybe mention in-person.
Now we need to ensure we don't repeat job title. No headings for job title.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
... (Monstro description + The work?) Actually we have two paragraphs: About Monstro and The work. Could combine into one
or two
. We'll put both as
elements.
Then
Responsibilities
- Frontend Technical Leadership & Architecture: 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Requirements
- 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.
- Clear communicator and mentor who can explain complex technical decisions, earn buy-in, and make the engineers around them better.
- Comfortable operating in an early-stage environment with ambiguity, high ownership, and significant influence over both the product and technical direction.
Skills
- Full-stack experience, including backend/API development experience (our backend is in Python)
- Experience building configurable, themeable, white-label, or embeddable UI/component systems
- Experience establishing frontend architecture or engineering practices in an early-stage company or rapidly evolving product environment
- Background in fintech, financial services, or another regulated industry
- Experience introducing AI-native development practices, tooling, or guardrails across an engineering team
Benefits
- 100% employer-paid medical, dental, and vision coverage
- Disability coverage
- Flexible PTO
- Paid parental leave
- Catered meals
Pay
About the role
. Responsibilities: "What You'll Do" includes bullet points (multiple paragraphs). We'll convert each bullet to- .
Requirements: "What We're Looking For" list of bullet points. We'll put under
Requirements
. Qualifications: maybe same as Requirements? Could skip if duplicate. But we could also put "Nice to Have" underSkills
orQualifications
. The instruction: prefer few substantive sections over many thin ones. So we could combine Nice to Have into Skills section. Benefits: "Why Monstro?" includes bullet points: Impact, Ownership, Experienced team, Principles-driven culture, In person, Compensation and benefits. That includes compensation details. We could split: Benefits section for non-compensation benefits (medical, dental, vision, disability, flexible PTO, paid parental leave, catered meals). Pay section for base compensation range. Schedule maybe not mentioned (in person 4 days a week). That's schedule info: "We are headquartered at The Spiral in Hudson Yards and work in the office four days a week". That's schedule. So we can include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Skills (Nice to Have), Benefits, Pay, Schedule. We must not include headings with filler like "commensurate with experience". We have specific content. Now we need to preserve all substantive info, not invent or summarize away detail. So we need to include all bullet points from each section. Let's extract content. About Monstro description: paragraphs about Monstro providing AI-powered Financial Intelligence System etc. We'll keep as prose under About the role? Actually About the role should be about the job, but we can put company description there. Might be okay. The work: paragraphs about challenge. What You'll Do: multiple bullet-like paragraphs each starting with a bold heading? Actually they are headings: "Frontend Technical Leadership & Architecture", "Hands-On Product Development", "Component Systems & Scalable UI", "Quality, Testing & Engineering Guardrails", "AI-Native Engineering", "Technical Influence & Mentorship". Each followed by description paragraphs. We need to turn each into list items? The instruction: Use- for any list of duties/requirements/benefits. So we can treat each of these as a duty. So
- Frontend Technical Leadership & Architecture: ... etc. Inside each li we can include the description as
- .
Nice to Have: list of bullet points.
Why Monstro?: bullet points: Impact, Ownership, Experienced team, Principles-driven culture, In person, in New York: ... Compensation and benefits: ... We'll separate.
Benefits: from Why Monstro: "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." Actually that includes compensation. We'll separate compensation into Pay. Benefits: medical, dental, vision, disability, flexible PTO, paid parental leave, catered meals. Also maybe "meaningful equity" is compensation? We'll treat equity as part of Pay? Could be part of compensation. We'll put equity in Pay.
Pay: Base Compensation Range (New York City): $249,000 - $298,000. Also mention competitive cash compensation and meaningful equity. We'll include that.
Schedule: "We are headquartered at The Spiral in Hudson Yards and work in the office four days a week". Also maybe mention in-person.
Now we need to ensure we don't repeat job title. No headings for job title.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
... (Monstro description + The work?) Actually we have two paragraphs: About Monstro and The work. Could combine into one
or two
. We'll put both as
elements. Then
Responsibilities
- Frontend Technical Leadership & Architecture: 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Requirements
- 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.
- Clear communicator and mentor who can explain complex technical decisions, earn buy-in, and make the engineers around them better.
- Comfortable operating in an early-stage environment with ambiguity, high ownership, and significant influence over both the product and technical direction.
Skills
- Full-stack experience, including backend/API development experience (our backend is in Python)
- Experience building configurable, themeable, white-label, or embeddable UI/component systems
- Experience establishing frontend architecture or engineering practices in an early-stage company or rapidly evolving product environment
- Background in fintech, financial services, or another regulated industry
- Experience introducing AI-native development practices, tooling, or guardrails across an engineering team
Benefits
- 100% employer-paid medical, dental, and vision coverage
- Disability coverage
- Flexible PTO
- Paid parental leave
- Catered meals
Pay
maybe? But we can just put text inside li. Simpler: each li contains the heading and description. What We're Looking For: list of bullet points each starting with bold? Actually they are sentences. We'll make each a
- for any list of duties/requirements/benefits. So we can treat each of these as a duty. So