← Software Engineering — P6

Goal templates — Software Engineering — P6

Software Engineering · Software 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)

Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence.

Specific
Deliver: "Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
Relevant
Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
Time-bound
⟨date⟩

JFM responsibility (P6)

Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas.

Specific
Deliver: "Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
Relevant
Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
Time-bound
⟨date⟩

JFM responsibility (P6)

Provides technical and professional leadership for reporting engineers.

Specific
Deliver: "Provides technical and professional leadership for reporting engineers."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
Relevant
Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
Time-bound
⟨date⟩

JFM responsibility (P6)

Works closely with executives and stakeholders to align technical strategies with business goals.

Specific
Deliver: "Works closely with executives and stakeholders to align technical strategies with business goals."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
Relevant
Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
Time-bound
⟨date⟩

JFM responsibility (P6)

Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals.

Specific
Deliver: "Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
Relevant
Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence.  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
   Relevant:    Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

2. Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas.  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
   Relevant:    Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

3. Provides technical and professional leadership for reporting engineers.  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Provides technical and professional leadership for reporting engineers."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
   Relevant:    Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

4. Works closely with executives and stakeholders to align technical strategies with business goals.  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Works closely with executives and stakeholders to align technical strategies with business goals."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
   Relevant:    Advances the Software Engineering · Software Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

5. Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals.  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves field-shaping, organization-wide problems with full independence; aligns technical architecture with business strategy."
   Relevant:    Advances the Software Engineering · Software 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)

Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence."
  • Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas."
  • Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Provides technical and professional leadership for reporting engineers.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provides technical and professional leadership for reporting engineers."
  • Evidence at this level's complexity bar: "Strategic, open-ended problems shaping the technical future" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Works closely with executives and stakeholders to align technical strategies with business goals.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Works closely with executives and stakeholders to align technical strategies with business goals."
  • Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals."
  • Evidence at this level's decision rights bar: "Sets technical strategy for a major area" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence.  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence."
  KR2. Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

Objective 2: Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas.  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas."
  KR2. Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

Objective 3: Provides technical and professional leadership for reporting engineers.  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provides technical and professional leadership for reporting engineers."
  KR2. Evidence at this level's complexity bar: "Strategic, open-ended problems shaping the technical future" — ⟨target⟩ by ⟨date⟩

Objective 4: Works closely with executives and stakeholders to align technical strategies with business goals.  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Works closely with executives and stakeholders to align technical strategies with business goals."
  KR2. Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

Objective 5: Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals.  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals."
  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.

AreaStandardTargetDue
Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence.Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."⟨target⟩⟨date⟩
Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas.Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."⟨target⟩⟨date⟩
Provides technical and professional leadership for reporting engineers.Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."⟨target⟩⟨date⟩
Works closely with executives and stakeholders to align technical strategies with business goals.Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."⟨target⟩⟨date⟩
Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals.Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence.  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas.  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Provides technical and professional leadership for reporting engineers.  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Works closely with executives and stakeholders to align technical strategies with business goals.  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals.  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Provides organization-wide technical vision; architects solutions for features and products that grow the business and makes crucial product and team-allocation decisions, coding selectively on critical paths."
   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

  • "Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence."→ ⟨target⟩ by ⟨date⟩
  • "Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas."→ ⟨target⟩ by ⟨date⟩
  • "Provides technical and professional leadership for reporting engineers."→ ⟨target⟩ by ⟨date⟩
  • "Works closely with executives and stakeholders to align technical strategies with business goals."→ ⟨target⟩ by ⟨date⟩
  • "Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals."→ ⟨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
  - "Architects solutions for features and products that grow the business, providing organization-wide technical direction with full independence."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Makes crucial product decisions regarding direction and scope and makes strategic decisions about which team members work on specific areas."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Provides technical and professional leadership for reporting engineers."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Works closely with executives and stakeholders to align technical strategies with business goals."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Codes selectively on critical and complex parts of projects and provides high-level mentorship that influences peer professionals."  →  ⟨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)]