Senior Software Engineer, Frontend
or drop it." Location restrictions could be considered minor metadata; we could include in a short p under maybe About the role or separate? But we need to preserve ALL substantive information. Location restrictions are substantive for eligibility. Should we include? Probably yes, as a short p. Also "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's substantive. Also "At Paperless Post, compensation is based on a number of factors, including geographic location, job-related skills, years of experience, and internal team banding." That's part of Pay. Also "All full-time offer packages come with a base salary, equity component, and options for fully paid medical, dental, and vision benefits." That's Benefits. Also "Company-wide, we enjoy an amazing ecosystem of an even gender split and a balance of engineers and designers." Could be part of About the role or maybe a separate section like Culture? Not in allowed headings. Could fold into About the role. Also "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." That's EEO boilerplate; we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that. Also "AI Usage Note" etc is boilerplate about AI usage in interviews; we should remove as it's not substantive job content? It's about interview policy; maybe considered boilerplate; but it's somewhat specific. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. AI usage note might be considered legal? Probably remove. Also "We are committed to providing reasonable accommodations." That's also EEO; remove. Thus we keep core job description. Now structure:
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.
Maybe also include location restrictions as a short p after About the role? Could be separatebut not a heading. But we need to preserve ALL substantive information; location restrictions is substantive. We'll add a
after About the role. Now Responsibilities: list bullet points. Responsibilities: - Drive frontend architecture decisions. - Partner closely with product and design. - Mentor engineers. - Collaborate effectively with cross-functional teams. - Influence architecture and articulate technical decisions across teams. - Solve problems and build features for end users. We could also include "orchestrating agentic AI workflows" but that's more skill/requirement. Now Requirements: maybe "6+ years of experience developing for web or mobile platforms in an established codebase." "Expert-level fluency in orchestrating agentic AI workflows; you leverage tools like Claude Code, Cursor, or Copilot to manage multiple streams of work, shifting your focus from manual code generation to architectural strategy and technical execution." Also "collaborative mindset that supports clear communication and constructive feedback." "Passion for solving problems and building features for end users." "Strong critical thinking skills with the ability to influence architecture and articulate technical decisions across teams." "Ability to mentor engineers and collaborate effectively with cross-functional teams." But many overlap with responsibilities. We need to differentiate: Usually Requirements are qualifications needed. We'll list those. Qualifications: maybe same as Requirements? Could combine but we need separate sections only if distinct content. Could treat Requirements as experience and technical qualifications, Qualifications as soft skills? But we risk duplication. Better: Use Requirements for experience and technical qualifications; Qualifications for soft skills and mindsets. Let's define: Requirements: - 6+ years of experience developing for web or mobile platforms in an established codebase. - Expert-level fluency in orchestrating agentic AI workflows; you leverage tools like Claude Code, Cursor, or Copilot to manage multiple streams of work, shifting your focus from manual code generation to architectural strategy and technical execution. Qualifications: - Collaborative mindset that supports clear communication and constructive feedback. - Passion for solving problems and building features for end users. - Strong critical thinking skills with the ability to influence architecture and articulate technical decisions across teams. - Ability to mentor engineers and collaborate effectively with cross-functional teams. Skills: tech stack list. Benefits: base salary, equity component, fully paid medical, dental, vision benefits. Pay: compensation range $152,100 - $185,000 USD; note based on NYC market, may vary based on candidate location; compensation based on geographic location, job-related skills, years of experience, internal team banding. We could combine Pay and Benefits? But they are distinct. We must not create sections with filler like "commensurate with experience". We have actual numbers. Now output HTML fragment. We need to ensure we don't repeat job title. Let's craft. We'll include
About the role
then... maybe multiple paragraphs? Could combine into one
but long; okay. After that, a
for location restrictions: "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." Now Responsibilities
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
...
We should not include Schedule. Check for any duplicated lines: ensure we didn't repeat. Now write content. About the role paragraph: combine the initial description and "A little bit about us" etc. Let's draft: "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