← Technical and Professional Roles — P2

Goal templates — Technical and Professional Roles — P2

Technical and Professional Roles · Technical and Professional Roles · P2 — Developing 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 (P2)

Owns small-to-medium features end to end, from design through development, for a defined area of the codebase.

Specific
Deliver: "Owns small-to-medium features end to end, from design through development, for a defined area of the codebase."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Works closely with peers across disciplines and begins to influence design decisions within the feature scope.

Specific
Deliver: "Works closely with peers across disciplines and begins to influence design decisions within the feature scope."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor.

Specific
Deliver: "Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance.

Specific
Deliver: "Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design.

Specific
Deliver: "Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Owns small-to-medium features end to end, from design through development, for a defined area of the codebase.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Owns small-to-medium features end to end, from design through development, for a defined area of the codebase."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

2. Works closely with peers across disciplines and begins to influence design decisions within the feature scope.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Works closely with peers across disciplines and begins to influence design decisions within the feature scope."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

3. Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

4. Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

5. Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles moderate problems requiring judgment in familiar contexts, weighing tradeoffs within a feature's scope under general instruction."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P2 — Developing 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 (P2)

Owns small-to-medium features end to end, from design through development, for a defined area of the codebase.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns small-to-medium features end to end, from design through development, for a defined area of the codebase."
  • Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Works closely with peers across disciplines and begins to influence design decisions within the feature scope.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Works closely with peers across disciplines and begins to influence design decisions within the feature scope."
  • Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor."
  • Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance."
  • Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design."
  • Evidence at this level's decision rights bar: "Routine technical choices within guidance" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Owns small-to-medium features end to end, from design through development, for a defined area of the codebase.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns small-to-medium features end to end, from design through development, for a defined area of the codebase."
  KR2. Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩

Objective 2: Works closely with peers across disciplines and begins to influence design decisions within the feature scope.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Works closely with peers across disciplines and begins to influence design decisions within the feature scope."
  KR2. Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩

Objective 3: Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor."
  KR2. Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩

Objective 4: Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance."
  KR2. Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩

Objective 5: Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design."
  KR2. Evidence at this level's decision rights bar: "Routine technical choices within guidance" — ⟨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
Owns small-to-medium features end to end, from design through development, for a defined area of the codebase.Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."⟨target⟩⟨date⟩
Works closely with peers across disciplines and begins to influence design decisions within the feature scope.Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."⟨target⟩⟨date⟩
Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor.Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."⟨target⟩⟨date⟩
Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance.Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."⟨target⟩⟨date⟩
Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design.Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Owns small-to-medium features end to end, from design through development, for a defined area of the codebase.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Works closely with peers across disciplines and begins to influence design decisions within the feature scope.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies developing engineering judgment in familiar contexts to own small-to-medium features, including API and service design within a defined area."
   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 small-to-medium features end to end, from design through development, for a defined area of the codebase."→ ⟨target⟩ by ⟨date⟩
  • "Works closely with peers across disciplines and begins to influence design decisions within the feature scope."→ ⟨target⟩ by ⟨date⟩
  • "Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor."→ ⟨target⟩ by ⟨date⟩
  • "Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance."→ ⟨target⟩ by ⟨date⟩
  • "Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design."→ ⟨target⟩ by ⟨date⟩

Role calibration

  • Meets the scope bar: "Defined deliverables / small features"→ ⟨target⟩ by ⟨date⟩
  • Meets the autonomy bar: "General supervision; reviewed at milestones"→ ⟨target⟩ by ⟨date⟩
  • Meets the complexity bar: "Some non-routine problems; applies established patterns"→ ⟨target⟩ by ⟨date⟩
  • Meets the impact bar: "Own and immediate-team deliverables"→ ⟨target⟩ by ⟨date⟩
  • Meets the decision rights bar: "Routine technical choices within guidance"→ ⟨target⟩ by ⟨date⟩
  • Meets the leadership bar: "May guide interns"→ ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Internal process
  - "Owns small-to-medium features end to end, from design through development, for a defined area of the codebase."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Works closely with peers across disciplines and begins to influence design decisions within the feature scope."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Designs and implements service APIs (e.g., gRPC, FastAPI) backed by data stores such as SQL or DynamoDB, learning tradeoffs as a developing individual contributor."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Participates in code review and on-call rotations, using observability tooling such as Datadog to triage production incidents with guidance."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Builds empathy for downstream consumers and teammates, asking clarifying questions to ensure work fits the broader design."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]

Role calibration
  - Meets the scope bar: "Defined deliverables / small features"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "General supervision; reviewed at milestones"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Some non-routine problems; applies established patterns"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Own and immediate-team deliverables"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Routine technical choices within guidance"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "May guide interns"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]