Goal templates — Security Engineering — P6

Security · Security 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)

Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area

Specific: Deliver: "Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
Relevant: Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups

Specific: Deliver: "Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
Relevant: Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage

Specific: Deliver: "Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
Relevant: Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams

Specific: Deliver: "Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
Relevant: Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations

Specific: Deliver: "Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
Relevant: Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
   Relevant:    Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

2. Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
   Relevant:    Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

3. Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
   Relevant:    Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

4. Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
   Relevant:    Advances the Security · Security Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

5. Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Drives cross-team technical decisions and resolves precedent-setting architecture problems; categorically broader scope than senior, creating initiatives rather than owning defined areas."
   Relevant:    Advances the Security · Security 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)

Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area"
Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups"
Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage"
Evidence at this level's complexity bar: "Strategic, open-ended problems shaping the technical future" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams"
Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations"
Evidence at this level's decision rights bar: "Sets technical strategy for a major area" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area"
  KR2. Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

Objective 2: Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups"
  KR2. Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

Objective 3: Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage"
  KR2. Evidence at this level's complexity bar: "Strategic, open-ended problems shaping the technical future" — ⟨target⟩ by ⟨date⟩

Objective 4: Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams"
  KR2. Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

Objective 5: Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations"
  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
Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area	Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."	⟨target⟩	⟨date⟩
Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups	Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."	⟨target⟩	⟨date⟩
Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage	Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."	⟨target⟩	⟨date⟩
Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams	Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."	⟨target⟩	⟨date⟩
Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations	Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal-level engineering expertise to create scope and define cross-team technical security programs with organizational reach."
   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

"Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area"→ ⟨target⟩ by ⟨date⟩
"Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups"→ ⟨target⟩ by ⟨date⟩
"Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage"→ ⟨target⟩ by ⟨date⟩
"Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams"→ ⟨target⟩ by ⟨date⟩
"Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations"→ ⟨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
  - "Creates scope where none existed — defines new cross-team technical initiatives and detection/architecture programs that did not previously exist, categorically beyond owning a defined area"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Drives cross-team technical decisions on platform-wide security architecture (cloud-native detection, ZTNA rollout, detection-as-code platform), resolving conflicting requirements across engineering groups"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Designs the technical security architecture and standards that other engineers build against, establishing reusable patterns for IAM, segmentation, and detection coverage"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Analyzes trends in the threat environment and translates them into engineering roadmaps and organizational risk reduction across multiple teams"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Mentors senior and staff-level engineers and acts as the technical authority resolving the hardest architecture and incident escalations"  →  ⟨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)]