Senior Software Engineer, Backend
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title. Must not include navigation etc.
We must preserve all substantive info. So we need to include details: about Paperless Post engineering team, collaborative, AI usage, etc. Also mention "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also "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 "A little bit about us" paragraph.
Also mention "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."
Also "What you bring to the table" bullet list.
Also "Tech stack:" bullet list.
Also "Company-wide, we enjoy an amazing ecosystem of an even gender split and a balance of engineers and designers." Also "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." Also "We are proud that Paperless Post has helped over 220 million people globally connect in the real world since our inception." Also mission statement.
Also "Women, people of color, trans/genderqueer individuals, individuals with disabilities, and veterans are especially encouraged to apply." That's EEO but maybe we should remove as boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So that line is EEO encouragement; we should remove it. Also "AI Usage Note" maybe not boilerplate? It's about policy; might be considered legal? It's about AI usage in interviews. Might be considered boilerplate? Probably we should remove it as it's not substantive about the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI Usage Note is more like policy; could be considered legal. Safer to remove.
Also "We are committed to providing reasonable accommodations." That's EEO/legal; remove.
Also "The compensation range for this role is $165,000 - $195,000 USD." Keep.
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." Keep maybe as 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." Keep as Benefits.
Also "The range posted here is based on the NYC market and may vary based on candidate location." Keep.
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." Keep maybe as part of About the role or a separate Location section but not required; we could embed in About the role.
We must not create Schedule section.
Now decide sections:
- About the role: include intro paragraphs about role, team, mission, remote-friendly locations.
- Responsibilities: maybe from "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also "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". Also maybe "Our engineers are increasingly working alongside AI..." but that's more about team.
We could treat responsibilities as bullet list: work across distributed systems, develop RESTful APIs, maintain SLAs, influence architecture, mentor engineers, collaborate cross-functional, etc.
But we must not invent; we need to pull from text. The text includes: "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also "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 "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." That's more a requirement.
"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."
Those are qualifications/skills.
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 have sections: Responsibilities (maybe short), Requirements (maybe combine qualifications and tech stack), Skills (maybe separate). But we must not create thin sections. Better to combine into one "Requirements" section that includes both qualifications and tech stack. Or have "Qualifications" and "Skills". The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (including qualifications and tech stack), Benefits, Pay. That's 5 sections.
We must not include Schedule.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
Structure:
About the role
... paragraphs ...
Responsibilities
- ... items ...
Requirements
- ... items ...
Benefits
- ... items ...
Pay
... compensation range ...
We must not repeat job title.
Now craft content.
About the role paragraph: combine 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." Then maybe add about team: "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." Then location/remote: "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." Also mission: "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." Also stats: "Paperless Post has helped over 220 million people globally connect in the real world since our inception." Also note about ad revenue: "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." Also gender split: "Company-wide, we enjoy an amazing ecosystem of an even gender split and a balance of engineers and designers."
We need to ensure we don't include EEO lines.
Now Responsibilities bullet list: from text: "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 — understanding that we're not just shipping code, we're keeping our users' trust." That's more attribute. Responsibilities could be: "Work across distributed systems and web infrastructure", "Develop and maintain RESTful APIs while upholding SLAs", "Orchestrate agentic AI workflows using tools like Claude Code, Cursor, or Copilot to manage multiple streams of work", "Influence architecture and articulate technical decisions across teams", "Mentor engineers and collaborate effectively with cross-functional teams", "Solve problems and build features for end users", "Navigate ambiguity and follow through on commitments", "Balance quick iteration with practical solutions". Ensure each is from text.
Now Requirements bullet list: include qualifications: "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
for prose. We must not repeat job title. Must not include navigation etc. We must preserve all substantive info. So we need to include details: about Paperless Post engineering team, collaborative, AI usage, etc. Also mention "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also "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 "A little bit about us" paragraph. Also mention "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." Also "What you bring to the table" bullet list. Also "Tech stack:" bullet list. Also "Company-wide, we enjoy an amazing ecosystem of an even gender split and a balance of engineers and designers." Also "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." Also "We are proud that Paperless Post has helped over 220 million people globally connect in the real world since our inception." Also mission statement. Also "Women, people of color, trans/genderqueer individuals, individuals with disabilities, and veterans are especially encouraged to apply." That's EEO but maybe we should remove as boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So that line is EEO encouragement; we should remove it. Also "AI Usage Note" maybe not boilerplate? It's about policy; might be considered legal? It's about AI usage in interviews. Might be considered boilerplate? Probably we should remove it as it's not substantive about the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI Usage Note is more like policy; could be considered legal. Safer to remove. Also "We are committed to providing reasonable accommodations." That's EEO/legal; remove. Also "The compensation range for this role is $165,000 - $195,000 USD." Keep. 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." Keep maybe as 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." Keep as Benefits. Also "The range posted here is based on the NYC market and may vary based on candidate location." Keep. 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." Keep maybe as part of About the role or a separate Location section but not required; we could embed in About the role. We must not create Schedule section. Now decide sections: - About the role: include intro paragraphs about role, team, mission, remote-friendly locations. - Responsibilities: maybe from "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also "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". Also maybe "Our engineers are increasingly working alongside AI..." but that's more about team. We could treat responsibilities as bullet list: work across distributed systems, develop RESTful APIs, maintain SLAs, influence architecture, mentor engineers, collaborate cross-functional, etc. But we must not invent; we need to pull from text. The text includes: "You'll work across distributed systems and web infrastructure as part of a deeply collaborative team with a robust development process." Also "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 "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." That's more a requirement. "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." Those are qualifications/skills. 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 have sections: Responsibilities (maybe short), Requirements (maybe combine qualifications and tech stack), Skills (maybe separate). But we must not create thin sections. Better to combine into one "Requirements" section that includes both qualifications and tech stack. Or have "Qualifications" and "Skills". The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (including qualifications and tech stack), Benefits, Pay. That's 5 sections. We must not include Schedule. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. Structure:
About the role
... paragraphs ...
Responsibilities
- ... items ...
Requirements
- ... items ...
Benefits
- ... items ...
Pay
... compensation range ...
We must not repeat job title. Now craft content. About the role paragraph: combine 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." Then maybe add about team: "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." Then location/remote: "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." Also mission: "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." Also stats: "Paperless Post has helped over 220 million people globally connect in the real world since our inception." Also note about ad revenue: "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." Also gender split: "Company-wide, we enjoy an amazing ecosystem of an even gender split and a balance of engineers and designers." We need to ensure we don't include EEO lines. Now Responsibilities bullet list: from text: "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 — understanding that we're not just shipping code, we're keeping our users' trust." That's more attribute. Responsibilities could be: "Work across distributed systems and web infrastructure", "Develop and maintain RESTful APIs while upholding SLAs", "Orchestrate agentic AI workflows using tools like Claude Code, Cursor, or Copilot to manage multiple streams of work", "Influence architecture and articulate technical decisions across teams", "Mentor engineers and collaborate effectively with cross-functional teams", "Solve problems and build features for end users", "Navigate ambiguity and follow through on commitments", "Balance quick iteration with practical solutions". Ensure each is from text. Now Requirements bullet list: include qualifications: "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