Staff Engineer, AI Native
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines (the intro appears twice). We need to keep the content: description of SEPS, mission, etc. That is part of "About the role" maybe. The posting includes "Join the Sony Engagement Platform Services (SEPS) Team..." repeated twice. We'll keep one copy.
We need sections: maybe "About the role" (intro), "Responsibilities", "Minimum Qualifications", "Preferred Qualifications", "Benefits", "Pay". Also maybe "Qualifications"? But we have Minimum and Preferred. Could combine? But spec says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role", "Responsibilities", "Minimum Qualifications", "Preferred Qualifications", "Benefits", "Pay". Ensure we don't create sections with filler.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, intro paragraph(s): combine the description: "Join the Sony Engagement Platform Services (SEPS) Team, where innovation meets collaboration in the dynamic world of digital engagement. At SEPS, we are building the next-generation platform that powers how fans connect with the content—and the creators—they love. Our mission is to unlock meaningful, data-driven engagement across Sony’s entertainment ecosystem, from games and anime to music, film, and live experiences—empowering both internal teams and external partners to build at scale. The goal is to create a world-class engagement platform that not only enhances existing revenue streams but also drives new opportunities through a robust ecosystem of partners and creators. By decoupling application development from platform services, we empower our teams to deliver exceptional solutions with agility and efficiency. If you are passionate about shaping the future of digital engagement and want to be part of a vibrant community that values creativity and collaboration, we invite you to explore the exciting opportunities within our team. Together, we will shape the future of fan experiences and define the foundation for what’s possible in the realm of engagement."
That's the About the role.
Then Responsibilities: list bullet points from responsibilities section.
We need to extract each responsibility line.
Responsibilities list:
- Architect, design and develop RESTful API Endpoints, ensuring high performance, scalability and maintainability.
- Collaborate closely with front-end engineers to build dynamic, responsive, and user-centric web applications that deliver seamless user experiences.
- Define robust data models and database schemas, and manage relational or NoSQL databases with a strong emphasis on data integrity and performance optimization.
- Direct and govern AI coding agents across the delivery lifecycle, setting context, reviewing agent-generated output, and enforcing SEPS delivery standards at every gate.
- Design and maintain agent workflows using agentic coding tools (Claude Code, Cursor, Copilot) and the AI-native development framework, ensuring structured, auditable, and high-quality delivery.
- Configure and maintain prompt engineering patterns, structured output schemas, with rules and guardrails to align agent behavior with SEPS platform standards.
- Trace, debug, and triage agent tool calls, prompt failures, and unexpected outputs, maintaining visibility into AI-assisted delivery at every stage.
- Create and maintain clear, comprehensive documentation for application architecture, design, configuration, and ongoing maintenance.
- Provide accurate task estimations and delivery timelines, contributing to effective sprint planning and execution.
- Participate in the on-call rotation, responding promptly to production issues and ensuring system stability and uptime.
- Mentor and support junior engineers, fostering a culture of AI-native ways of working, learning, and continuous improvement.
Make
- for each.
Minimum Qualifications: list bullet points.
Minimum Qualifications list:
- 8+ years professional experience working with medium/large complex code bases
- Experience in Full Stack development
- Experience with one or more of the following programming languages: Java, Go, or Python
- Experience in REST API design and implementation
- Highly Proficient in HTML, CSS, the JavaScript ecosystem and familiarity with popular frameworks like React, Angular, Ember, Jest, Babel, and TypeScript
- Knowledgeable in UI/UX design principles
- Demonstrated proficiency with AI-native coding tools (Claude Code, Cursor, or GitHub Copilot) as a primary delivery vehicle, not a productivity add-on
- Working knowledge of prompt engineering, context management, and structured output patterns
- Familiarity with agent development concepts, tool use, function calling, approvals, and workflow chaining
- Awareness of secure AI coding practices including prompt injection, sandbox basics, and access control
- Strong communication and interpersonal skills
- Desire to collaborate and to develop strong and positive team relationships
- Attention to detail, organizational skills, a strong work ethic and the ability to work independently.
Preferred Qualifications list:
- Bachelor’s degree in Computer Science or related field, or at least three years of proven experience in lieu of a degree
- Demonstrated ability to write clean, maintainable, and well-documented code.
- Database management, cloud technologies (AWS), and containerization (Docker, Kubernetes)
- Knowledge of React best practices
- Familiarity with DevOps tools and practices, including CI/CD pipelines
- Automated deployment tools (e.g. Terraform, Ansible, Jenkins)
- Experience with the AI-native development framework (e.g. BMad Method)
- Familiarity with MCP, A2A concepts, tool-connection patterns, and agent skill configuration
- Eval basics, writing test cases, applying LLM-as-judge concepts, and defining acceptance criteria for AI-generated output
- Experience tracing and debugging prompt chains, tool calls, and agent failures
- Understanding of hallucination reduction techniques, prompt caching, and model fallback strategies
- Excellent problem-solving skills and attention to detail
- Experience with Agile development methodologies such as SAFe, Scrum
Benefits: we have a paragraph describing benefits. We'll put as
maybe with list? The benefits description includes many items; we could list them as
- . The instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as list.
Benefits list items:
- Comprehensive medical, prescription drug, dental, and vision coverage with coverage for spouses/domestic partners and child dependents, including access to a Health Savings Account (HSA) and Flexible Spending Account (FSA)
- Employee assistance plan and comprehensive behavioral health benefits
- Fertility benefits, including surrogacy, and adoption assistance programs
- Basic and supplemental life insurance for employees as well as supplemental life insurance coverage for their spouses/domestic partners and children
- Voluntary benefits such as group legal, identity theft protection, accident, and hospital indemnity insurance
- Short-term & long-term disability plans
- Up to 12 weeks of paid parental and caregiver leave
- 401(k) Plan with pre-tax, Roth, and after-tax options and company match with immediate vesting
- Education assistance and student loan programs
- Other Programs: Time off to include vacation, paid holidays, sick leave, Summer Fridays (early release), and a winter break between Christmas and New Year’s Day (based on business needs)
- Referral bonuses (subject to eligibility)
- Matching gift program
- A wide variety of employee business resource groups (EBRGs)
- Special discounts on Sony products, offered exclusively to Sony employees
- Employee stock purchase plan (Sony covers commissions and fees for your Sony stock purchases made through after-tax payroll deductions)
Pay: we have salary range and bonus target.
We need to include Pay section with that info. Not to include filler like "commensurate with experience". We have actual numbers.
Pay: The anticipated annual base salary for this role is $220,000–$240,000 for the Los Angeles, CA office location and $200,000–$220,000 for San Diego, CA. In addition to the annual base salary, this role has an annual bonus target of 17%. This range does not include any other compensation components or other benefits that an individual may be eligible for. The actual base salary offered depends on a variety of factors, which may include as applicable, the qualifications of the individual applicant for the position, years of relevant experience, specific and unique skills, level of education attained, certifications or other professional licenses held, and the location in which the applicant lives and/or from which they will be performing the job.
We'll put that as
maybe.
We should not include sections like Schedule (not present). Also we should not include "Requirements" heading if we have Minimum and Preferred Qualifications; but spec says we can use Requirements heading. However we have Minimum and Preferred; we could combine into Requirements but better to follow spec: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we have Minimum and Preferred Qualifications; we could put them under "Requirements" and "Preferred Qualifications"? Actually "Qualifications" heading could be used for both minimum and preferred? The spec says use headings for those sections; we can decide to use "Minimum Qualifications" and "Preferred Qualifications" as subheadings? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those exact headings? It says e.g., not exclusive. So we can use those headings. We have content for About the role, Responsibilities, Requirements (maybe combine minimum qualifications), Qualifications (maybe preferred?), Benefits, Pay. We don't have Skills separate; we could embed skills in qualifications. But we can also create a Skills section if we have skill list. However we have many skill items in qualifications; better to put them under Requirements and Qualifications.
Let's decide: Use "About the role", "Responsibilities", "Requirements", "Qualifications", "Benefits", "Pay". Under Requirements we put Minimum Qualifications. Under Qualifications we put Preferred Qualifications. That seems logical.
We must not repeat job title as heading. Good.
Now ensure we don't include boilerplate like "SCA offers benefits-eligible employees..." etc. We already captured benefits list; we should not include the introductory sentence about SCA offers benefits-eligible employees... but we can keep it as part of benefits description? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits intro sentence is not boilerplate; it's part of benefits description. Could keep but we already list benefits; we could keep a short preamble
then list. But we can just list benefits; the preamble may be considered filler but not boilerplate. Safer to include a brief
describing benefits program then list.
We'll include a
for benefits intro: "SCA offers benefits-eligible employees (generally regular employees scheduled to work 20 or more hours a week) a comprehensive benefits program that offers coverage and support for employees and their family’s physical, emotional, and financial well-being." Then list.
Similarly for Pay we could include a
with the salary details.
Now produce HTML.
Let's craft:
About the role
Join the Sony Engagement Platform Services (SEPS) Team, where innovation meets collaboration in the dynamic world of digital engagement. At SEPS, we are building the next-generation platform that powers how fans connect with the content—and the creators—they love. Our mission is to unlock meaningful, data-driven engagement across Sony’s entertainment ecosystem, from games and anime
for prose. We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines (the intro appears twice). We need to keep the content: description of SEPS, mission, etc. That is part of "About the role" maybe. The posting includes "Join the Sony Engagement Platform Services (SEPS) Team..." repeated twice. We'll keep one copy. We need sections: maybe "About the role" (intro), "Responsibilities", "Minimum Qualifications", "Preferred Qualifications", "Benefits", "Pay". Also maybe "Qualifications"? But we have Minimum and Preferred. Could combine? But spec says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role", "Responsibilities", "Minimum Qualifications", "Preferred Qualifications", "Benefits", "Pay". Ensure we don't create sections with filler. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, intro paragraph(s): combine the description: "Join the Sony Engagement Platform Services (SEPS) Team, where innovation meets collaboration in the dynamic world of digital engagement. At SEPS, we are building the next-generation platform that powers how fans connect with the content—and the creators—they love. Our mission is to unlock meaningful, data-driven engagement across Sony’s entertainment ecosystem, from games and anime to music, film, and live experiences—empowering both internal teams and external partners to build at scale. The goal is to create a world-class engagement platform that not only enhances existing revenue streams but also drives new opportunities through a robust ecosystem of partners and creators. By decoupling application development from platform services, we empower our teams to deliver exceptional solutions with agility and efficiency. If you are passionate about shaping the future of digital engagement and want to be part of a vibrant community that values creativity and collaboration, we invite you to explore the exciting opportunities within our team. Together, we will shape the future of fan experiences and define the foundation for what’s possible in the realm of engagement." That's the About the role. Then Responsibilities: list bullet points from responsibilities section. We need to extract each responsibility line. Responsibilities list: - Architect, design and develop RESTful API Endpoints, ensuring high performance, scalability and maintainability. - Collaborate closely with front-end engineers to build dynamic, responsive, and user-centric web applications that deliver seamless user experiences. - Define robust data models and database schemas, and manage relational or NoSQL databases with a strong emphasis on data integrity and performance optimization. - Direct and govern AI coding agents across the delivery lifecycle, setting context, reviewing agent-generated output, and enforcing SEPS delivery standards at every gate. - Design and maintain agent workflows using agentic coding tools (Claude Code, Cursor, Copilot) and the AI-native development framework, ensuring structured, auditable, and high-quality delivery. - Configure and maintain prompt engineering patterns, structured output schemas, with rules and guardrails to align agent behavior with SEPS platform standards. - Trace, debug, and triage agent tool calls, prompt failures, and unexpected outputs, maintaining visibility into AI-assisted delivery at every stage. - Create and maintain clear, comprehensive documentation for application architecture, design, configuration, and ongoing maintenance. - Provide accurate task estimations and delivery timelines, contributing to effective sprint planning and execution. - Participate in the on-call rotation, responding promptly to production issues and ensuring system stability and uptime. - Mentor and support junior engineers, fostering a culture of AI-native ways of working, learning, and continuous improvement. Make
- for each.
Minimum Qualifications: list bullet points.
Minimum Qualifications list:
- 8+ years professional experience working with medium/large complex code bases
- Experience in Full Stack development
- Experience with one or more of the following programming languages: Java, Go, or Python
- Experience in REST API design and implementation
- Highly Proficient in HTML, CSS, the JavaScript ecosystem and familiarity with popular frameworks like React, Angular, Ember, Jest, Babel, and TypeScript
- Knowledgeable in UI/UX design principles
- Demonstrated proficiency with AI-native coding tools (Claude Code, Cursor, or GitHub Copilot) as a primary delivery vehicle, not a productivity add-on
- Working knowledge of prompt engineering, context management, and structured output patterns
- Familiarity with agent development concepts, tool use, function calling, approvals, and workflow chaining
- Awareness of secure AI coding practices including prompt injection, sandbox basics, and access control
- Strong communication and interpersonal skills
- Desire to collaborate and to develop strong and positive team relationships
- Attention to detail, organizational skills, a strong work ethic and the ability to work independently.
Preferred Qualifications list:
- Bachelor’s degree in Computer Science or related field, or at least three years of proven experience in lieu of a degree
- Demonstrated ability to write clean, maintainable, and well-documented code.
- Database management, cloud technologies (AWS), and containerization (Docker, Kubernetes)
- Knowledge of React best practices
- Familiarity with DevOps tools and practices, including CI/CD pipelines
- Automated deployment tools (e.g. Terraform, Ansible, Jenkins)
- Experience with the AI-native development framework (e.g. BMad Method)
- Familiarity with MCP, A2A concepts, tool-connection patterns, and agent skill configuration
- Eval basics, writing test cases, applying LLM-as-judge concepts, and defining acceptance criteria for AI-generated output
- Experience tracing and debugging prompt chains, tool calls, and agent failures
- Understanding of hallucination reduction techniques, prompt caching, and model fallback strategies
- Excellent problem-solving skills and attention to detail
- Experience with Agile development methodologies such as SAFe, Scrum
Benefits: we have a paragraph describing benefits. We'll put as
maybe with list? The benefits description includes many items; we could list them as
- . The instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as list.
Benefits list items:
- Comprehensive medical, prescription drug, dental, and vision coverage with coverage for spouses/domestic partners and child dependents, including access to a Health Savings Account (HSA) and Flexible Spending Account (FSA)
- Employee assistance plan and comprehensive behavioral health benefits
- Fertility benefits, including surrogacy, and adoption assistance programs
- Basic and supplemental life insurance for employees as well as supplemental life insurance coverage for their spouses/domestic partners and children
- Voluntary benefits such as group legal, identity theft protection, accident, and hospital indemnity insurance
- Short-term & long-term disability plans
- Up to 12 weeks of paid parental and caregiver leave
- 401(k) Plan with pre-tax, Roth, and after-tax options and company match with immediate vesting
- Education assistance and student loan programs
- Other Programs: Time off to include vacation, paid holidays, sick leave, Summer Fridays (early release), and a winter break between Christmas and New Year’s Day (based on business needs)
- Referral bonuses (subject to eligibility)
- Matching gift program
- A wide variety of employee business resource groups (EBRGs)
- Special discounts on Sony products, offered exclusively to Sony employees
- Employee stock purchase plan (Sony covers commissions and fees for your Sony stock purchases made through after-tax payroll deductions)
Pay: we have salary range and bonus target.
We need to include Pay section with that info. Not to include filler like "commensurate with experience". We have actual numbers.
Pay: The anticipated annual base salary for this role is $220,000–$240,000 for the Los Angeles, CA office location and $200,000–$220,000 for San Diego, CA. In addition to the annual base salary, this role has an annual bonus target of 17%. This range does not include any other compensation components or other benefits that an individual may be eligible for. The actual base salary offered depends on a variety of factors, which may include as applicable, the qualifications of the individual applicant for the position, years of relevant experience, specific and unique skills, level of education attained, certifications or other professional licenses held, and the location in which the applicant lives and/or from which they will be performing the job.
We'll put that as
maybe. We should not include sections like Schedule (not present). Also we should not include "Requirements" heading if we have Minimum and Preferred Qualifications; but spec says we can use Requirements heading. However we have Minimum and Preferred; we could combine into Requirements but better to follow spec: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we have Minimum and Preferred Qualifications; we could put them under "Requirements" and "Preferred Qualifications"? Actually "Qualifications" heading could be used for both minimum and preferred? The spec says use headings for those sections; we can decide to use "Minimum Qualifications" and "Preferred Qualifications" as subheadings? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those exact headings? It says e.g., not exclusive. So we can use those headings. We have content for About the role, Responsibilities, Requirements (maybe combine minimum qualifications), Qualifications (maybe preferred?), Benefits, Pay. We don't have Skills separate; we could embed skills in qualifications. But we can also create a Skills section if we have skill list. However we have many skill items in qualifications; better to put them under Requirements and Qualifications. Let's decide: Use "About the role", "Responsibilities", "Requirements", "Qualifications", "Benefits", "Pay". Under Requirements we put Minimum Qualifications. Under Qualifications we put Preferred Qualifications. That seems logical. We must not repeat job title as heading. Good. Now ensure we don't include boilerplate like "SCA offers benefits-eligible employees..." etc. We already captured benefits list; we should not include the introductory sentence about SCA offers benefits-eligible employees... but we can keep it as part of benefits description? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits intro sentence is not boilerplate; it's part of benefits description. Could keep but we already list benefits; we could keep a short preamble
then list. But we can just list benefits; the preamble may be considered filler but not boilerplate. Safer to include a brief
describing benefits program then list. We'll include a
for benefits intro: "SCA offers benefits-eligible employees (generally regular employees scheduled to work 20 or more hours a week) a comprehensive benefits program that offers coverage and support for employees and their family’s physical, emotional, and financial well-being." Then list. Similarly for Pay we could include a
with the salary details. Now produce HTML. Let's craft:
About the role
Join the Sony Engagement Platform Services (SEPS) Team, where innovation meets collaboration in the dynamic world of digital engagement. At SEPS, we are building the next-generation platform that powers how fans connect with the content—and the creators—they love. Our mission is to unlock meaningful, data-driven engagement across Sony’s entertainment ecosystem, from games and anime
- for any list of duties/requirements/benefits. So we should list benefits as list.
Benefits list items:
- Comprehensive medical, prescription drug, dental, and vision coverage with coverage for spouses/domestic partners and child dependents, including access to a Health Savings Account (HSA) and Flexible Spending Account (FSA)
- Employee assistance plan and comprehensive behavioral health benefits
- Fertility benefits, including surrogacy, and adoption assistance programs
- Basic and supplemental life insurance for employees as well as supplemental life insurance coverage for their spouses/domestic partners and children
- Voluntary benefits such as group legal, identity theft protection, accident, and hospital indemnity insurance
- Short-term & long-term disability plans
- Up to 12 weeks of paid parental and caregiver leave
- 401(k) Plan with pre-tax, Roth, and after-tax options and company match with immediate vesting
- Education assistance and student loan programs
- Other Programs: Time off to include vacation, paid holidays, sick leave, Summer Fridays (early release), and a winter break between Christmas and New Year’s Day (based on business needs)
- Referral bonuses (subject to eligibility)
- Matching gift program
- A wide variety of employee business resource groups (EBRGs)
- Special discounts on Sony products, offered exclusively to Sony employees
- Employee stock purchase plan (Sony covers commissions and fees for your Sony stock purchases made through after-tax payroll deductions)
Pay: we have salary range and bonus target.
We need to include Pay section with that info. Not to include filler like "commensurate with experience". We have actual numbers.
Pay: The anticipated annual base salary for this role is $220,000–$240,000 for the Los Angeles, CA office location and $200,000–$220,000 for San Diego, CA. In addition to the annual base salary, this role has an annual bonus target of 17%. This range does not include any other compensation components or other benefits that an individual may be eligible for. The actual base salary offered depends on a variety of factors, which may include as applicable, the qualifications of the individual applicant for the position, years of relevant experience, specific and unique skills, level of education attained, certifications or other professional licenses held, and the location in which the applicant lives and/or from which they will be performing the job.
We'll put that as
- . The instruction: Use