← Technical and Professional Roles — P1

Goal templates — Technical and Professional Roles — P1

Technical and Professional Roles · Technical and Professional Roles · P1 — Entry-Level 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 (P1)

Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision.

Specific
Deliver: "Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P1)

Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers.

Specific
Deliver: "Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior 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 routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P1)

Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling.

Specific
Deliver: "Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P1)

Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS.

Specific
Deliver: "Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Solves routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
Relevant
Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

2. Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior 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 routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

3. Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

4. Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Solves routine, well-defined problems using standard approaches; escalates anything ambiguous to senior engineers."
   Relevant:    Advances the Technical and Professional Roles · Technical and Professional Roles mandate for a P1 — Entry-Level 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 (P1)

Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision."
  • Evidence at this level's scope bar: "Own tasks within a defined component" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers."
  • Evidence at this level's autonomy bar: "Close supervision; work reviewed frequently" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling."
  • Evidence at this level's complexity bar: "Routine problems with known solutions" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS."
  • Evidence at this level's impact bar: "Own deliverables" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision."
  KR2. Evidence at this level's scope bar: "Own tasks within a defined component" — ⟨target⟩ by ⟨date⟩

Objective 2: Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers."
  KR2. Evidence at this level's autonomy bar: "Close supervision; work reviewed frequently" — ⟨target⟩ by ⟨date⟩

Objective 3: Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling."
  KR2. Evidence at this level's complexity bar: "Routine problems with known solutions" — ⟨target⟩ by ⟨date⟩

Objective 4: Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS."
  KR2. Evidence at this level's impact bar: "Own deliverables" — ⟨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
Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision.Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."⟨target⟩⟨date⟩
Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers.Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."⟨target⟩⟨date⟩
Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling.Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."⟨target⟩⟨date⟩
Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS.Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational programming and debugging knowledge to routine tasks with standard, known answers; relies on established team patterns rather than independent design."
   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

  • "Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision."→ ⟨target⟩ by ⟨date⟩
  • "Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers."→ ⟨target⟩ by ⟨date⟩
  • "Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling."→ ⟨target⟩ by ⟨date⟩
  • "Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS."→ ⟨target⟩ by ⟨date⟩

Role calibration

  • Meets the scope bar: "Own tasks within a defined component"→ ⟨target⟩ by ⟨date⟩
  • Meets the autonomy bar: "Close supervision; work reviewed frequently"→ ⟨target⟩ by ⟨date⟩
  • Meets the complexity bar: "Routine problems with known solutions"→ ⟨target⟩ by ⟨date⟩
  • Meets the impact bar: "Own deliverables"→ ⟨target⟩ by ⟨date⟩
  • Meets the decision rights bar: "Few independent decisions; escalates the rest"→ ⟨target⟩ by ⟨date⟩
  • Meets the leadership bar: "None — building the craft"→ ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Internal process
  - "Learns engineering fundamentals — programming, debugging, and collaboration practices — while working under close supervision."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Contributes to small, well-scoped tasks and features within an existing codebase under the guidance of senior engineers."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Reasons through assigned problems with senior support, learning how the team's services and data flows fit together before reaching for tooling."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Submits code for review and applies reviewer feedback, building familiarity with version control, CI pipelines, and cloud basics on AWS."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]

Role calibration
  - Meets the scope bar: "Own tasks within a defined component"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Close supervision; work reviewed frequently"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Routine problems with known solutions"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Own deliverables"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Few independent decisions; escalates the rest"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "None — building the craft"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]