Senior Backend Engineer
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to ensure we include all substantive info from the posting, except removed boilerplate.
Let's extract substantive paragraphs:
Intro: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Backend Engineer based in the United States. This remote role offers the opportunity to build and evolve critical backend systems powering a modern insurance platform. You will design, develop, test, and maintain scalable services that support both customer experiences and core business operations. Working across APIs, internal tooling, external integrations, data providers, and distributed systems, you will have a meaningful impact on platform reliability and performance. You will also contribute to architectural decisions and help shape technology practices as the platform evolves. The role combines hands-on engineering with technical mentorship and close collaboration across teams. It is well suited to an experienced backend engineer who enjoys solving complex problems and building reliable systems with real-world impact."
That's prose for About the role.
Responsibilities (Accountabilities): list items:
- Design, build, test, and maintain backend services and core systems that support the insurance platform and customer-facing experiences.
- Collaborate with internal and external partners to develop APIs and services that enable reliable, intuitive user experiences.
- Build and improve internal tooling and APIs that make business and engineering processes more efficient, secure, and scalable.
- Implement systemic improvements that bring existing systems into alignment with evolving architectural goals.
- Develop integrations with external services supporting payments, documents, claims, and other critical business workflows.
- Integrate with data providers to source and process real-time information across areas such as property characteristics and risk profiles.
- Contribute to architectural discussions and important technical decisions, including microservices versus monoliths, deployment approaches, technologies, and engineering policies.
- Drive improvements to business-critical systems with a focus on stability, performance, scalability, and operational reliability.
- Deliver complete systems and features from initial design through implementation and production deployment with limited supervision.
- Provide technical expertise, mentorship, and day-to-day support to other engineers on the team.
- Participate in team rituals and collaboration practices, including daily stand-ups, regular 1:1 meetings, and retrospectives.
Requirements:
- At least 4 years of professional production experience developing backend web applications and services.
- Professional experience using Go in previous engineering roles.
- Strong experience building reliable backend systems and improving business-critical applications for stability, performance, and scalability.
- Demonstrated ability to independently deliver complete systems and projects from start to finish within reasonable timelines.
- Strong understanding of backend architecture, APIs, distributed systems, and modern cloud-based development practices.
- Experience working with databases such as PostgreSQL and familiarity with modern data and infrastructure environments.
- Strong interpersonal and communication skills, including the ability to explain complex technical concepts clearly to non-technical audiences.
- Ability to collaborate effectively with engineers, business stakeholders, external partners, and cross-functional teams.
- A willingness to contribute to architectural and operational decisions and take ownership of technical outcomes.
- Experience with some of the following technologies and tools is relevant: Go, PostgreSQL, Google Cloud, Kubernetes, Cloud Run, Pub/Sub, BigQuery, CloudSQL, Terraform, GitHub, DataDog, CircleCI, Kafka, Airflow, and related cloud/data infrastructure.
- The interview process includes a technical coding challenge in Go.
- Applicants must currently be authorized to work full-time in the United States and must be residing in the United States.
- This position is not eligible for employer-sponsored visa sponsorship now or in the future.
Benefits:
- Budgeted salary range of $145,600–$163,800.
- Full salary range of $145,600–$218,400, with actual compensation determined based on experience, qualifications, skills, and other relevant factors.
- Remote-first work model with a strong focus on flexibility.
- Equity opportunity tied to company growth.
- Comprehensive medical, dental, and vision coverage.
- Life and disability insurance, including voluntary supplemental coverage options.
- Up to 8 weeks (320 hours) of paid parental leave for eligible employees, with additional disability coverage available for birthing parents.
- 401(k) company contribution equal to 3% of gross income, regardless of employee contributions.
- $1,500 upfront home-office setup allowance.
- $75 per month internet stipend.
- $2,000 annual professional development allowance for courses, conferences, and learning resources.
- $50 per month wellness stipend through the “Be Well” program.
- Paid volunteer hours to support community involvement.
- Financial referral rewards for successful employee referrals.
Pay: Already covered in benefits but we need separate Pay section if posting states them. The posting includes salary ranges. We could put Pay section with those ranges. However Benefits section also includes salary range lines; but we should not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits? But they ask to use headings for Benefits, Pay, Schedule. We need to include a section only when posting has real, specific content for it. The posting does have salary info, so Pay section is appropriate. Benefits also have other items. We could separate Pay (salary ranges) and Benefits (other benefits). However the salary ranges also appear in Benefits list; we could keep them in Pay and not repeat in Benefits. But we must preserve all substantive information; we can move salary lines to Pay and keep other benefits in Benefits.
Schedule: Remote-first work model with a strong focus on flexibility. That's schedule/location. Could be Schedule section.
We also have "Remote-first work model with a strong focus on flexibility." Already used.
We need to avoid duplication.
Let's craft sections:
About the role
Intro paragraph(s).
Responsibilities
- ...
Requirements
- ...
Skills
Maybe list of technologies? Could be from requirements: "Experience with some of the following technologies and tools is relevant: Go, PostgreSQL, Google Cloud, Kubernetes, Cloud Run, Pub/Sub, BigQuery, CloudSQL, Terraform, GitHub, DataDog, CircleCI, Kafka, Airflow, and related cloud/data infrastructure." That's a list; we can put in Skills.
Pay
Budgeted salary range of $145,600–$163,800. Full salary range of $145,600–$218,400, with actual compensation determined based on experience, qualifications, skills, and other relevant factors.
Benefits
- Remote-first work model with a strong focus on flexibility.
- Equity opportunity tied to company growth.
- Comprehensive medical, dental, and vision coverage.
- Life and disability insurance, including voluntary supplemental coverage options.
- Up to 8 weeks (320 hours) of paid parental leave for eligible employees, with additional disability coverage available for birthing parents.
- 401(k) company contribution equal to 3% of gross income, regardless of employee contributions.
- $1,500 upfront home-office setup allowance.
- $75 per month internet stipend.
- $2,000 annual professional development allowance for courses, conferences, and learning resources.
- $50 per month wellness stipend through the “Be Well” program.
- Paid volunteer hours to support community involvement.
- Financial referral rewards for successful employee referrals.
Schedule
Remote-first work model with a strong focus on flexibility.
But note we already have Remote-first in Benefits; we might duplicate. Could move remote-first to Schedule only and not include in Benefits. However Benefits also includes other items; we can keep remote-first in Schedule only. The instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Schedule with similar line may be thin. But we need to include Schedule if posting has real specific content. It does: remote-first work model with a strong focus on flexibility. That's schedule/location. We'll put that in Schedule and not duplicate in Benefits.
Thus Benefits list excludes remote-first line.
Check we haven't missed any substantive info: The intro paragraph includes "based in the United States" etc. That's covered.
We also have "This position is listed on behalf of a partner company, who manages all applications and next steps." That's part of About the role.
We also have "Our partner is looking for a Senior Backend Engineer based in the United States." included.
We also have "This remote role offers the opportunity to build and evolve critical backend systems powering a modern insurance platform." included.
We also have "You will design, develop, test, and maintain scalable services that support both customer experiences and core business operations." included.
We also have "Working across APIs, internal tooling, external integrations, data providers, and distributed systems, you will have a meaningful impact on platform reliability and performance." included.
We also have "You will also contribute to architectural decisions and help shape technology practices as the platform evolves." included.
We also have "The role combines hands-on engineering with technical mentorship and close collaboration across teams." included.
We also have "It is well suited to an experienced backend engineer who enjoys solving complex problems and building reliable systems with real-world impact." included.
All good.
Now ensure we didn't include boilerplate: removed "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc.
Now produce HTML fragment only.
Check each section has content.
We'll output:
About the role
...
Responsibilities
...
Requirements
...
Skills
...
(or with list? The instruction: Use
- for any list of duties/requirements/benefits. Skills is a list, so use ul.)
Pay
...
Benefits
...
Schedule
Remote-first work model with a strong focus on flexibility.
Make sure no extra whitespace issues.
Now craft the HTML.
Let's write the About
for prose. We need to ensure we include all substantive info from the posting, except removed boilerplate. Let's extract substantive paragraphs: Intro: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Backend Engineer based in the United States. This remote role offers the opportunity to build and evolve critical backend systems powering a modern insurance platform. You will design, develop, test, and maintain scalable services that support both customer experiences and core business operations. Working across APIs, internal tooling, external integrations, data providers, and distributed systems, you will have a meaningful impact on platform reliability and performance. You will also contribute to architectural decisions and help shape technology practices as the platform evolves. The role combines hands-on engineering with technical mentorship and close collaboration across teams. It is well suited to an experienced backend engineer who enjoys solving complex problems and building reliable systems with real-world impact." That's prose for About the role. Responsibilities (Accountabilities): list items: - Design, build, test, and maintain backend services and core systems that support the insurance platform and customer-facing experiences. - Collaborate with internal and external partners to develop APIs and services that enable reliable, intuitive user experiences. - Build and improve internal tooling and APIs that make business and engineering processes more efficient, secure, and scalable. - Implement systemic improvements that bring existing systems into alignment with evolving architectural goals. - Develop integrations with external services supporting payments, documents, claims, and other critical business workflows. - Integrate with data providers to source and process real-time information across areas such as property characteristics and risk profiles. - Contribute to architectural discussions and important technical decisions, including microservices versus monoliths, deployment approaches, technologies, and engineering policies. - Drive improvements to business-critical systems with a focus on stability, performance, scalability, and operational reliability. - Deliver complete systems and features from initial design through implementation and production deployment with limited supervision. - Provide technical expertise, mentorship, and day-to-day support to other engineers on the team. - Participate in team rituals and collaboration practices, including daily stand-ups, regular 1:1 meetings, and retrospectives. Requirements: - At least 4 years of professional production experience developing backend web applications and services. - Professional experience using Go in previous engineering roles. - Strong experience building reliable backend systems and improving business-critical applications for stability, performance, and scalability. - Demonstrated ability to independently deliver complete systems and projects from start to finish within reasonable timelines. - Strong understanding of backend architecture, APIs, distributed systems, and modern cloud-based development practices. - Experience working with databases such as PostgreSQL and familiarity with modern data and infrastructure environments. - Strong interpersonal and communication skills, including the ability to explain complex technical concepts clearly to non-technical audiences. - Ability to collaborate effectively with engineers, business stakeholders, external partners, and cross-functional teams. - A willingness to contribute to architectural and operational decisions and take ownership of technical outcomes. - Experience with some of the following technologies and tools is relevant: Go, PostgreSQL, Google Cloud, Kubernetes, Cloud Run, Pub/Sub, BigQuery, CloudSQL, Terraform, GitHub, DataDog, CircleCI, Kafka, Airflow, and related cloud/data infrastructure. - The interview process includes a technical coding challenge in Go. - Applicants must currently be authorized to work full-time in the United States and must be residing in the United States. - This position is not eligible for employer-sponsored visa sponsorship now or in the future. Benefits: - Budgeted salary range of $145,600–$163,800. - Full salary range of $145,600–$218,400, with actual compensation determined based on experience, qualifications, skills, and other relevant factors. - Remote-first work model with a strong focus on flexibility. - Equity opportunity tied to company growth. - Comprehensive medical, dental, and vision coverage. - Life and disability insurance, including voluntary supplemental coverage options. - Up to 8 weeks (320 hours) of paid parental leave for eligible employees, with additional disability coverage available for birthing parents. - 401(k) company contribution equal to 3% of gross income, regardless of employee contributions. - $1,500 upfront home-office setup allowance. - $75 per month internet stipend. - $2,000 annual professional development allowance for courses, conferences, and learning resources. - $50 per month wellness stipend through the “Be Well” program. - Paid volunteer hours to support community involvement. - Financial referral rewards for successful employee referrals. Pay: Already covered in benefits but we need separate Pay section if posting states them. The posting includes salary ranges. We could put Pay section with those ranges. However Benefits section also includes salary range lines; but we should not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits? But they ask to use headings for Benefits, Pay, Schedule. We need to include a section only when posting has real, specific content for it. The posting does have salary info, so Pay section is appropriate. Benefits also have other items. We could separate Pay (salary ranges) and Benefits (other benefits). However the salary ranges also appear in Benefits list; we could keep them in Pay and not repeat in Benefits. But we must preserve all substantive information; we can move salary lines to Pay and keep other benefits in Benefits. Schedule: Remote-first work model with a strong focus on flexibility. That's schedule/location. Could be Schedule section. We also have "Remote-first work model with a strong focus on flexibility." Already used. We need to avoid duplication. Let's craft sections:
About the role
Intro paragraph(s).
Responsibilities
- ...
Requirements
- ...
Skills
Maybe list of technologies? Could be from requirements: "Experience with some of the following technologies and tools is relevant: Go, PostgreSQL, Google Cloud, Kubernetes, Cloud Run, Pub/Sub, BigQuery, CloudSQL, Terraform, GitHub, DataDog, CircleCI, Kafka, Airflow, and related cloud/data infrastructure." That's a list; we can put in Skills.Pay
Budgeted salary range of $145,600–$163,800. Full salary range of $145,600–$218,400, with actual compensation determined based on experience, qualifications, skills, and other relevant factors.
Benefits
- Remote-first work model with a strong focus on flexibility.
- Equity opportunity tied to company growth.
- Comprehensive medical, dental, and vision coverage.
- Life and disability insurance, including voluntary supplemental coverage options.
- Up to 8 weeks (320 hours) of paid parental leave for eligible employees, with additional disability coverage available for birthing parents.
- 401(k) company contribution equal to 3% of gross income, regardless of employee contributions.
- $1,500 upfront home-office setup allowance.
- $75 per month internet stipend.
- $2,000 annual professional development allowance for courses, conferences, and learning resources.
- $50 per month wellness stipend through the “Be Well” program.
- Paid volunteer hours to support community involvement.
- Financial referral rewards for successful employee referrals.
Schedule
Remote-first work model with a strong focus on flexibility.
But note we already have Remote-first in Benefits; we might duplicate. Could move remote-first to Schedule only and not include in Benefits. However Benefits also includes other items; we can keep remote-first in Schedule only. The instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Schedule with similar line may be thin. But we need to include Schedule if posting has real specific content. It does: remote-first work model with a strong focus on flexibility. That's schedule/location. We'll put that in Schedule and not duplicate in Benefits. Thus Benefits list excludes remote-first line. Check we haven't missed any substantive info: The intro paragraph includes "based in the United States" etc. That's covered. We also have "This position is listed on behalf of a partner company, who manages all applications and next steps." That's part of About the role. We also have "Our partner is looking for a Senior Backend Engineer based in the United States." included. We also have "This remote role offers the opportunity to build and evolve critical backend systems powering a modern insurance platform." included. We also have "You will design, develop, test, and maintain scalable services that support both customer experiences and core business operations." included. We also have "Working across APIs, internal tooling, external integrations, data providers, and distributed systems, you will have a meaningful impact on platform reliability and performance." included. We also have "You will also contribute to architectural decisions and help shape technology practices as the platform evolves." included. We also have "The role combines hands-on engineering with technical mentorship and close collaboration across teams." included. We also have "It is well suited to an experienced backend engineer who enjoys solving complex problems and building reliable systems with real-world impact." included. All good. Now ensure we didn't include boilerplate: removed "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Now produce HTML fragment only. Check each section has content. We'll output:About the role
...
Responsibilities
- ...
Requirements
- ...
Skills
- ...
with list? The instruction: Use
- for any list of duties/requirements/benefits. Skills is a list, so use ul.)
Pay
...
Benefits
- ...
Schedule
Remote-first work model with a strong focus on flexibility.
Make sure no extra whitespace issues. Now craft the HTML. Let's write the About