Senior Software Engineer, Backend

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. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. Let's parse the posting. Content: - Intro: "Paperless Post is looking for a few Senior Backend Engineers to help build and evolve the services that power our events management platform. You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process. As a senior member of the team, you'll bring technical depth, strong ownership, and a genuine care for the end user — understanding that we're not just shipping code, we're keeping our users' trust." - "A little bit about us" paragraph: description of engineering team, collaborative, consumer-facing product, feature teams, prioritize creativity, continuing education, quality code, pragmatic but brave approach, engineers working alongside AI, tools like Claude Code, increased output, reduced incidents. - "What you bring to the table": list of requirements/experience: 6+ years backend/full-stack, expert-level fluency in orchestrating agentic AI workflows (Claude Code, Cursor, Copilot), extensive experience building and scaling distributed systems and web infrastructure, expertise in developing RESTful APIs and maintaining SLAs, strong critical thinking, ability to influence architecture, collaborative mindset, passion for solving problems, strong sense of ownership, resourceful proactive problem-solving, ability to mentor engineers, collaborate with cross-functional teams. - "Tech stack: Expertise in at least one statically typed language. Experience in Golang, Ruby on Rails, Node.js, Java, or similar technology is a must. Deep understanding of relational databases like Postgres. Expertise in maintaining CI/CD pipelines such as CircleCI. Expertise in software testing with unit and integration test suites such as Ginkgo and Gomega. Nice to have: expertise in TypeScript & React and proficiency in GraphQL." - "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." - "AI Usage Note": details about AI usage policy, interview restrictions, accommodations. - "We are committed to providing reasonable accommodations. This policy does not apply to approved accessibility or disability accommodations. If you require assistive technology or other support, please let the recruiting team know." - "The compensation range for this role is $165,000 - $195,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." We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be the intro describing role: building services, distributed systems, collaborative team, senior member, etc. That seems appropriate. - Responsibilities: The posting does not explicitly list responsibilities as bullet list; but we can infer from description: building and evolving services, working across distributed systems and web infrastructure, collaborating, bringing technical depth, ownership, caring for end user, etc. However we must not invent or summarize away detail; we must preserve all substantive information. If the posting does not have explicit responsibilities list, we should not create a Responsibilities section with placeholder. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only include sections where there is explicit content. Thus we need to see if there is a list of duties/responsibilities. The posting includes: "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process. As a senior member of the team, you'll bring technical depth, strong ownership, and a genuine care for the end user — understanding that we're not just shipping code, we're keeping our users' trust." That's more about what you'll do, could be considered responsibilities. But it's not a list; it's prose. We could put that in About the role or Responsibilities as prose. However we need to avoid duplication. Usually About the role is a brief description; Responsibilities is bullet list of duties. Since we don't have explicit bullet list, maybe we should not create Responsibilities section. Instead we can put that description under About the role. - Requirements: The "What you bring to the table" list includes experience, expertise, etc. That's requirements. Also tech stack could be requirements. So we can have Requirements section with bullet list. - Qualifications: Might overlap with Requirements. Could separate but we need to avoid thin sections. Perhaps combine Requirements and Qualifications? But we need to follow headings: we can have Requirements and Qualifications if there is distinct content. The posting does not separate qualifications vs requirements explicitly. Could treat "What you bring to the table" as Requirements, and "Tech stack" as Qualifications? Or maybe Skills section for tech stack. Let's think. We have sections: Skills (could be tech stack). Benefits (we have benefits: base salary, equity component, options for fully paid medical, dental, vision benefits). Pay (compensation range). Schedule (maybe remote-friendly and locations). The posting mentions remote-friendly and locations list. That could be Schedule? Actually schedule is about work hours, remote, etc. Could be considered Schedule/Location. The instruction says use Schedule heading for schedule info. We have location restrictions and remote-friendly. That's schedule-related. So we can include Schedule section with that info. Benefits: medical, dental, vision, equity, base salary (though base salary is Pay). Benefits: equity component, options for fully paid medical, dental, vision benefits. Pay: compensation range $165k-$195k. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO encouragement, AI usage note, accommodations note (though accommodations is part of policy but maybe we can keep? It's not boilerplate? It's about accommodations; could be considered relevant but it's more policy. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The AI usage note and accommodations might be considered legal/policy. Probably remove them. Also remove "We are committed to providing reasonable accommodations..." etc. That's legal. So we should drop AI Usage Note and accommodations paragraph. Also remove the diversity encouragement statement? That's EEO/equal-opportunity boilerplate. Remove. Thus we keep: intro, about us paragraph, what you bring to the table, tech stack, company-wide statements about gender split, ad revenue, 220 million people, mission, diversity encouragement (remove), compensation range, benefits, remote-friendly locations. We need to preserve all substantive information. The company-wide statements about gender split, ad revenue, 220 million, mission are substantive about company. Could go under About the role or maybe a separate section like "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company info under About the role as well (makes sense). Or we could create a separate section like "About the company" but not allowed. So we incorporate into About the role. Thus About the role will include: intro about role, description of engineering team, company mission, impact, etc. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's craft sections: maybe not needed; just headings and content. We'll produce:

  About the role

  Paperless Post is looking for a few Senior Backend Engineers to help build and evolve the services that power our events management platform. You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process. As a senior member of the team, you'll bring technical depth, strong ownership, and a genuine care for the end user — understanding that we're not just shipping code, we're keeping our users' trust.

  The Paperless Post Engineering team is a highly collaborative group of developers and technologists building and refining a consumer‑facing product that millions of people interact with each month. Individual feature teams focus on unique pieces of the user experience and include engineers, product managers, quality assurers, and product designers. The team prioritizes creativity and continuing education, follows a pragmatic but brave approach to technology, and increasingly works alongside AI tools such as Claude Code to increase output while reducing deploy‑related incidents. Paperless Post has helped over 220 million people globally connect in the real world since its inception and exists to help all people celebrate the moments that matter to them.

  That seems good. Now Requirements: we have "What you bring to the table" list. Let's turn each bullet into
• . Also include tech stack? Might be separate Skills section. Let's create Requirements section with bullet list of the experience/skills items (excluding tech stack). Items: - 6+ years of experience as a backend or full-stack engineer 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. - Extensive experience building and scaling distributed systems and web infrastructure. - Expertise in developing RESTful APIs and maintaining SLAs. - Strong critical thinking skills with the ability to influence architecture and articulate technical decisions across teams. - A collaborative mindset that supports clear communication and constructive feedback. - A passion for solving problems and building features for end users. - A strong sense of ownership and accountability, with the ability to navigate ambiguity and follow through on commitments. - Resourceful and proactive problem‑solving, balancing quick iteration with practical solutions. - Ability to mentor engineers and collaborate effectively with cross‑functional teams. Now Skills section: tech stack. - Expertise in at least one statically typed language. - Experience in Golang, Ruby on Rails, Node.js, Java, or similar technology is a must. - Deep understanding of relational databases like Postgres. - Expertise in maintaining CI/CD pipelines such as CircleCI. - Expertise in software testing with unit and integration test suites such as Ginkgo and Gomega. - Nice to have: expertise in TypeScript & React and proficiency in GraphQL. We could separate must-have vs nice-to-have but still list. Now Benefits: base salary, equity component, options for fully paid medical, dental, vision benefits. Also maybe mention "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. We'll put in
  • . Pay: compensation range $165,000 - $195,000 USD. Also note that compensation based on factors,