Goal templates — Database Engineering — P6

Data & Database Engineering · Database 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)

Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions

Specific: Deliver: "Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions"
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 on organization-wide database architecture, reliability, and scale with full independence."
Relevant: Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale

Specific: Deliver: "Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale"
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 on organization-wide database architecture, reliability, and scale with full independence."
Relevant: Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization

Specific: Deliver: "Meets with stakeholders to advise and negotiate, shaping the data persistence direction for 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 on organization-wide database architecture, reliability, and scale with full independence."
Relevant: Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams

Specific: Deliver: "Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams"
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 on organization-wide database architecture, reliability, and scale with full independence."
Relevant: Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

JFM responsibility (P6)

Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives

Specific: Deliver: "Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives"
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 on organization-wide database architecture, reliability, and scale with full independence."
Relevant: Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions"
   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 on organization-wide database architecture, reliability, and scale with full independence."
   Relevant:    Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

2. Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale"
   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 on organization-wide database architecture, reliability, and scale with full independence."
   Relevant:    Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

3. Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Meets with stakeholders to advise and negotiate, shaping the data persistence direction for 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 on organization-wide database architecture, reliability, and scale with full independence."
   Relevant:    Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

4. Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams"
   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 on organization-wide database architecture, reliability, and scale with full independence."
   Relevant:    Advances the Data & Database Engineering · Database Engineering mandate for a P6 — Principal Professional.
   Time-bound:  ⟨date⟩

5. Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives  [source: JFM responsibility (P6)]
   Specific:    Deliver: "Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives"
   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 on organization-wide database architecture, reliability, and scale with full independence."
   Relevant:    Advances the Data & Database Engineering · Database 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)

Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions"
Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale"
Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization"
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 staff and principal engineers and influences peer professionals across teams

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams"
Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P6)

Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives"
Evidence at this level's decision rights bar: "Sets technical strategy for a major area" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions"
  KR2. Evidence at this level's scope bar: "Organization-wide architecture and the hardest problems" — ⟨target⟩ by ⟨date⟩

Objective 2: Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale"
  KR2. Evidence at this level's autonomy bar: "Defines direction; minimal oversight" — ⟨target⟩ by ⟨date⟩

Objective 3: Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization"
  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 staff and principal engineers and influences peer professionals across teams  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams"
  KR2. Evidence at this level's impact bar: "Organization-wide" — ⟨target⟩ by ⟨date⟩

Objective 5: Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives  [source: JFM responsibility (P6)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives"
  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
Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions	Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."	⟨target⟩	⟨date⟩
Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale	Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."	⟨target⟩	⟨date⟩
Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization	Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."	⟨target⟩	⟨date⟩
Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams	Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."	⟨target⟩	⟨date⟩
Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives	Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives  [source: JFM responsibility (P6) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies principal, field-shaping expertise to set company-wide database engineering strategy and direct high-risk distributed-systems work."
   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

"Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions"→ ⟨target⟩ by ⟨date⟩
"Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale"→ ⟨target⟩ by ⟨date⟩
"Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization"→ ⟨target⟩ by ⟨date⟩
"Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams"→ ⟨target⟩ by ⟨date⟩
"Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives"→ ⟨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
  - "Sets engineering strategy for database systems across the company and makes strategic, high-impact, organization-wide decisions"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Leads deep, complex, or high-risk technical projects with broad impact, ensuring reliability of distributed database clusters at scale"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Meets with stakeholders to advise and negotiate, shaping the data persistence direction for the organization"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Provides high-level mentorship to staff and principal engineers and influences peer professionals across teams"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P6)]
  - "Manages technical projects spanning deadlines, budgets, and hiring/training, and supervises engineering teams on critical initiatives"  →  ⟨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)]