Site Reliability Engineer

We need to output HTML fragment with sections: About the role? Actually we have Company Description, Role Description, Responsibilities, Candidate Qualifications, Why Tennr? (which includes Benefits and maybe other), Benefits, Compensation Range. We must use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not repeat job title as heading. We have no job ID. We must include sections only when posting has real specific content. So we need sections: About the role (maybe from Role Description), Responsibilities, Qualifications (Candidate Qualifications), Benefits, Pay (Compensation Range). Possibly also "About the company" but not required heading list; we could use "About the role" for role description, and maybe "Company Description" could be omitted because not in list; but we could include as a

without heading? The instruction: 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 that pattern. Probably we should include headings for sections we have content: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also "About the company" but not required; we could just put company description as a

without heading. We must not include Schedule if not present. No schedule info. We must not include empty sections. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none obvious. We need to format lists with

• . Let's extract content: Company Description: paragraph about Tennr. Role Description: paragraph about joining Infrastructure team as SRE, hands-on role, etc. Responsibilities: bullet list items (starting with Continue the PagerDuty rollout..., Build in-app Datadog instrumentation..., Manage credential storage..., Manage certificate issuance..., Manage encryption key lifecycle...). Candidate Qualifications: bullet list items (2–4 years..., Familiarity..., Hands-on..., Working understanding..., Careful..., Eager...). Why Tennr?: bullet list items (Drive Impact..., Develop Operational Expertise..., Innovate with Purpose..., Build Relationships...). Also includes "Free lunch! Plus a pantry full of snacks." That's part of Benefits? Actually after Why Tennr? they list those bullet points then "Free lunch! Plus a pantry full of snacks." Then Benefits section: list of benefits. Benefits: list: Beautiful new office at 345 Hudson Street, Unlimited PTO, 100% paid employee health benefit options, Employer-funded 401(k) match, Competitive parental leave. Compensation Range: $175K - $200K. We need to output HTML fragment. Let's decide sections: -

  About the role

  : combine Company Description and Role Description? Actually About the role could be the Role Description paragraph. Company Description could be a preceding

  without heading, or we could include as part of About the role? The instruction: "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 that pattern. Probably we should have a heading for About the role (role description) and maybe a separate heading for About the company? Not in list, but we could just put company description as a

  before any heading. Thus output:

  Company description paragraph.

  About the role

  Role description paragraph.

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  Compensation Range: $175K - $200K

  We must not include Schedule. Check for any duplicated lines: none. Make sure we preserve all substantive information: include all bullet points exactly as given. Let's copy bullet points precisely. Responsibilities: - Continue the PagerDuty rollout across engineering teams, helping them define escalation policies, schedules, and runbooks so on-call is calm and clear. - Build in-app Datadog instrumentation — metrics, traces, and alerts — working from the observability standards Infrastructure sets. - Manage credential storage and rotation across our environments. - Manage certificate issuance, renewal, and rotation. - Manage encryption key lifecycle and rotation, keeping PHI protected end to end. Qualifications: - 2–4 years in SRE, infrastructure, systems, or a strong adjacent engineering background. - Familiarity with PagerDuty or a comparable on-call and incident-response tool. - Hands-on with Datadog or another observability platform, or eager to go deep on it. - Working understanding of secrets, certificate, and key management (e.g. AWS Secrets Manager / KMS / ACM, HashiCorp Vault). - Careful and methodical with anything touching security and rotation — you sweat the details. - Eager to grow into broader SRE ownership, and energized by working in a regulated healthcare (HIPAA / PHI) environment. Why Tennr? bullet points: - Drive Impact: one of our company values is Cowboy, meaning you set the pace. You won’t just talk about things, you’ll get them done. And feel the impact. - Develop Operational Expertise: learn the inner workings of scaling systems, tools, and infrastructure. - Innovate with Purpose: we’re not just doing this for fun (although we do have a lot of fun). At Tennr, you’ll join a high-caliber team maniacally focused on reducing patient delays across the U.S. healthcare system. - Build Relationships: collaborate and connect with like-minded, driven individuals in our Hudson Square office 4 days/week. Then after that: "Free lunch! Plus a pantry full of snacks." This is a benefit; we can include in Benefits list. Benefits list: - Beautiful new office at 345 Hudson Street - Unlimited PTO - 100% paid employee health benefit options - Employer-funded 401(k) match - Competitive parental leave - Free lunch! Plus a pantry full of snacks. We should include all. Now ensure we don't include any boilerplate like "Why Tennr?" heading; we can incorporate those bullet points under Benefits or maybe under a separate heading like "Why Tennr?" but not in allowed headings list. Could treat as part of Benefits or as a separate section with heading "Why Tennr?" but not in list; maybe better to incorporate into Benefits or as a separate

  Why Tennr?

  but instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could incorporate those points under Benefits or maybe under a heading "About the company"? However the Why Tennr? points are more about culture/benefits; we could put them under Benefits as well. But we already have Benefits list; we could add those as additional bullet points under Benefits. That would preserve all info. Thus Benefits section will include: Beautiful new office..., Unlimited PTO..., 100% paid employee health benefit options..., Employer-funded 401(k) match..., Competitive parental leave, Free lunch! Plus a pantry full of snacks., Drive Impact..., Develop Operational Expertise..., Innovate with Purpose..., Build Relationships... But that mixes culture with benefits; still preserves info. Alternatively we could add a separate heading "Why Tennr?" but it's not in the list; but the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add a heading for Why Tennr? as

  Why Tennr?

  . That seems okay. However to be safe, we could follow the pattern and include it as a heading; it's not prohibited. I'll include a heading

  Why Tennr?

  with those bullet points, and then Benefits heading with the tangible benefits. Thus we have sections: About the role, Responsibilities, Qualifications, Why Tennr?, Benefits, Pay. Check that we don't repeat any info. Now produce HTML. Let's craft:

  Today, when you go to your doctor and get referred to a specialist, your doctor sends out a referral and tells you, “They’ll be in touch soon.” So you wait. And wait. Sometimes days, weeks, or even months. Why? Because too often providers are overwhelmed with the painstakingly tedious work required to get paid by insurance companies. Powered by proprietary models, Tennr handles the complex paperwork that gets patients through the door and providers paid, helping operators get patients the right care, at the right time, in the right setting.

  About the role

  You’ll join Tennr’s Infrastructure team as a Site Reliability Engineer, focused on the systems that keep us reliable, observable, and secure. This is a hands-on role with real room to grow: you’ll roll out our on-call tooling, wire observability into the product, and own the lifecycle of the credentials, certificates, and keys that protect patient data. It’s a great fit for someone a few years into their career who wants to grow into deep SRE ownership — with strong mentorship, real problems to solve from day one, and a direct line to the reliability and security of a platform that handles PHI.

  Responsibilities

  • Continue the PagerDuty rollout across engineering teams, helping them define escalation policies, schedules, and runbooks so on-call is calm and clear.
  • Build in-app Datadog instrumentation — metrics, traces, and alerts — working from the observability standards Infrastructure sets.
  • Manage credential storage and rotation across our environments.
  • Manage certificate issuance, renewal, and rotation.
  • Manage encryption key lifecycle and rotation, keeping PHI protected end to end.

  Qualifications

  • 2–4 years in SRE, infrastructure, systems, or a strong adjacent engineering background.
  • Familiarity with PagerDuty or a comparable on-call and incident-response tool.
  • Hands-on with Datadog or another observability platform, or eager to go deep on it.
  • Working understanding of secrets, certificate, and key management (e.g. AWS Secrets Manager / KMS / ACM, HashiCorp Vault).
  • Careful and methodical with anything touching security and rotation — you sweat the details.
  • Eager to grow into broader SRE ownership, and energized by working in a regulated healthcare (HIPAA / PHI) environment.

  Why Tennr?

  • Drive Impact: one of our company values is Cowboy, meaning you set the pace. You won’t just talk about things, you’ll get them done. And feel the impact.
  • Develop Operational Expertise: learn the inner workings of scaling systems, tools, and infrastructure.
  • Innovate with Purpose: we’re not just doing this for fun (although we do have a lot of fun). At Tennr, you’ll join a high-caliber team maniacally focused on reducing patient delays across the U.S. healthcare system.
  • Build