Goal templates — Data Engineering — M2

Data & Database Engineering · Data Engineering · M2 — Manager II

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 (M2)

Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments.

Specific: Deliver: "Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

JFM responsibility (M2)

Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers.

Specific: Deliver: "Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

JFM responsibility (M2)

Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads.

Specific: Deliver: "Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

JFM responsibility (M2)

Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents.

Specific: Deliver: "Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

JFM responsibility (M2)

Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC.

Specific: Deliver: "Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments. [source: JFM responsibility (M2)]
Specific: Deliver: "Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

2. Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers. [source: JFM responsibility (M2)]
Specific: Deliver: "Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

3. Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads. [source: JFM responsibility (M2)]
Specific: Deliver: "Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

4. Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents. [source: JFM responsibility (M2)]
Specific: Deliver: "Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

5. Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC. [source: JFM responsibility (M2)]
Specific: Deliver: "Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment within known factors on pipeline design, partitioning, and batch/stream trade-offs for assigned workloads; owns tactical SLA outcomes."
Relevant: Advances the Data & Database Engineering · Data Engineering mandate for a M2 — Manager II.
Time-bound: ⟨date⟩

OKRs

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

JFM responsibility (M2)

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments."
Evidence at this level's scope bar: "An established team or sub-function" — ⟨target⟩ by ⟨date⟩

JFM responsibility (M2)

Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers."
Evidence at this level's autonomy bar: "Owns planning for the group" — ⟨target⟩ by ⟨date⟩

JFM responsibility (M2)

Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads."
Evidence at this level's complexity bar: "Cross-project coordination and priorities" — ⟨target⟩ by ⟨date⟩

JFM responsibility (M2)

Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents."
Evidence at this level's impact bar: "Group delivery and development" — ⟨target⟩ by ⟨date⟩

JFM responsibility (M2)

Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC."
Evidence at this level's decision rights bar: "Owns staffing, priorities, performance for the group" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments. [source: JFM responsibility (M2)]
KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments."
KR2. Evidence at this level's scope bar: "An established team or sub-function" — ⟨target⟩ by ⟨date⟩

Objective 2: Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers. [source: JFM responsibility (M2)]
KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers."
KR2. Evidence at this level's autonomy bar: "Owns planning for the group" — ⟨target⟩ by ⟨date⟩

Objective 3: Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads. [source: JFM responsibility (M2)]
KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads."
KR2. Evidence at this level's complexity bar: "Cross-project coordination and priorities" — ⟨target⟩ by ⟨date⟩

Objective 4: Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents. [source: JFM responsibility (M2)]
KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents."
KR2. Evidence at this level's impact bar: "Group delivery and development" — ⟨target⟩ by ⟨date⟩

Objective 5: Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC. [source: JFM responsibility (M2)]
KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC."
KR2. Evidence at this level's decision rights bar: "Owns staffing, priorities, performance for the group" — ⟨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
Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments.	Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."	⟨target⟩	⟨date⟩
Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers.	Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."	⟨target⟩	⟨date⟩
Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads.	Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."	⟨target⟩	⟨date⟩
Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents.	Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."	⟨target⟩	⟨date⟩
Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC.	Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments.  [source: JFM responsibility (M2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers.  [source: JFM responsibility (M2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads.  [source: JFM responsibility (M2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents.  [source: JFM responsibility (M2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC.  [source: JFM responsibility (M2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies deep data engineering judgment to lead a skilled team, making pipeline design and tooling decisions within known engineering factors."
   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

"Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments."→ ⟨target⟩ by ⟨date⟩
"Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers."→ ⟨target⟩ by ⟨date⟩
"Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads."→ ⟨target⟩ by ⟨date⟩
"Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents."→ ⟨target⟩ by ⟨date⟩
"Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC."→ ⟨target⟩ by ⟨date⟩

Role calibration

Meets the scope bar: "An established team or sub-function"→ ⟨target⟩ by ⟨date⟩
Meets the autonomy bar: "Owns planning for the group"→ ⟨target⟩ by ⟨date⟩
Meets the complexity bar: "Cross-project coordination and priorities"→ ⟨target⟩ by ⟨date⟩
Meets the impact bar: "Group delivery and development"→ ⟨target⟩ by ⟨date⟩
Meets the decision rights bar: "Owns staffing, priorities, performance for the group"→ ⟨target⟩ by ⟨date⟩
Meets the leadership bar: "Manages a team; sometimes manages leads"→ ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Internal process
  - "Manages a skilled team of data engineers (and occasionally junior leads) delivering robust pipelines and data warehousing solutions on Snowflake/Redshift/BigQuery, owning tactical outcomes against quarterly commitments."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (M2)]
  - "Coordinates cross-functionally with analytics and product teams to integrate new sources via Fivetran/Kafka ingestion and to surface curated data into Looker/BI layers."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (M2)]
  - "Makes judgment calls within known engineering factors on pipeline design trade-offs — Spark vs. dbt transformations, partitioning, and batch vs. streaming — for the team's assigned workloads."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (M2)]
  - "Owns the team's data quality and SLA targets, defining monitoring and alerting expectations (Splunk/Grafana) and driving remediation of recurring incidents."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (M2)]
  - "Develops individual engineers through written development plans, calibrating performance and supporting promotion of independent contributors to senior IC."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (M2)]

Role calibration
  - Meets the scope bar: "An established team or sub-function"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Owns planning for the group"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Cross-project coordination and priorities"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Group delivery and development"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Owns staffing, priorities, performance for the group"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "Manages a team; sometimes manages leads"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]