Senior Software Engineer, Frontend

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. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - Intro: "Paperless Post is looking for a Senior Frontend Engineer to help craft the rich, polished experiences that millions of people rely on to celebrate the moments that matter. You'll drive frontend architecture decisions, and partner closely with product and design as part of a deeply collaborative team. We're looking for someone who cares about the craft — and equally about the people on the other side of the screen." This could be About the role. - "A little bit about us" paragraph: description of team, collaborative, etc. Could be About the role or maybe separate "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put company description under About the role or maybe under Qualifications? Probably About the role includes overview. - "What you bring to the table" bullet list: 6+ years experience, expert-level fluency in orchestrating agentic AI workflows, collaborative mindset, passion, strong critical thinking, ability to mentor. That's Requirements/Qualifications/Skills. - "Tech stack:" list: Expertise in TypeScript & React and proficiency in GraphQL. Familiarity with Next.js, SSR concepts, frontend tooling. Solid understanding of HTML, CSS, responsive layouts, accessibility best practices. Expertise in maintaining CI/CD pipelines such as CircleCI. Expertise in software testing with unit and end-to-end tests using frameworks such as Cypress, Jest, Testim, or Detox. Nice to have: hands-on React Native experience building and shipping features. A plus: experience in Golang, Ruby on Rails, Node.js, or Java. That's Skills/Requirements. - "Company-wide, we enjoy an amazing ecosystem of an even gender split and a balance of engineers and designers. Because Paperless Post isn't supported by ad revenue, we can focus our efforts on creating and improving on the ideal version of our platform, product, content, and partnerships for our users. We are proud that Paperless Post has helped over 220 million people globally connect in the real world since our inception. Paperless Post exists to help all people celebrate all the moments that matter to them. We believe that having a team reflective of the diverse world around us empowers us to create a product that serves everyone. Women, people of color, trans/genderqueer individuals, individuals with disabilities, and veterans are especially encouraged to apply." This is EEO/diversity statement; we must remove EEO boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop that paragraph. - "AI Usage Note" paragraph about AI usage in interviews, etc. That's also boilerplate? It's about policy; maybe we should remove as it's not substantive job content. Likely remove. - "We are committed to providing reasonable accommodations..." also EEO/accommodations; remove. - "The compensation range for this role is $152,100 - $185,000 USD. At Paperless Post, compensation is based on a number of factors, including geographic location, job-related skills, years of experience, and internal team banding. All full-time offer packages come with a base salary, equity component, and options for fully paid medical, dental, and vision benefits. The range posted here is based on the NYC market and may vary based on candidate location. While this position is remote-friendly, we can only employ in the following locations: New York, New Jersey, Connecticut, Pennsylvania, North Carolina, California, Colorado, Ohio, Texas, Florida, Illinois, Washington, Maine." That includes Pay and Benefits and Schedule? It mentions compensation range, benefits (medical, dental, vision), equity component. Also mentions remote-friendly and location restrictions (maybe schedule? Not exactly schedule). There's no explicit schedule (e.g., full-time, hours). So we can include Pay section with salary range and note about equity, benefits. Benefits section could list medical, dental, vision, equity, maybe remote-friendly? But remote-friendly is more about location; maybe we can put under Benefits? But we should only include sections if posting has real specific content. It does have compensation range and benefits details. So we can include Pay and Benefits. Schedule: No explicit schedule (e.g., full-time, hours). Could infer full-time but not stated. Better to omit Schedule section. Responsibilities: The posting mentions "You'll drive frontend architecture decisions, and partner closely with product and design as part of a deeply collaborative team." That's a responsibility. Also maybe "drive frontend architecture decisions" is responsibility. Also maybe "partner closely with product and design". Could also include "help craft the rich, polished experiences". That's more about role. We can put responsibilities as bullet list: Drive frontend architecture decisions; Partner closely with product and design; Collaborate with team; Mentor engineers (mentioned under what you bring). Actually mentoring is under what you bring, but could be responsibility. We'll keep responsibilities as those explicit duties. Requirements: Could be the 6+ years experience, expert-level fluency in orchestrating agentic AI workflows, collaborative mindset, passion, critical thinking, ability to mentor, etc. Also maybe "expertise in TypeScript & React" etc. But those are skills. We'll separate. Qualifications: Could be similar to requirements; but we need to avoid duplication. We can decide to have Requirements (experience, soft skills) and Qualifications (technical expertise). Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. So we might combine into Requirements and Skills. But we have headings list; we can choose to include only those with content. Let's think: The posting includes: - About the role: intro + company description (maybe we keep company description as part of About the role). We'll keep. - Responsibilities: drive frontend architecture decisions, partner with product/design, collaborate with team (maybe also mentor). We'll list. - Requirements: 6+ years experience developing for web/mobile in established codebase; expert-level fluency in orchestrating agentic AI workflows; collaborative mindset; passion for solving problems; strong critical thinking; ability to mentor engineers; collaborate effectively with cross-functional teams. (These are from "What you bring to the table"). - Qualifications: maybe we could treat "Tech stack" as Qualifications. Or Skills. Let's decide: Qualifications = technical expertise (TypeScript, React, GraphQL, Next.js, SSR, HTML/CSS, accessibility, CI/CD, testing). Skills = maybe nice-to-haves (React Native, Golang, Ruby on Rails, Node.js, Java). But the instruction says prefer few sections; we could combine Qualifications and Skills into one "Skills" section covering both required and nice-to-have. But we have both headings allowed; we could include Skills for required tech stack, and maybe Qualifications for nice-to-have? However Qualifications usually refers to required qualifications. Let's treat Qualifications as required technical qualifications, and Skills as nice-to-have/pluses. That seems reasonable. - Benefits: base salary, equity component, options for fully paid medical, dental, vision benefits. Also mention remote-friendly? Could be under Benefits or maybe under Pay? We'll put Benefits: medical, dental, vision, equity, remote-friendly (location flexibility). But remote-friendly is location not benefit; but we can include as part of Benefits? Might be better to put under Pay? Actually Pay section includes salary range and equity component. Benefits section includes medical, dental, vision, maybe remote-friendly? We'll decide. - Pay: compensation range $152,100 - $185,000 USD, based on NYC market, may vary by location, compensation based on factors, base salary, equity component. - Schedule: not present, omit. We must not include placeholder text like "commensurate with experience". We have specific numbers. We must not include boilerplate like EEO, AI usage note, accommodations. We must preserve all substantive information. So we need to keep the list of locations where they can employ: New York, New Jersey, Connecticut, Pennsylvania, North Carolina, California, Colorado, Ohio, Texas, Florida, Illinois, Washington, Maine. That's substantive; where to put? Could be under Benefits or maybe under Pay? It's about employment eligibility. Could be under Benefits as "Eligible work locations". Or we could add a separate section like "Location" but not in allowed headings. So we need to fold into existing allowed heading. Perhaps under Benefits we can include "Eligible to work in: NY, NJ, CT, PA, NC, CA, CO, OH, TX, FL, IL, WA, ME". Or under Pay we could note location-based variation. I'd put under Benefits. Also note "While this position is remote-friendly, we can only employ in the following locations:" That's substantive. Now we need to format HTML: use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. So no

  Senior Frontend Engineer

  . We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft:

  About the role

  Paperless Post is looking for a Senior Frontend Engineer to help craft the rich, polished experiences that millions of people rely on to celebrate the moments that matter. You'll drive frontend architecture decisions, and partner closely with product and design as part of a deeply collaborative team. We're looking for someone who cares about the craft — and equally about the people on the other side of the screen.

  The Paperless Post Engineering team, a highly collaborative group of developers and technologists, is charged with building and refining a consumer-facing product that millions of people interact with each month. Our individual feature teams each focus on a unique piece of the user experience and are made up of engineers, product managers, quality assurers, and product designers. We prioritize creativity and continuing education, and our ongoing commitment to quality code shows in our pragmatic but brave approach to technology. Our engineers are increasingly working alongside AI, running tools like Claude Code across multiple streams of work at once. That means less time writing code by hand and more time on architecture, judgment, and the problems only people can solve. It's helped us increase our output this year while reducing deploy-related incidents compared to the same period last year.

  That's About the role. Now Responsibilities:

  Responsibilities

  • Drive frontend architecture decisions
  • Partner closely with product and design teams
  • Collaborate with cross‑functional team members
  • Mentor engineers
  But note mentoring is from "What you bring". Could be responsibility. We'll include. Now Requirements (experience/soft skills):

  Requirements

  • 6+ years of experience developing for web or mobile platforms in an established codebase
  • Expert‑level fluency in orchestrating agentic AI workflows (e.g., Claude Code, Cursor, Copilot)
  • Collaborative mindset supporting clear communication and constructive feedback
  • Passion for solving problems and building features for end users
  • Strong critical thinking skills with ability to influence architecture and articulate technical decisions across teams
  • Ability to mentor engineers and collaborate effectively with cross‑functional teams
  Now Qualifications (required technical qualifications):

  Qualifications

  • Expertise in TypeScript & React
  • Proficiency in GraphQL
  • Familiarity with Next.js, SSR concepts, and frontend tooling