Staff Software Engineer, Public API
Etsy · Brooklyn, NY · 2 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually we have company description, role description, team description, day-to-day, qualities, compensation & benefits, location, etc. We must not repeat job title as heading. Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content.
We have:
- Company Description: could be "About the role"? Actually "About the role" is a heading for description of role. Could use "About the role" for the role description (What’s the Role?). Also "What’s this team like at Etsy?" could be "Team" maybe not a standard heading but we could put under "About the role" or separate "Team". The instruction: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content.
We have:
- Company Description: could be "About the role"? Actually "About the role" is a heading for description of role. Could use "About the role" for the role description (What’s the Role?). Also "What’s this team like at Etsy?" could be "Team" maybe not a standard heading but we could put under "About the role" or separate "Team". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings only if content exists. We can also add other headings? It says use for section headings (e.g. ...). Likely they expect those headings. We should include sections that have content: About the role, Responsibilities, Requirements (maybe Qualifications), Skills, Benefits, Pay. Schedule not present (no schedule details). So omit Schedule.
We need to extract content:
About the role: description of role: "The OpenAPI team works on Etsy’s public API provided for sellers and 3rd party developers. We build and maintain technical capabilities to enable our users to integrate with our API and build apps to extend Etsy tooling. We also work closely with various product teams at Etsy when they build new features on our team’s platform. We are looking for a backend engineer to join our team where you will collaborate closely with a dedicated team of backend engineers, a product manager, and an engineering manager. You will work on a variety of back-end projects to improve the developer experience and stability of OpenAPI, such as system performance optimization, agentic tooling, security enhancements, testing functionality, and webhooks. You will also provide guidance to internal teams at Etsy to assist them in rolling out new features on OpenAPI and managing breaking changes. As a staff engineer, you will partner with team leads to set the technical direction of the team. This will involve keeping tabs on recurring pain points on our platform, potential opportunities that arise across the company, and industry trends. Based on this expertise, you will help decide which tracks of work our team pursues. You will be responsible for the design of larger projects and will mentor junior teammates on designing smaller projects. This is a full time role reporting to the Senior Engineering Manager."
That's about role.
Responsibilities: day-to-day list: "Build and maintain software written in PHP", "Evolve the OpenAPI platform by identifying areas of friction and implementing features that can measurably improve Developer Experience.", "Partner with product engineering teams to build and roll out new features", "Debug hairy issues spanning multiple systems to determine the root cause and either route it to the appropriate owner or fix yourself", "Collaborate with cross functional partners - product, analytics, research, etc - to determine the highest impact projects that align with our team’s strategy", "Work with teammates and other subject matter experts as necessary to scope out new platform projects and break them down into multiple stages for delivery, identifying and resolving architectural trade-offs", "Write high quality code and mentor your teammates to do the same through PR reviews, pairing, and general mentoring", "Steer the technical direction of the team, from which projects we work on to which team processes we follow". Also maybe "Of course, this is just a sample..." but that's not a responsibility.
We can put these as - .
Requirements/Qualifications: The "Qualities that will help you thrive in this role are:" list: Experience with object-oriented software languages. The majority of work developed will be in PHP. Experience building and maintaining REST APIs (especially managing breaking changes) and related technical capabilities. Experience using observability tools to monitor API usage and related metrics, such as Grafana, HoneyComb, or Google Cloud Logging. A strong sense of ownership for our platform. The ability to think critically and independently to ensure we are building the right things in the right way. Close attention to detail, with the ability to translate business requirements to production-ready code. Strong communication that adapts to technical and non-technical audiences. Curiosity and ability to learn autonomously. Experience working with AI Agents and related tools, like MCP servers and skills.
We could split into Requirements (maybe experience) and Qualifications (skills). But we can combine into one section "Qualifications" or "Requirements". The instruction says use headings like Requirements, Qualifications, Skills. We have both. We could put experience items under Requirements, and skills/abilities under Qualifications, and maybe specific technical skills under Skills. But we have overlapping. Let's decide:
- Requirements: Experience with object-oriented software languages (PHP), Experience building and maintaining REST APIs (especially managing breaking changes), Experience using observability tools (Grafana, HoneyComb, Google Cloud Logging), Experience working with AI Agents and related tools (MCP servers and skills).
- Qualifications: Strong sense of ownership, ability to think critically and independently, close attention to detail, strong communication, curiosity and ability to learn autonomously.
- Skills: maybe not separate; but we could put technical skills like PHP, REST APIs, observability, AI agents under Skills. However we already used them in Requirements. To avoid duplication, maybe we just have Requirements and Qualifications, and omit Skills. The instruction says we can include sections only when posting has real specific content. We have content for Requirements and Qualifications. We'll not create Skills if we think it's redundant.
Benefits: "In addition to salary, you'll be eligible for an equity package, an annual performance bonus, and our competitive benefits that support you and your family." Also maybe mention "competitive benefits". We'll list equity package, annual performance bonus, competitive benefits.
Pay: Salary ranges: Geo-1: 197,000 - 267,000 USD Annual; Geo-2: 178,000 - 240,000 USD Annual. Also note base salary determined by location, skills, experience. We'll include that.
Location: Not a standard heading but we could include under "About the role" or separate? Not in list. Could omit or include as paragraph under About the role. The instruction says we can include other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to stick to those. Location info could be placed in a
under About the role or Pay? Probably under About the role as part of role description. We'll include a short paragraph about location: "We prioritize candidates based within commutable distance of Etsy’s Brooklyn Office. Depending on proximity, we ask team members to come in once or twice per week. Remote candidates outside commutable distance may be considered on a case-by-case basis, with the expectation of occasional travel to the office."
We'll put that as a
after the About the role content.
Now we need to output only HTML fragment, no /, no markdown fences.
Structure:
About the role
... role description ...
Location paragraph.
Responsibilities
- ... each responsibility ...
Requirements
- ... each requirement ...
Qualifications
- ... each qualification ...
Benefits
- ... each benefit ...
Pay
... salary ranges ...
We must not include Schedule.
Check for any duplicated lines: ensure we don't repeat.
Now craft content precisely.
About the role paragraph: combine the description.
Let's write:
"The OpenAPI team works on Etsy’s public API provided for sellers and 3rd party developers. We build and maintain technical capabilities to enable our users to integrate with our API and build apps to extend Etsy tooling. We also work closely with various product teams at Etsy when they build new features on our team’s platform. We are looking for a backend engineer to join our team where you will collaborate closely with a dedicated team of backend engineers, a product manager, and an engineering manager. You will work on a variety of back-end projects to improve the developer experience and stability of OpenAPI, such as system performance optimization, agentic tooling, security enhancements, testing functionality, and webhooks. You will also provide guidance to internal teams at Etsy to assist them in rolling out new features on OpenAPI and managing breaking changes. As a staff engineer, you will partner with team leads to set the technical direction of the team. This will involve keeping tabs on recurring pain points on our platform, potential opportunities that arise across the company, and industry trends. Based on this expertise, you will help decide which tracks of work our team pursues. You will be responsible for the design of larger projects and will mentor junior teammates on designing smaller projects. This is a full time role reporting to the Senior Engineering Manager."
Location paragraph: "We prioritize candidates based within commutable distance of Etsy’s Brooklyn Office. Depending on proximity, we ask team members to come in once or twice per week. Remote candidates outside commutable distance may be considered on a case‑by‑case basis, with the expectation of occasional travel to the office."
Responsibilities list items:
- Build and maintain software written in PHP
- Evolve the OpenAPI platform by identifying areas of friction and implementing features that can measurably improve Developer Experience
- Partner with product engineering teams to build and roll out new features
- Debug hairy issues spanning multiple systems to determine the root cause and either route it to the appropriate owner or fix yourself
- Collaborate with cross‑functional partners (product, analytics, research, etc.) to determine the highest impact projects that align with our team’s strategy
- Work with teammates and other subject matter experts as necessary to scope out new platform projects and break them down into multiple stages for delivery, identifying and resolving architectural trade‑offs
- Write high quality code and mentor your teammates to do the same through PR reviews, pairing, and general mentoring
- Steer the technical direction of the team, from which projects we work on to which team processes we follow
Requirements list:
- Experience with object‑oriented software languages (the majority of work is developed in PHP)
- Experience building and maintaining REST APIs, especially managing breaking changes, and related technical capabilities
- Experience using observability tools to monitor API usage and related metrics, such as Grafana, HoneyComb, or Google Cloud Logging
- Experience working with AI Agents and related tools, like MCP servers and skills
Qualifications list:
- A strong sense of ownership for the platform
- The ability to think critically and independently to ensure we are building the right things in the right way
- Close attention to detail, with the ability to translate business requirements to production‑ready code
- Strong communication that adapts to technical and non‑technical audiences
- Curiosity and ability to learn autonomously
Benefits list:
- Equity package
- Annual performance bonus
- Competitive benefits that support you and your family
Pay paragraph:
"Base salary is determined by your location, skills, and experience. Etsy uses two geographic pay zones: Geo‑1 (New York City metropolitan area, San Francisco Bay Area, and Seattle metropolitan area) with a salary range of $197,000 – $267,000 USD annually; Geo‑2 (all other U.S. locations) with a salary range of $178,000 – $240,000 USD annually."
Make sure to use proper HTML escaping for $? Not needed.
Now
for section headings (e.g. ...). Likely they expect those headings. We should include sections that have content: About the role, Responsibilities, Requirements (maybe Qualifications), Skills, Benefits, Pay. Schedule not present (no schedule details). So omit Schedule.
We need to extract content:
About the role: description of role: "The OpenAPI team works on Etsy’s public API provided for sellers and 3rd party developers. We build and maintain technical capabilities to enable our users to integrate with our API and build apps to extend Etsy tooling. We also work closely with various product teams at Etsy when they build new features on our team’s platform. We are looking for a backend engineer to join our team where you will collaborate closely with a dedicated team of backend engineers, a product manager, and an engineering manager. You will work on a variety of back-end projects to improve the developer experience and stability of OpenAPI, such as system performance optimization, agentic tooling, security enhancements, testing functionality, and webhooks. You will also provide guidance to internal teams at Etsy to assist them in rolling out new features on OpenAPI and managing breaking changes. As a staff engineer, you will partner with team leads to set the technical direction of the team. This will involve keeping tabs on recurring pain points on our platform, potential opportunities that arise across the company, and industry trends. Based on this expertise, you will help decide which tracks of work our team pursues. You will be responsible for the design of larger projects and will mentor junior teammates on designing smaller projects. This is a full time role reporting to the Senior Engineering Manager."
That's about role.
Responsibilities: day-to-day list: "Build and maintain software written in PHP", "Evolve the OpenAPI platform by identifying areas of friction and implementing features that can measurably improve Developer Experience.", "Partner with product engineering teams to build and roll out new features", "Debug hairy issues spanning multiple systems to determine the root cause and either route it to the appropriate owner or fix yourself", "Collaborate with cross functional partners - product, analytics, research, etc - to determine the highest impact projects that align with our team’s strategy", "Work with teammates and other subject matter experts as necessary to scope out new platform projects and break them down into multiple stages for delivery, identifying and resolving architectural trade-offs", "Write high quality code and mentor your teammates to do the same through PR reviews, pairing, and general mentoring", "Steer the technical direction of the team, from which projects we work on to which team processes we follow". Also maybe "Of course, this is just a sample..." but that's not a responsibility.
We can put these as - .
Requirements/Qualifications: The "Qualities that will help you thrive in this role are:" list: Experience with object-oriented software languages. The majority of work developed will be in PHP. Experience building and maintaining REST APIs (especially managing breaking changes) and related technical capabilities. Experience using observability tools to monitor API usage and related metrics, such as Grafana, HoneyComb, or Google Cloud Logging. A strong sense of ownership for our platform. The ability to think critically and independently to ensure we are building the right things in the right way. Close attention to detail, with the ability to translate business requirements to production-ready code. Strong communication that adapts to technical and non-technical audiences. Curiosity and ability to learn autonomously. Experience working with AI Agents and related tools, like MCP servers and skills.
We could split into Requirements (maybe experience) and Qualifications (skills). But we can combine into one section "Qualifications" or "Requirements". The instruction says use headings like Requirements, Qualifications, Skills. We have both. We could put experience items under Requirements, and skills/abilities under Qualifications, and maybe specific technical skills under Skills. But we have overlapping. Let's decide:
- Requirements: Experience with object-oriented software languages (PHP), Experience building and maintaining REST APIs (especially managing breaking changes), Experience using observability tools (Grafana, HoneyComb, Google Cloud Logging), Experience working with AI Agents and related tools (MCP servers and skills).
- Qualifications: Strong sense of ownership, ability to think critically and independently, close attention to detail, strong communication, curiosity and ability to learn autonomously.
- Skills: maybe not separate; but we could put technical skills like PHP, REST APIs, observability, AI agents under Skills. However we already used them in Requirements. To avoid duplication, maybe we just have Requirements and Qualifications, and omit Skills. The instruction says we can include sections only when posting has real specific content. We have content for Requirements and Qualifications. We'll not create Skills if we think it's redundant.
Benefits: "In addition to salary, you'll be eligible for an equity package, an annual performance bonus, and our competitive benefits that support you and your family." Also maybe mention "competitive benefits". We'll list equity package, annual performance bonus, competitive benefits.
Pay: Salary ranges: Geo-1: 197,000 - 267,000 USD Annual; Geo-2: 178,000 - 240,000 USD Annual. Also note base salary determined by location, skills, experience. We'll include that.
Location: Not a standard heading but we could include under "About the role" or separate? Not in list. Could omit or include as paragraph under About the role. The instruction says we can include other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to stick to those. Location info could be placed in a
under About the role or Pay? Probably under About the role as part of role description. We'll include a short paragraph about location: "We prioritize candidates based within commutable distance of Etsy’s Brooklyn Office. Depending on proximity, we ask team members to come in once or twice per week. Remote candidates outside commutable distance may be considered on a case-by-case basis, with the expectation of occasional travel to the office."
We'll put that as a
after the About the role content.
Now we need to output only HTML fragment, no /, no markdown fences.
Structure:
About the role
... role description ...
Location paragraph.
Responsibilities
- ... each responsibility ...
Requirements
- ... each requirement ...
Qualifications
- ... each qualification ...
Benefits
- ... each benefit ...
Pay
... salary ranges ...
We must not include Schedule.
Check for any duplicated lines: ensure we don't repeat.
Now craft content precisely.
About the role paragraph: combine the description.
Let's write:
"The OpenAPI team works on Etsy’s public API provided for sellers and 3rd party developers. We build and maintain technical capabilities to enable our users to integrate with our API and build apps to extend Etsy tooling. We also work closely with various product teams at Etsy when they build new features on our team’s platform. We are looking for a backend engineer to join our team where you will collaborate closely with a dedicated team of backend engineers, a product manager, and an engineering manager. You will work on a variety of back-end projects to improve the developer experience and stability of OpenAPI, such as system performance optimization, agentic tooling, security enhancements, testing functionality, and webhooks. You will also provide guidance to internal teams at Etsy to assist them in rolling out new features on OpenAPI and managing breaking changes. As a staff engineer, you will partner with team leads to set the technical direction of the team. This will involve keeping tabs on recurring pain points on our platform, potential opportunities that arise across the company, and industry trends. Based on this expertise, you will help decide which tracks of work our team pursues. You will be responsible for the design of larger projects and will mentor junior teammates on designing smaller projects. This is a full time role reporting to the Senior Engineering Manager."
Location paragraph: "We prioritize candidates based within commutable distance of Etsy’s Brooklyn Office. Depending on proximity, we ask team members to come in once or twice per week. Remote candidates outside commutable distance may be considered on a case‑by‑case basis, with the expectation of occasional travel to the office."
Responsibilities list items:
- Build and maintain software written in PHP
- Evolve the OpenAPI platform by identifying areas of friction and implementing features that can measurably improve Developer Experience
- Partner with product engineering teams to build and roll out new features
- Debug hairy issues spanning multiple systems to determine the root cause and either route it to the appropriate owner or fix yourself
- Collaborate with cross‑functional partners (product, analytics, research, etc.) to determine the highest impact projects that align with our team’s strategy
- Work with teammates and other subject matter experts as necessary to scope out new platform projects and break them down into multiple stages for delivery, identifying and resolving architectural trade‑offs
- Write high quality code and mentor your teammates to do the same through PR reviews, pairing, and general mentoring
- Steer the technical direction of the team, from which projects we work on to which team processes we follow
Requirements list:
- Experience with object‑oriented software languages (the majority of work is developed in PHP)
- Experience building and maintaining REST APIs, especially managing breaking changes, and related technical capabilities
- Experience using observability tools to monitor API usage and related metrics, such as Grafana, HoneyComb, or Google Cloud Logging
- Experience working with AI Agents and related tools, like MCP servers and skills
Qualifications list:
- A strong sense of ownership for the platform
- The ability to think critically and independently to ensure we are building the right things in the right way
- Close attention to detail, with the ability to translate business requirements to production‑ready code
- Strong communication that adapts to technical and non‑technical audiences
- Curiosity and ability to learn autonomously
Benefits list:
- Equity package
- Annual performance bonus
- Competitive benefits that support you and your family
Pay paragraph:
"Base salary is determined by your location, skills, and experience. Etsy uses two geographic pay zones: Geo‑1 (New York City metropolitan area, San Francisco Bay Area, and Seattle metropolitan area) with a salary range of $197,000 – $267,000 USD annually; Geo‑2 (all other U.S. locations) with a salary range of $178,000 – $240,000 USD annually."
Make sure to use proper HTML escaping for $? Not needed.
Now
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to stick to those. Location info could be placed in a
under About the role or Pay? Probably under About the role as part of role description. We'll include a short paragraph about location: "We prioritize candidates based within commutable distance of Etsy’s Brooklyn Office. Depending on proximity, we ask team members to come in once or twice per week. Remote candidates outside commutable distance may be considered on a case-by-case basis, with the expectation of occasional travel to the office." We'll put that as a
after the About the role content. Now we need to output only HTML fragment, no /, no markdown fences. Structure:
About the role
... role description ...
Location paragraph.
Responsibilities
- ... each responsibility ...
Requirements
- ... each requirement ...
Qualifications
- ... each qualification ...
Benefits
- ... each benefit ...
Pay
... salary ranges ...
We must not include Schedule. Check for any duplicated lines: ensure we don't repeat. Now craft content precisely. About the role paragraph: combine the description. Let's write: "The OpenAPI team works on Etsy’s public API provided for sellers and 3rd party developers. We build and maintain technical capabilities to enable our users to integrate with our API and build apps to extend Etsy tooling. We also work closely with various product teams at Etsy when they build new features on our team’s platform. We are looking for a backend engineer to join our team where you will collaborate closely with a dedicated team of backend engineers, a product manager, and an engineering manager. You will work on a variety of back-end projects to improve the developer experience and stability of OpenAPI, such as system performance optimization, agentic tooling, security enhancements, testing functionality, and webhooks. You will also provide guidance to internal teams at Etsy to assist them in rolling out new features on OpenAPI and managing breaking changes. As a staff engineer, you will partner with team leads to set the technical direction of the team. This will involve keeping tabs on recurring pain points on our platform, potential opportunities that arise across the company, and industry trends. Based on this expertise, you will help decide which tracks of work our team pursues. You will be responsible for the design of larger projects and will mentor junior teammates on designing smaller projects. This is a full time role reporting to the Senior Engineering Manager." Location paragraph: "We prioritize candidates based within commutable distance of Etsy’s Brooklyn Office. Depending on proximity, we ask team members to come in once or twice per week. Remote candidates outside commutable distance may be considered on a case‑by‑case basis, with the expectation of occasional travel to the office." Responsibilities list items: - Build and maintain software written in PHP - Evolve the OpenAPI platform by identifying areas of friction and implementing features that can measurably improve Developer Experience - Partner with product engineering teams to build and roll out new features - Debug hairy issues spanning multiple systems to determine the root cause and either route it to the appropriate owner or fix yourself - Collaborate with cross‑functional partners (product, analytics, research, etc.) to determine the highest impact projects that align with our team’s strategy - Work with teammates and other subject matter experts as necessary to scope out new platform projects and break them down into multiple stages for delivery, identifying and resolving architectural trade‑offs - Write high quality code and mentor your teammates to do the same through PR reviews, pairing, and general mentoring - Steer the technical direction of the team, from which projects we work on to which team processes we follow Requirements list: - Experience with object‑oriented software languages (the majority of work is developed in PHP) - Experience building and maintaining REST APIs, especially managing breaking changes, and related technical capabilities - Experience using observability tools to monitor API usage and related metrics, such as Grafana, HoneyComb, or Google Cloud Logging - Experience working with AI Agents and related tools, like MCP servers and skills Qualifications list: - A strong sense of ownership for the platform - The ability to think critically and independently to ensure we are building the right things in the right way - Close attention to detail, with the ability to translate business requirements to production‑ready code - Strong communication that adapts to technical and non‑technical audiences - Curiosity and ability to learn autonomously Benefits list: - Equity package - Annual performance bonus - Competitive benefits that support you and your family Pay paragraph: "Base salary is determined by your location, skills, and experience. Etsy uses two geographic pay zones: Geo‑1 (New York City metropolitan area, San Francisco Bay Area, and Seattle metropolitan area) with a salary range of $197,000 – $267,000 USD annually; Geo‑2 (all other U.S. locations) with a salary range of $178,000 – $240,000 USD annually." Make sure to use proper HTML escaping for $? Not needed. Now