Senior Site Reliability Engineer II
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content.
We have content: About Juniper Square (company overview). Could be considered "About the role"? Actually "About Juniper Square" is company description, not role. But we could be "About the role". There's "About Your Role" heading. So we can have About the role
with that content.
Then responsibilities: "What You’ll Do" list.
Then qualifications: "Qualifications Required" and "Preferred". Could combine into Requirements/Qualifications.
Then benefits: "Benefits Include" list.
Then compensation: "Compensation" includes base salary range. So we need Pay section.
Schedule: not mentioned; we should not create Schedule section.
We must not include boilerplate like EEO etc. Not present.
We must preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We need to include headings as
. For each section we include heading then content.
We must not repeat job title as heading.
We need to include metadata like Job ID? Not present.
Let's extract content.
Company description: "About Juniper Square Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come. Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us! Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time."
That's a lot. We'll put under About the role
maybe? Actually "About Juniper Square" is company overview; but we can still put under About the role heading as per instruction examples. Or we could make a separate section like "About Juniper Square" but instruction only gave examples; we can use any heading but must be . 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 we should follow those examples. Probably they expect sections like About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We'll put company overview under About the role.
Then responsibilities: list items under What You’ll Do.
We need to convert each bullet to
- .
Responsibilities bullet list:
- Own reliability and observability across the organization — SLAs/SLOs, instrumentation, and on-call health
- Design, deploy, and maintain Kubernetes infrastructure (Helm, EKS/ECS) and core AWS services (RDS/Aurora Postgres, networking, scaling)
- Build and maintain CI/CD pipelines in GitHub Actions and Argo/Helm
- Drive adoption of Infrastructure as Code standards (Terraform, and increasingly Crossplane) across multiple teams
- Partner with 16+ engineering teams to roll out new standards, tools, and processes — adapting the rollout to how each team actually works
- Participate in on-call rotation and lead incident response/root-cause analysis for issues that cross team boundaries
- Use AI tools daily to work faster and more effectively, and help less AI-fluent teammates pick up the same habits
- Represent SRE's perspective in planning conversations with engineering leadership
We'll put under
Responsibilities
with .
Qualifications: Required and Preferred.
We can combine into Requirements or Qualifications. Use Qualifications
maybe.
List required:
- 8-10 years of experience as a Senior SRE, DevOps, or Infrastructure Engineer
- Background at smaller-to-mid-size, high-growth SaaS companies (Series A/B through C/D) — you know how to move fast and own ambiguity, not navigate a large, slow-moving org
- Deep hands-on experience with Kubernetes (EKS or ECS), GitHub Actions, Terraform, CI/CD pipelines, and Helm/Argo
- Real database experience with Postgres and DocumentDB (Mongo) across RDS/Aurora
- A track record of working cross-functionally — managing timelines, setting expectations, and collaborating with other teams' engineers, not just your own
- Already using AI as part of your actual workflow (coding, debugging, design)
Preferred:
- Crossplane
- Datadog
We could list as separate under Qualifications.
Then "What Sets You Apart" maybe could be Skills? But we could include under Qualifications as additional bullet points. However instruction says use sections only when posting has real specific content. We have that content; we could make a section "Skills" for those bullet points. But we already have Qualifications. Might be okay to include under Qualifications.
Better: Use Requirements
for required, and maybe Preferred Qualifications
but instruction only gave examples; but we can still use for any heading. Safer to follow examples: maybe we put Required under Qualifications and Preferred under Skills? But Skills section is listed as example. We could put the "What Sets You Apart" under Skills.
Let's decide:
- About the role (company overview + Juniper Square offers employees ways to work etc.)
- Responsibilities
- Qualifications (required)
- Skills (preferred + what sets you apart)
- Benefits
- Pay
We need to include Pay section with base salary range.
Benefits list: Health, dental, and vision care for you and your family; Life insurance; Mental wellness coverage; Fertility and growing family support; Flex Time Off in addition to company-paid holidays; Paid family leave, medical leave, and bereavement leave policies; Retirement saving plans; Allowance to customize your work and technology setup at home; Annual professional development stipend.
We'll put under Benefits
with .
Pay: Pay
with containing the base salary range and note.
We must not include Schedule.
Now ensure we preserve all substantive info: also note about Juniper Square offers employees a variety of ways to work... that's part of About the role.
Also note about "Your recruiter can provide additional details about compensation and benefits." That's maybe boilerplate? It's not a list; it's a sentence. Might be considered application instruction? It's not exactly instruction to apply; it's just a note. Might be okay to keep as prose under Pay or Benefits? It's about compensation and benefits details. Could be kept under Pay as a note.
But instruction: remove application instructions. This is not exactly application instruction; it's a note about recruiter providing details. Might be okay to keep.
We'll include that sentence in Pay section after salary range.
Now produce HTML.
We must not include markdown fences.
Let's craft:
About the role
About Juniper Square Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come. Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us! Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time.
Responsibilities
- Own reliability and observability across the organization — SLAs/SLOs, instrumentation, and on-call health
- Design, deploy, and maintain Kubernetes infrastructure (Helm, EKS/ECS) and core AWS services (RDS/Aurora Postgres, networking, scaling)
- Build and maintain CI/CD pipelines in GitHub Actions and Argo/Helm
- Drive adoption of Infrastructure as Code standards (Terraform, and increasingly Crossplane) across multiple teams
- Partner with 16+ engineering teams to roll out new standards, tools, and processes — adapting the rollout to how each team actually works
- Participate in on-call rotation and lead incident response/root-cause analysis for issues that cross team boundaries
- Use AI tools daily to work faster and more effectively, and help less AI-fluent teammates pick up the same habits
- Represent SRE's perspective in planning conversations with engineering leadership
Qualifications
- 8-10 years of experience as a Senior SRE, DevOps, or Infrastructure Engineer
- Background at smaller-to-mid-size, high-growth SaaS companies (Series A/B through C/D
for prose. We need to include headings as
. For each section we include heading then content.
We must not repeat job title as heading.
We need to include metadata like Job ID? Not present.
Let's extract content.
Company description: "About Juniper Square Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come. Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us! Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time."
That's a lot. We'll put under About the role
maybe? Actually "About Juniper Square" is company overview; but we can still put under About the role heading as per instruction examples. Or we could make a separate section like "About Juniper Square" but instruction only gave examples; we can use any heading but must be . 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 we should follow those examples. Probably they expect sections like About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We'll put company overview under About the role.
Then responsibilities: list items under What You’ll Do.
We need to convert each bullet to
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow those examples. Probably they expect sections like About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We'll put company overview under About the role. Then responsibilities: list items under What You’ll Do. We need to convert each bullet to
Responsibilities
with- .
Qualifications: Required and Preferred.
We can combine into Requirements or Qualifications. Use
- Own reliability and observability across the organization — SLAs/SLOs, instrumentation, and on-call health
- Design, deploy, and maintain Kubernetes infrastructure (Helm, EKS/ECS) and core AWS services (RDS/Aurora Postgres, networking, scaling)
- Build and maintain CI/CD pipelines in GitHub Actions and Argo/Helm
- Drive adoption of Infrastructure as Code standards (Terraform, and increasingly Crossplane) across multiple teams
- Partner with 16+ engineering teams to roll out new standards, tools, and processes — adapting the rollout to how each team actually works
- Participate in on-call rotation and lead incident response/root-cause analysis for issues that cross team boundaries
- Use AI tools daily to work faster and more effectively, and help less AI-fluent teammates pick up the same habits
- Represent SRE's perspective in planning conversations with engineering leadership
- 8-10 years of experience as a Senior SRE, DevOps, or Infrastructure Engineer
- Background at smaller-to-mid-size, high-growth SaaS companies (Series A/B through C/D
Qualifications
maybe. List required: - 8-10 years of experience as a Senior SRE, DevOps, or Infrastructure Engineer - Background at smaller-to-mid-size, high-growth SaaS companies (Series A/B through C/D) — you know how to move fast and own ambiguity, not navigate a large, slow-moving org - Deep hands-on experience with Kubernetes (EKS or ECS), GitHub Actions, Terraform, CI/CD pipelines, and Helm/Argo - Real database experience with Postgres and DocumentDB (Mongo) across RDS/Aurora - A track record of working cross-functionally — managing timelines, setting expectations, and collaborating with other teams' engineers, not just your own - Already using AI as part of your actual workflow (coding, debugging, design) Preferred: - Crossplane - Datadog We could list as separate- under Qualifications.
Then "What Sets You Apart" maybe could be Skills? But we could include under Qualifications as additional bullet points. However instruction says use sections only when posting has real specific content. We have that content; we could make a section "Skills" for those bullet points. But we already have Qualifications. Might be okay to include under Qualifications.
Better: Use
Requirements
for required, and maybePreferred Qualifications
but instruction only gave examples; but we can still use for any heading. Safer to follow examples: maybe we put Required under Qualifications and Preferred under Skills? But Skills section is listed as example. We could put the "What Sets You Apart" under Skills.
Let's decide:
- About the role (company overview + Juniper Square offers employees ways to work etc.)
- Responsibilities
- Qualifications (required)
- Skills (preferred + what sets you apart)
- Benefits
- Pay
We need to include Pay section with base salary range.
Benefits list: Health, dental, and vision care for you and your family; Life insurance; Mental wellness coverage; Fertility and growing family support; Flex Time Off in addition to company-paid holidays; Paid family leave, medical leave, and bereavement leave policies; Retirement saving plans; Allowance to customize your work and technology setup at home; Annual professional development stipend.
We'll put under Benefits
with .
Pay: Pay
with containing the base salary range and note.
We must not include Schedule.
Now ensure we preserve all substantive info: also note about Juniper Square offers employees a variety of ways to work... that's part of About the role.
Also note about "Your recruiter can provide additional details about compensation and benefits." That's maybe boilerplate? It's not a list; it's a sentence. Might be considered application instruction? It's not exactly instruction to apply; it's just a note. Might be okay to keep as prose under Pay or Benefits? It's about compensation and benefits details. Could be kept under Pay as a note.
But instruction: remove application instructions. This is not exactly application instruction; it's a note about recruiter providing details. Might be okay to keep.
We'll include that sentence in Pay section after salary range.
Now produce HTML.
We must not include markdown fences.
Let's craft:
About the role
About Juniper Square Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come. Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us! Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time.
Responsibilities
Qualifications
Pay
withcontaining the base salary range and note. We must not include Schedule. Now ensure we preserve all substantive info: also note about Juniper Square offers employees a variety of ways to work... that's part of About the role. Also note about "Your recruiter can provide additional details about compensation and benefits." That's maybe boilerplate? It's not a list; it's a sentence. Might be considered application instruction? It's not exactly instruction to apply; it's just a note. Might be okay to keep as prose under Pay or Benefits? It's about compensation and benefits details. Could be kept under Pay as a note. But instruction: remove application instructions. This is not exactly application instruction; it's a note about recruiter providing details. Might be okay to keep. We'll include that sentence in Pay section after salary range. Now produce HTML. We must not include markdown fences. Let's craft:
About the role
About Juniper Square Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come. Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us! Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time.