Staff Software Engineer, Agentic AI
for section headings, - for lists,
for prose.
We need to decide which sections to include.
Potential sections:
- About the role (prose)
- Responsibilities (list)
- Qualifications (list)
- Skills (list) maybe combine with Qualifications? But we have both qualifications and skills; we could make one "Requirements" section that includes both qualifications and skills. However the instruction says use headings like Requirements, Qualifications, Skills. We can include multiple if they have content.
We need to avoid thin sections. Let's see if we can split meaningfully.
Qualifications: Strong background in building core components for high scale compute and data distributed systems; 8+ years experience of building distributed systems, and/or foundational cloud services at scale; interest in working with Python, Go, Java; proven success in designing, writing, testing, debugging, performance tuning; strong grip on foundational CS; maintaining distributed/highly concurrent software in large code bases; track record of identifying problems, implementing solutions, delivering complex projects in distributed systems or databases; experience leading 15-20 people projects involving distributed systems infrastructure from conception to successful delivery; good verbal and written technical communication skills, desire to collaborate with colleagues.
Skills: Bonus points for experience with containerization and orchestration platforms (e.g. Kubernetes) and AI frameworks and tools; Be a force multiplier in our software development process. Enable teams to deliver great products through leadership and technical contributions; Eager to learn, with a strong technical background.
But some of those are more like qualities. Could be part of Qualifications.
Given instruction to prefer few substantive sections over many thin ones, maybe combine Qualifications and Skills into one "Requirements" section.
But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with real content.
We have:
- About the role: yes.
- Responsibilities: yes.
- Requirements: we could include qualifications and skills combined.
- Benefits: yes.
- Pay: yes.
- Schedule: yes (hybrid/in-office, NYC area).
We could omit Qualifications and Skills separate to avoid thin sections.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
Now we need to extract prose and list items.
About the role: combine the initial paragraph(s) into a single
. Should we split? Probably one
covering all.
Responsibilities: list items:
- Provide technical leadership to teams developing cutting edge technologies related to enabling deployment at scale of AI applications.
- Take on challenging, high-visibility projects that improve and enhance the performance, scalability, and reliability of the distributed systems infrastructure for the new product.
- Work closely with product management, product engineering, product design peers as well as other teams within the company to define the first version and future evolution of the service.
- Design, build and deliver well-tested core pieces of the platform in collaboration with other vested parties.
- Contribute to shaping architecture, code reviews and development practices, developer experience as the teams and product grow.
- Mentor fellow engineers and assume ownership and accountability of projects.
We need to ensure we didn't miss any.
Also maybe "provide technical direction and implement core parts of a new platform" is part of About the role.
Now Requirements: combine qualifications and skills.
List items:
- Strong background in building core components for high scale compute and data distributed systems.
- 8+ years experience of building distributed systems, and/or foundational cloud services at scale.
- Interest in working with Python, Go, and Java.
- Proven success in designing, writing, testing, debugging, performance tuning.
- Strong grasp of foundational computer science concepts.
- Experience maintaining distributed and/or highly concurrent software systems in large, long-lived code bases.
- Track record of identifying problems, implementing solutions, and delivering complex projects in distributed systems or databases.
- Experience leading 15-20 people projects involving distributed systems infrastructure from conception to successful delivery.
- Good verbal and written technical communication skills; desire to collaborate with colleagues.
- Bonus points for experience with containerization and orchestration platforms (e.g., Kubernetes) and AI frameworks and tools.
- Ability to be a force multiplier in the software development process, enabling teams to deliver great products through leadership and technical contributions.
- Eager to learn, with a strong technical background.
We could combine some but fine.
Benefits: list:
- Equity
- Participation in the employee stock purchase program
- Flexible paid time off
- 20 weeks fully-paid gender-neutral parental leave
- Fertility and adoption assistance
- 401(k) plan
- Mental health counseling
- Access to transgender-inclusive health insurance coverage
- Health benefits offerings
Pay: we can put as
with the salary range.
Schedule: hybrid or in-office working models, based in New York City area.
We need to ensure we don't include boilerplate like "We're looking to speak with candidates based in the New York City area for our hybrid or in-office working models." That's schedule.
Now produce HTML.
We need to
for prose. We need to decide which sections to include. Potential sections: - About the role (prose) - Responsibilities (list) - Qualifications (list) - Skills (list) maybe combine with Qualifications? But we have both qualifications and skills; we could make one "Requirements" section that includes both qualifications and skills. However the instruction says use headings like Requirements, Qualifications, Skills. We can include multiple if they have content. We need to avoid thin sections. Let's see if we can split meaningfully. Qualifications: Strong background in building core components for high scale compute and data distributed systems; 8+ years experience of building distributed systems, and/or foundational cloud services at scale; interest in working with Python, Go, Java; proven success in designing, writing, testing, debugging, performance tuning; strong grip on foundational CS; maintaining distributed/highly concurrent software in large code bases; track record of identifying problems, implementing solutions, delivering complex projects in distributed systems or databases; experience leading 15-20 people projects involving distributed systems infrastructure from conception to successful delivery; good verbal and written technical communication skills, desire to collaborate with colleagues. Skills: Bonus points for experience with containerization and orchestration platforms (e.g. Kubernetes) and AI frameworks and tools; Be a force multiplier in our software development process. Enable teams to deliver great products through leadership and technical contributions; Eager to learn, with a strong technical background. But some of those are more like qualities. Could be part of Qualifications. Given instruction to prefer few substantive sections over many thin ones, maybe combine Qualifications and Skills into one "Requirements" section. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with real content. We have: - About the role: yes. - Responsibilities: yes. - Requirements: we could include qualifications and skills combined. - Benefits: yes. - Pay: yes. - Schedule: yes (hybrid/in-office, NYC area). We could omit Qualifications and Skills separate to avoid thin sections. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Now we need to extract prose and list items. About the role: combine the initial paragraph(s) into a single
. Should we split? Probably one
covering all. Responsibilities: list items: - Provide technical leadership to teams developing cutting edge technologies related to enabling deployment at scale of AI applications. - Take on challenging, high-visibility projects that improve and enhance the performance, scalability, and reliability of the distributed systems infrastructure for the new product. - Work closely with product management, product engineering, product design peers as well as other teams within the company to define the first version and future evolution of the service. - Design, build and deliver well-tested core pieces of the platform in collaboration with other vested parties. - Contribute to shaping architecture, code reviews and development practices, developer experience as the teams and product grow. - Mentor fellow engineers and assume ownership and accountability of projects. We need to ensure we didn't miss any. Also maybe "provide technical direction and implement core parts of a new platform" is part of About the role. Now Requirements: combine qualifications and skills. List items: - Strong background in building core components for high scale compute and data distributed systems. - 8+ years experience of building distributed systems, and/or foundational cloud services at scale. - Interest in working with Python, Go, and Java. - Proven success in designing, writing, testing, debugging, performance tuning. - Strong grasp of foundational computer science concepts. - Experience maintaining distributed and/or highly concurrent software systems in large, long-lived code bases. - Track record of identifying problems, implementing solutions, and delivering complex projects in distributed systems or databases. - Experience leading 15-20 people projects involving distributed systems infrastructure from conception to successful delivery. - Good verbal and written technical communication skills; desire to collaborate with colleagues. - Bonus points for experience with containerization and orchestration platforms (e.g., Kubernetes) and AI frameworks and tools. - Ability to be a force multiplier in the software development process, enabling teams to deliver great products through leadership and technical contributions. - Eager to learn, with a strong technical background. We could combine some but fine. Benefits: list: - Equity - Participation in the employee stock purchase program - Flexible paid time off - 20 weeks fully-paid gender-neutral parental leave - Fertility and adoption assistance - 401(k) plan - Mental health counseling - Access to transgender-inclusive health insurance coverage - Health benefits offerings Pay: we can put as
with the salary range. Schedule: hybrid or in-office working models, based in New York City area. We need to ensure we don't include boilerplate like "We're looking to speak with candidates based in the New York City area for our hybrid or in-office working models." That's schedule. Now produce HTML. We need to