Senior Software Engineer II (AI Native)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. The posting includes: description (About the role), responsibilities (Accountabilities), requirements (Requirements), benefits (Benefits). No explicit Pay or Schedule details. So we should not include Pay or Schedule sections. Also maybe Skills? The posting mentions technologies but could be part of Requirements. We could have a Skills section if we want but not required. The instruction: prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Benefits. Possibly Qualifications? The Requirements includes qualifications like degree, experience. Could combine. We'll output sections: About the role (the initial paragraph), Responsibilities (Accountabilities), Requirements (Requirements), Benefits (Benefits). Use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove "Our partner is looking for a Senior Software Engineer II (AI Native) based in United States ." Actually that is part of description; we keep it but maybe we can incorporate into About the role. The job title is already shown on page, we should not repeat as heading. So we can start with a paragraph describing role.
We need to ensure we don't include Job ID etc.
Let's extract content:
About the role: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Software Engineer II (AI Native) based in United States . This is a senior full-stack engineering role focused on building technology for meaningful, large-scale consumer experiences. You’ll initially work on products supporting aging adults who want to remain independent while staying connected with their families. The role combines backend engineering, native mobile development, cloud technologies, and AI-native development practices. You’ll own features end to end, from architecture and implementation through production operations, on-call, and measurable member impact. You’ll also help define how AI can transform engineering workflows, from ideation and coding to testing, reviews, and iteration. The environment is remote-first, highly collaborative, and designed around experimentation, technical ownership, and continuous improvement. As priorities evolve, you may also help extend successful product and engineering patterns into connected devices and pet-focused experiences."
That's the prose.
Responsibilities (Accountabilities): list bullet points:
- Design, build, and operate end-to-end product features across backend services, APIs, and native iOS and Android experiences.
- Work across Java, Spring Boot, Kafka, Kafka Streams, AWS, Swift, Kotlin, and related cloud-native technologies as required by the product.
- Use AI coding assistants and agentic workflows as first-class engineering tools for analysis, specification, implementation, testing, refactoring, codebase navigation, and documentation.
- Help establish and document AI-native engineering practices, creating playbooks and workflows that can be adopted across the wider engineering organization.
- Collaborate closely with product managers, designers, and platform engineers to turn complex user needs into reliable, scalable, and accessible solutions.
- Own the complete lifecycle of the systems and features you build, from initial implementation through production monitoring, incident response, and on-call support.
- Contribute to architectural decisions, technical standards, code reviews, and continuous improvement initiatives.
- Apply AI-assisted development techniques to increase engineering leverage while maintaining strong quality, security, reliability, and accountability standards.
- Mentor other engineers and share effective AI workflows, prompting strategies, development practices, and technical approaches.
- Monitor and improve performance, reliability, accessibility, and overall quality for the experiences you own.
- Adapt successful technical and product patterns to support additional customer segments and emerging product priorities as the team evolves.
Requirements: list bullet points:
- 5+ years of professional experience building and operating high-quality, consumer-scale software or services.
- At least 1 year of hands-on experience prompting, evaluating, and building with large language models or AI-based development technologies.
- Strong full-stack capabilities spanning backend services and native mobile development, with experience in iOS and/or Android and the ability to move comfortably across the technology stack.
- Experience with technologies such as Java, Spring Boot, Kafka, Kafka Streams, AWS, Swift, Kotlin, or comparable modern backend, cloud, and mobile technologies.
- Deep understanding of agentic development workflows, prompt engineering, context management, and MCP/function calling.
- Demonstrated ability to use AI tooling as a substantive engineering partner rather than solely for autocomplete, research, or basic assistance.
- Strong ownership mindset, with the ability to identify problems independently and follow solutions through development, production, and measurable customer impact.
- Strong communication and collaboration skills, with the ability to work effectively with product, design, platform, and engineering teams.
- Interest in defining and improving AI-native engineering practices and helping teammates adopt effective AI-assisted workflows.
- Strong empathy for end users and the ability to translate real human needs into thoughtful technical solutions.
- Experience with performance, reliability, accessibility, incident response, and production operations.
- Bachelor's degree in a technical field or equivalent professional experience.
Benefits: list bullet points:
- Fully remote work opportunity for candidates based in Canada or the United States, subject to applicable hiring requirements.
- Canadian salary range of $171,500–$201,000 CAD for candidates based in Canada.
- Total compensation includes equity in the form of Restricted Stock Units (RSUs), alongside a comprehensive benefits package.
- Medical, dental, and vision coverage, plus life and disability benefits and supplemental medical and dental plans for Canadian employees.
- RRSP with DPSP plan for Canadian employees.
- Paid parental leave.
- Mental Wellness Program and Employee Assistance Program (EAP).
- Flexible paid time off, company-wide holidays, and summer and winter shutdown periods.
- Learning and development programs to support ongoing professional growth.
- Equipment, tools, and reimbursement support for an effective remote working environment.
- Free membership benefits and connected-device products.
- Remote-first flexibility with a distributed workforce.
- Opportunities to work with modern AI technologies and help shape AI-native engineering practices.
- Significant ownership over end-to-end product development and the opportunity to work on products serving large-scale consumer audiences.
- An inclusive environment that values diverse perspectives, direct and respectful communication, continuous improvement, and customer-focused product development.
We should not include Pay or Schedule sections because no explicit pay schedule beyond salary range for Canada; but that is a pay detail. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state salary range for Canada, which is pay info. So we could include a Pay section? However they said prefer few substantive sections; we already have Benefits section that includes salary range. Could we keep salary range inside Benefits? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid putting pay info inside Benefits. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can have Benefits section (since posting states benefits). Pay section would be separate; we should not create a Pay section unless posting explicitly states pay details separate from benefits. It does state salary range, but that's still pay. However we could incorporate salary range into Benefits as a bullet. That seems acceptable and avoids creating a separate Pay section. The instruction: "Prefer a few substantive sections over many thin ones." So we keep Benefits only.
We must not include any boilerplate like "This position is listed on behalf of a partner company..." Actually that is part of description; we keep it.
We must not include "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc.
Now produce HTML fragment:
About the role
... paragraph ...
Responsibilities
- ... each bullet ...
Requirements
- ... each bullet ...
Benefits
- ... each bullet ...
Make sure to preserve all details exactly as in posting. Need to ensure no stray spaces or formatting issues.
Let's craft the About the role paragraph: combine sentences.
"This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Software Engineer II (AI Native) based in United States. This is a senior full-stack engineering role focused on building technology for meaningful, large-scale consumer experiences. You’ll initially work on products supporting aging adults who want to remain independent while staying connected with their families. The role combines backend engineering, native mobile development, cloud technologies, and AI-native development practices. You’ll own features end to end, from architecture and implementation through production operations, on-call, and measurable member impact. You’ll also help define how AI can transform engineering workflows, from ideation and coding to testing, reviews, and iteration. The environment is remote-first, highly collaborative, and designed around experimentation, technical ownership, and continuous improvement. As priorities evolve, you may also help extend successful product and engineering patterns into connected devices and pet-focused experiences."
Make sure punctuation correct.
Now Responsibilities bullets: copy exactly as given, preserving punctuation.
Check each bullet:
- Design, build, and operate end-to-end product features across backend services, APIs, and native iOS and Android experiences.
- Work across Java, Spring Boot, Kafka, Kafka Streams, AWS, Swift, Kotlin, and related cloud-native technologies as required by the product.
- Use AI coding assistants and agentic workflows as first-class engineering tools for analysis, specification, implementation, testing, refactoring, codebase navigation, and documentation.
- Help establish and document AI-native engineering practices, creating playbooks and workflows that can be adopted across the wider engineering organization.
- Collaborate closely with product managers, designers, and platform engineers to turn complex user needs into reliable, scalable, and accessible solutions.
- Own the complete lifecycle of the systems and features you build, from initial implementation through production monitoring, incident response, and on-call support.
- Contribute to architectural decisions, technical standards, code reviews, and continuous improvement initiatives.
- Apply AI-assisted development techniques to increase engineering leverage while maintaining strong quality, security, reliability, and accountability standards.
- Mentor other engineers and share effective AI workflows, prompting strategies, development practices, and technical approaches.
- Monitor and improve performance, reliability, accessibility, and overall quality for the experiences you own.
- Adapt successful technical and product patterns to support additional customer segments and emerging product priorities as the team evolves.
Now Requirements bullets:
- 5+ years of professional experience building and operating high-quality, consumer-scale software or services.
- At least 1 year of hands-on experience prompting, evaluating, and building with large language models or AI-based development technologies.
- Strong full-stack capabilities spanning backend services and native mobile development, with experience in iOS and/or Android and the ability to move comfortably across the technology stack.
- Experience with technologies such as Java, Spring Boot, Kafka, Kafka Streams, AWS, Swift, Kotlin, or comparable modern backend, cloud, and mobile technologies.
- Deep understanding of agentic development workflows, prompt engineering, context management, and MCP/function calling.
- Demonstrated ability to use AI tooling as a substantive engineering partner rather than solely for autocomplete, research, or basic assistance.
- Strong ownership mindset, with the ability to identify problems independently and follow solutions through development, production, and measurable customer impact.
- Strong communication and collaboration skills, with the ability to work effectively with product, design, platform, and engineering teams.
- Interest in defining and improving AI-native engineering practices and helping teammates adopt effective AI-assisted workflows.
- Strong empathy for end users and the ability to translate real human needs into thoughtful technical solutions.
- Experience with performance, reliability, accessibility, incident response, and
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove "Our partner is looking for a Senior Software Engineer II (AI Native) based in United States ." Actually that is part of description; we keep it but maybe we can incorporate into About the role. The job title is already shown on page, we should not repeat as heading. So we can start with a paragraph describing role. We need to ensure we don't include Job ID etc. Let's extract content: About the role: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Software Engineer II (AI Native) based in United States . This is a senior full-stack engineering role focused on building technology for meaningful, large-scale consumer experiences. You’ll initially work on products supporting aging adults who want to remain independent while staying connected with their families. The role combines backend engineering, native mobile development, cloud technologies, and AI-native development practices. You’ll own features end to end, from architecture and implementation through production operations, on-call, and measurable member impact. You’ll also help define how AI can transform engineering workflows, from ideation and coding to testing, reviews, and iteration. The environment is remote-first, highly collaborative, and designed around experimentation, technical ownership, and continuous improvement. As priorities evolve, you may also help extend successful product and engineering patterns into connected devices and pet-focused experiences." That's the prose. Responsibilities (Accountabilities): list bullet points: - Design, build, and operate end-to-end product features across backend services, APIs, and native iOS and Android experiences. - Work across Java, Spring Boot, Kafka, Kafka Streams, AWS, Swift, Kotlin, and related cloud-native technologies as required by the product. - Use AI coding assistants and agentic workflows as first-class engineering tools for analysis, specification, implementation, testing, refactoring, codebase navigation, and documentation. - Help establish and document AI-native engineering practices, creating playbooks and workflows that can be adopted across the wider engineering organization. - Collaborate closely with product managers, designers, and platform engineers to turn complex user needs into reliable, scalable, and accessible solutions. - Own the complete lifecycle of the systems and features you build, from initial implementation through production monitoring, incident response, and on-call support. - Contribute to architectural decisions, technical standards, code reviews, and continuous improvement initiatives. - Apply AI-assisted development techniques to increase engineering leverage while maintaining strong quality, security, reliability, and accountability standards. - Mentor other engineers and share effective AI workflows, prompting strategies, development practices, and technical approaches. - Monitor and improve performance, reliability, accessibility, and overall quality for the experiences you own. - Adapt successful technical and product patterns to support additional customer segments and emerging product priorities as the team evolves. Requirements: list bullet points: - 5+ years of professional experience building and operating high-quality, consumer-scale software or services. - At least 1 year of hands-on experience prompting, evaluating, and building with large language models or AI-based development technologies. - Strong full-stack capabilities spanning backend services and native mobile development, with experience in iOS and/or Android and the ability to move comfortably across the technology stack. - Experience with technologies such as Java, Spring Boot, Kafka, Kafka Streams, AWS, Swift, Kotlin, or comparable modern backend, cloud, and mobile technologies. - Deep understanding of agentic development workflows, prompt engineering, context management, and MCP/function calling. - Demonstrated ability to use AI tooling as a substantive engineering partner rather than solely for autocomplete, research, or basic assistance. - Strong ownership mindset, with the ability to identify problems independently and follow solutions through development, production, and measurable customer impact. - Strong communication and collaboration skills, with the ability to work effectively with product, design, platform, and engineering teams. - Interest in defining and improving AI-native engineering practices and helping teammates adopt effective AI-assisted workflows. - Strong empathy for end users and the ability to translate real human needs into thoughtful technical solutions. - Experience with performance, reliability, accessibility, incident response, and production operations. - Bachelor's degree in a technical field or equivalent professional experience. Benefits: list bullet points: - Fully remote work opportunity for candidates based in Canada or the United States, subject to applicable hiring requirements. - Canadian salary range of $171,500–$201,000 CAD for candidates based in Canada. - Total compensation includes equity in the form of Restricted Stock Units (RSUs), alongside a comprehensive benefits package. - Medical, dental, and vision coverage, plus life and disability benefits and supplemental medical and dental plans for Canadian employees. - RRSP with DPSP plan for Canadian employees. - Paid parental leave. - Mental Wellness Program and Employee Assistance Program (EAP). - Flexible paid time off, company-wide holidays, and summer and winter shutdown periods. - Learning and development programs to support ongoing professional growth. - Equipment, tools, and reimbursement support for an effective remote working environment. - Free membership benefits and connected-device products. - Remote-first flexibility with a distributed workforce. - Opportunities to work with modern AI technologies and help shape AI-native engineering practices. - Significant ownership over end-to-end product development and the opportunity to work on products serving large-scale consumer audiences. - An inclusive environment that values diverse perspectives, direct and respectful communication, continuous improvement, and customer-focused product development. We should not include Pay or Schedule sections because no explicit pay schedule beyond salary range for Canada; but that is a pay detail. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state salary range for Canada, which is pay info. So we could include a Pay section? However they said prefer few substantive sections; we already have Benefits section that includes salary range. Could we keep salary range inside Benefits? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid putting pay info inside Benefits. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can have Benefits section (since posting states benefits). Pay section would be separate; we should not create a Pay section unless posting explicitly states pay details separate from benefits. It does state salary range, but that's still pay. However we could incorporate salary range into Benefits as a bullet. That seems acceptable and avoids creating a separate Pay section. The instruction: "Prefer a few substantive sections over many thin ones." So we keep Benefits only. We must not include any boilerplate like "This position is listed on behalf of a partner company..." Actually that is part of description; we keep it. We must not include "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Now produce HTML fragment:
About the role
... paragraph ...
Responsibilities
- ... each bullet ...
Requirements
- ... each bullet ...
Benefits
- ... each bullet ...