← DevOps & Site Reliability Engineering — P2

Goal templates — DevOps & Site Reliability Engineering — P2

Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering · P2 — Developing Professional

These are canon-derived frames, not advice: every line is either verbatim JobFrame canon text or a fixed template wrapping it. ⟨target⟩ / ⟨baseline⟩ / ⟨date⟩ are placeholders for the manager to fill in. Nothing here is generated by AI — rows are omitted, never invented, when the canon lacks the underlying field.

SMART goals

One row per canon core output / responsibility this level owns.

JFM responsibility (P2)

Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance.

Specific
Deliver: "Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
Relevant
Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana.

Specific
Deliver: "Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
Relevant
Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken.

Specific
Deliver: "Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
Relevant
Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Participates in incident response with supervision and executes defined reliability work and well-scoped improvements.

Specific
Deliver: "Participates in incident response with supervision and executes defined reliability work and well-scoped improvements."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
Relevant
Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns.

Specific
Deliver: "Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
Relevant
Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
   Relevant:    Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

2. Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
   Relevant:    Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

3. Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
   Relevant:    Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

4. Participates in incident response with supervision and executes defined reliability work and well-scoped improvements.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Participates in incident response with supervision and executes defined reliability work and well-scoped improvements."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
   Relevant:    Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

5. Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Moderate complexity in familiar contexts; performs basic troubleshooting and documents findings, escalating issues beyond established procedures."
   Relevant:    Advances the Infrastructure, DevOps & SRE · DevOps & Site Reliability Engineering mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

OKRs

Objectives from this level's core outputs; key results only where a real dimension or capability backs them.

JFM responsibility (P2)

Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance."
  • Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana."
  • Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken."
  • Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Participates in incident response with supervision and executes defined reliability work and well-scoped improvements.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Participates in incident response with supervision and executes defined reliability work and well-scoped improvements."
  • Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns."
  • Evidence at this level's decision rights bar: "Routine technical choices within guidance" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance."
  KR2. Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩

Objective 2: Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana."
  KR2. Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩

Objective 3: Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken."
  KR2. Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩

Objective 4: Participates in incident response with supervision and executes defined reliability work and well-scoped improvements.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Participates in incident response with supervision and executes defined reliability work and well-scoped improvements."
  KR2. Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩

Objective 5: Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns."
  KR2. Evidence at this level's decision rights bar: "Routine technical choices within guidance" — ⟨target⟩ by ⟨date⟩

MBO areas

Key result areas from this level's responsibilities, each with a standard grounded in the canon leveling rubric where one exists.

AreaStandardTargetDue
Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance.Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."⟨target⟩⟨date⟩
Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana.Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."⟨target⟩⟨date⟩
Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken.Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."⟨target⟩⟨date⟩
Participates in incident response with supervision and executes defined reliability work and well-scoped improvements.Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."⟨target⟩⟨date⟩
Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns.Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Participates in incident response with supervision and executes defined reliability work and well-scoped improvements.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational knowledge of Linux/Unix administration, scripting (Python/Bash), and basic cloud and monitoring concepts to execute well-defined reliability tasks following runbooks and existing patterns."
   Target:   ⟨target⟩   Due: ⟨date⟩

Scorecard

Only perspectives with real canon backing are shown — no Financial or Customer perspective, since nothing in the canon grounds business-financial or customer measures for a role alone.

Internal process

  • "Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance."→ ⟨target⟩ by ⟨date⟩
  • "Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana."→ ⟨target⟩ by ⟨date⟩
  • "Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken."→ ⟨target⟩ by ⟨date⟩
  • "Participates in incident response with supervision and executes defined reliability work and well-scoped improvements."→ ⟨target⟩ by ⟨date⟩
  • "Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns."→ ⟨target⟩ by ⟨date⟩

Role calibration

  • Meets the scope bar: "Defined deliverables / small features"→ ⟨target⟩ by ⟨date⟩
  • Meets the autonomy bar: "General supervision; reviewed at milestones"→ ⟨target⟩ by ⟨date⟩
  • Meets the complexity bar: "Some non-routine problems; applies established patterns"→ ⟨target⟩ by ⟨date⟩
  • Meets the impact bar: "Own and immediate-team deliverables"→ ⟨target⟩ by ⟨date⟩
  • Meets the decision rights bar: "Routine technical choices within guidance"→ ⟨target⟩ by ⟨date⟩
  • Meets the leadership bar: "May guide interns"→ ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Internal process
  - "Performs basic troubleshooting and documents existing systems, monitoring solutions, and runbooks under guidance."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Contributes to automation scripts in Python and Bash and assists with implementation of monitoring solutions using tools like Prometheus and Grafana."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Joins the on-call rotation with phased onboarding — responding to alerts, following runbooks, escalating appropriately, and documenting actions taken."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Participates in incident response with supervision and executes defined reliability work and well-scoped improvements."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Provisions defined infrastructure changes using Terraform or CloudFormation templates against established patterns."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]

Role calibration
  - Meets the scope bar: "Defined deliverables / small features"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "General supervision; reviewed at milestones"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Some non-routine problems; applies established patterns"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Own and immediate-team deliverables"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Routine technical choices within guidance"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "May guide interns"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]