← Infrastructure & Platform Engineering — P6

Goal templates — Infrastructure & Platform Engineering — P6

Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering · P6 — Principal 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 (P6)

Owns the technical direction of how dozens of services fit into a coherent platform architecture

Specific: Deliver: "Owns the technical direction of how dozens of services fit into a coherent platform architecture"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
Relevant: Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)

Specific: Deliver: "Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
Relevant: Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach

Specific: Deliver: "Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
Relevant: Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization

Specific: Deliver: "Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
Relevant: Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Influences systems and standards spanning 10 to 30+ teams through influence-without-authority

Specific: Deliver: "Influences systems and standards spanning 10 to 30+ teams through influence-without-authority"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
Relevant: Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Owns the technical direction of how dozens of services fit into a coherent platform architecture  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Owns the technical direction of how dozens of services fit into a coherent platform architecture"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
   Relevant:    Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

2. Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
   Relevant:    Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

3. Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
   Relevant:    Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

4. Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
   Relevant:    Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

5. Influences systems and standards spanning 10 to 30+ teams through influence-without-authority  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Influences systems and standards spanning 10 to 30+ teams through influence-without-authority"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Provides visionary problem-solving with full independence, owning long-term technical roadmap and coherent architecture across 10 to 30+ teams."
   Relevant:    Advances the Infrastructure, DevOps & SRE · Infrastructure & Platform Engineering mandate for a P6 — Principal 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 (P6)

Owns the technical direction of how dozens of services fit into a coherent platform architecture

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns the technical direction of how dozens of services fit into a coherent platform architecture"
Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)"
Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach"
Evidence at this level's complexity bar: "Strategic, open-ended problems shaping the technical future" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization"
Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Influences systems and standards spanning 10 to 30+ teams through influence-without-authority

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Influences systems and standards spanning 10 to 30+ teams through influence-without-authority"
Evidence at this level's decision rights bar: "Sets technical strategy for a major area" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Owns the technical direction of how dozens of services fit into a coherent platform architecture  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns the technical direction of how dozens of services fit into a coherent platform architecture"
  KR2. Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

Objective 2: Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)"
  KR2. Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

Objective 3: Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach"
  KR2. Evidence at this level's complexity bar: "Strategic, open-ended problems shaping the technical future" — ⟨target⟩ by ⟨date⟩

Objective 4: Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization"
  KR2. Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

Objective 5: Influences systems and standards spanning 10 to 30+ teams through influence-without-authority  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Influences systems and standards spanning 10 to 30+ teams through influence-without-authority"
  KR2. Evidence at this level's decision rights bar: "Sets technical strategy for a major area" — ⟨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.

Area	Standard	Target	Due
Owns the technical direction of how dozens of services fit into a coherent platform architecture	Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."	⟨target⟩	⟨date⟩
Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)	Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."	⟨target⟩	⟨date⟩
Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach	Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."	⟨target⟩	⟨date⟩
Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization	Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."	⟨target⟩	⟨date⟩
Influences systems and standards spanning 10 to 30+ teams through influence-without-authority	Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Owns the technical direction of how dozens of services fit into a coherent platform architecture  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Influences systems and standards spanning 10 to 30+ teams through influence-without-authority  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies field-shaping platform expertise to organization-wide architecture spanning dozens of services and multiple teams, owning vendor and budget decisions."
   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

"Owns the technical direction of how dozens of services fit into a coherent platform architecture"→ ⟨target⟩ by ⟨date⟩
"Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)"→ ⟨target⟩ by ⟨date⟩
"Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach"→ ⟨target⟩ by ⟨date⟩
"Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization"→ ⟨target⟩ by ⟨date⟩
"Influences systems and standards spanning 10 to 30+ teams through influence-without-authority"→ ⟨target⟩ by ⟨date⟩

Role calibration

Meets the scope bar: "Organization-wide architecture and the hardest problems"→ ⟨target⟩ by ⟨date⟩
Meets the autonomy bar: "Defines direction; minimal oversight"→ ⟨target⟩ by ⟨date⟩
Meets the complexity bar: "Strategic, open-ended problems shaping the technical future"→ ⟨target⟩ by ⟨date⟩
Meets the impact bar: "Organization-wide"→ ⟨target⟩ by ⟨date⟩
Meets the decision rights bar: "Sets technical strategy for a major area"→ ⟨target⟩ by ⟨date⟩
Meets the leadership bar: "Recognized authority; multiplies many teams"→ ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Internal process
  - "Owns the technical direction of how dozens of services fit into a coherent platform architecture"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Carries budget conversations and owns vendor relationships (Datadog, HashiCorp)"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Holds a charter covering multiple platform teams, setting long-term technical roadmap and resource planning approach"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Provides high-level mentorship to senior engineers and shapes architectural decisions across the organization"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Influences systems and standards spanning 10 to 30+ teams through influence-without-authority"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]

Role calibration
  - Meets the scope bar: "Organization-wide architecture and the hardest problems"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Defines direction; minimal oversight"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Strategic, open-ended problems shaping the technical future"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Organization-wide"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Sets technical strategy for a major area"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "Recognized authority; multiplies many teams"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]