Senior Software Engineer, Backend

Paperless Post · San Francisco, CA · 1 mo ago

RemoteRemoteEngineering$165k–$195k/yrFull-time

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. Must preserve all substantive info. Remove boilerplate like EEO, etc. Must not include sections with placeholder text. We need to parse the posting. Key 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": description of engineering team, collaborative, consumer-facing product, feature teams, creativity, continuing education, quality code, pragmatic but brave approach, engineers working alongside AI, using 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 problem-solving, ability to mentor engineers, collaborate cross-functional. - 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: amazing ecosystem of even gender split and balance of engineers and designers. Because Paperless Post isn't supported by ad revenue, we can focus on creating ideal version of platform, product, content, partnerships. Proud that helped over 220 million people globally connect. 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: description of policy about AI usage in interviews. This is likely boilerplate but maybe considered relevant? It's about interview policy. Might be considered not substantive for role? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. AI Usage Note might be considered legal/boilerplate? It's about interview policy, maybe not needed. Probably remove. - "We are committed to providing reasonable accommodations..." also likely boilerplate. - Compensation: "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." Thus we have Pay section with salary range and benefits mention. Also location restrictions. We need sections: About the role (maybe intro), Responsibilities (maybe what you'll do), Requirements (experience), Qualifications (maybe tech stack?), Skills (maybe soft skills), Benefits (benefits mentioned), Pay (salary range), Schedule (maybe remote-friendly? Not explicit schedule). The posting does not mention schedule specifics (like full-time, hours). It says remote-friendly but location restrictions. No explicit schedule like "full-time", "40 hours/week". Might not include Schedule section if no specific content. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to include details about role, responsibilities, requirements, qualifications, skills, benefits, pay. We must decide how to map content to sections. Section headings:

About the role

Responsibilities

Requirements

Qualifications

Skills

Benefits

Pay

Schedule

. We should only include sections that have real specific content. Let's extract: About the role: Could be the introductory paragraph describing 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." That's substantive. Responsibilities: Could be derived from "You'll work across distributed systems and web infrastructure..." plus maybe "As a senior member... bring technical depth, strong ownership, genuine care for end user". Also maybe "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also maybe "As a senior member of the team, you'll bring technical depth, strong ownership, and a genuine care for the end user". Also maybe "You'll work across distributed systems and web infrastructure". Also maybe "As a senior member... you'll bring technical depth...". Also maybe "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team". Also maybe "You'll bring technical depth, strong ownership, and a genuine care for the end user". Also maybe "You'll work across distributed systems and web infrastructure". Also maybe "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." Also maybe "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also maybe "As a senior member of the team, you'll bring technical depth, strong ownership, and a genuine care for the end user". Also maybe "You'll work across distributed systems and web infrastructure". Also maybe "As a senior member of the team, you'll bring technical depth, strong ownership, and a genuine care for the end user". Also maybe "You'll work across distributed systems and web infrastructure". Also maybe "As a senior member of the team, you'll bring technical depth, strong ownership, and a genuine care for the end user". This is repetitive. Better to extract responsibilities from "What you bring to the table" maybe? Actually that's more qualifications. Responsibilities could be: "Help build and evolve the services that power our events management platform", "Work across distributed systems and web infrastructure", "Part of a deeply collaborative team with a robust development process", "Bring technical depth, strong ownership, genuine care for end user", "Keep users' trust". Also maybe "Work alongside AI, running tools like Claude Code across multiple streams of work". Actually that's under "A little bit about us". But responsibilities could be derived from the role description. Qualifications: Could be the "What you bring to the table" list (6+ years experience, AI workflow expertise, distributed systems, RESTful APIs, critical thinking, collaborative mindset, passion, ownership, problem-solving, mentoring). Also tech stack requirements. Skills: Could be the technical skills: expertise in statically typed language, Golang, Ruby on Rails, Node.js, Java, Postgres, CI/CD (CircleCI), testing (Ginkgo/Gomega), nice to have TypeScript/React, GraphQL. Benefits: "All full-time offer packages come with a base salary, equity component, and options for fully paid medical, dental, and vision benefits." Also maybe "We prioritize creativity and continuing education". Also maybe "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 more about culture. Pay: Salary range $165,000 - $195,000 USD, plus note about location-based variation, equity component already in benefits. Schedule: Not explicit. Could mention remote-friendly but location restrictions. That's not schedule. Could maybe treat location as schedule? Not appropriate. Probably omit Schedule section. We must not include sections with placeholder text. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also a section for "Location" but not in list; we could fold location into Pay or Benefits? The instruction says we can only use those headings. So we must not create new headings. So location info must be placed somewhere else, maybe in Pay section as a note, or in About the role? Probably we can include location note in Pay section as a short paragraph. We must not include boilerplate like EEO, AI Usage Note, accommodations, etc. We must preserve all substantive information. So we need to ensure we don't drop any substantive info like the AI workflow expertise, the mention of Claude Code, etc. Let's draft sections. 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.

Responsibilities: Could be a

Help build and evolve the services that power our events management platform.
Work across distributed systems and web infrastructure.
Collaborate within a deeply collaborative team following a robust development process.
Bring technical depth, strong ownership, and genuine care for the end user to maintain users' trust.
Leverage AI tools like Claude Code to manage multiple streams of work, focusing on architecture and judgment.

. Qualifications: Could be the tech stack requirements: 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