Performance Calibration Tool
Junior Data Engineer · Performance Levels
Fill in the fields below, then save as PDF or print at A2 landscape.
⎘ Copy to Clipboard
⎙ Print / Save as PDF
Role
Junior Data Engineer
Name
Manager
Period
Date
Level 1
Unsatisfactory
Low
Individual
Impact
Fails to deliver well-defined ETL/ELT pipeline tasks independently despite having clear direction and examples.
Submits SQL and Python with systematic quality failures - missing null handling, incorrect joins, no data tests.
Does not monitor pipelines after deployment and is unaware of failures until a consumer raises an issue.
Consistently avoids raising blockers; pipeline issues stall for days without team visibility.
Examples
Assigned a clearly scoped ingestion pipeline with an existing example; delivered broken code after multiple review cycles.
Deployed a dbt model without any data quality tests despite the team's definition of done requiring them.
Dampeners
Was placed on an unfamiliar data domain with insufficient context about source system behaviour.
Tooling environment was unstable during this period, adding friction to delivery.
Progression Signal
Delivers one well-defined pipeline task end-to-end with appropriate tests and documentation.
Begins monitoring deployed pipelines without being prompted.
Business Impact
Impact
Data consumers receive incorrect or stale data from pipelines that are not properly validated.
Senior engineers are pulled into reactive triage rather than platform improvements.
Examples
A downstream analytics dashboard surfaced incorrect aggregations for a week due to an unvalidated pipeline change.
Dampeners
Scope of pipelines at junior level limits the blast radius; damage is contained.
Progression Signal
Pipeline work begins to land with passing tests and no post-deployment incidents.
Mid
Individual
Impact
Delivers some pipeline work but with recurring quality issues - fan-out joins, incorrect CTEs, missing freshness checks.
Does not apply data quality tests consistently, treating them as optional rather than a definition-of-done requirement.
Struggles to provide useful, specific feedback in code reviews on peers' work.
Examples
Three PRs in one sprint required significant rework due to aggregation logic errors caught by the reviewer.
Reviewed a graduate's model but provided only vague feedback with no actionable suggestions.
Dampeners
Recently moved to a new data domain with unfamiliar source systems.
Progression Signal
Begins applying data quality tests as a default, not an afterthought.
Provides at least one specific, actionable data review comment per PR.
Business Impact
Impact
Data quality overhead falls on senior engineers, slowing platform delivery and reducing trust in the data.
Inconsistent pipeline quality erodes confidence among data analyst consumers.
Examples
Analyst team flagged two data quality issues in one month that were caused by insufficiently validated pipeline changes.
Dampeners
Business impact is still limited by junior scope; senior engineers catch most issues before they reach consumers.
Progression Signal
Consumer-facing data quality issues attributable to this engineer drop to near zero.
High
Individual
Impact
Persistently resistant to data review feedback; same SQL anti-patterns recur across multiple PRs.
Does not engage with data modelling discussions or show interest in understanding the downstream business context.
Work patterns create a negative signal for the team - disengagement or dismissiveness in technical discussions.
Examples
Received feedback about window function misuse on four consecutive PRs with no visible improvement.
Declined an offer to pair on a complex dimensional modelling task with a senior engineer.
Dampeners
External circumstances may be affecting engagement; should be explored before formal process.
Progression Signal
Engages with one data review comment constructively, showing genuine willingness to understand the reasoning.
Business Impact
Impact
Sustained quality issues and disengagement create friction for the team and erode data platform reliability.
Senior engineer time consumed by repeated intervention diverts from platform strategic work.
Examples
Senior engineer spent over 15% of sprint capacity managing this individual's pipeline output and rework.
Dampeners
Impact is still team-scoped; no systemic downstream business impact yet.
Progression Signal
Senior engineer overhead reduces as individual begins to take ownership of data quality in their work.
Level 2
Development Needed
Low
Individual
Impact
Delivers well-defined pipeline tasks but requires more step-by-step direction than expected at this tenure.
Data quality tests are present but shallow - checking obvious cases and missing real failure modes.
Does not yet manage their own task queue effectively; relies on TTL to break work down for them.
Examples
Completed a dbt intermediate model but only after three rounds of review covering the same data modelling issues.
Added dbt tests that checked schema only, missing business-logic assertions identified in the requirements.
Dampeners
Five months in role; still building familiarity with cloud warehouse and orchestration tooling.
Progression Signal
Begins completing similar pipeline tasks with materially fewer review rounds.
Starts writing data quality tests that catch real business logic failures, not just schema issues.
Business Impact
Impact
Pipeline delivery requires higher review investment than expected, reducing senior engineer capacity.
Shallow data quality tests provide false assurance to downstream analytics consumers.
Examples
A data quality gap missed in testing required a hot fix two days after a pipeline shipped to production.
Dampeners
Typical for early junior tenure; the trajectory matters more than the current position.
Progression Signal
Review investment drops and post-deployment issues reduce as quality improves.
Mid
Individual
Impact
Delivers pipeline work but does not connect SQL transformations to the downstream business use case they serve.
Data modelling decisions are made by copying existing patterns without understanding the trade-offs.
Does not investigate data quality alerts on pipelines they own; escalates without prior diagnosis.
Examples
Built a fact table using the source grain without considering the analyst's query pattern, causing performance issues.
Escalated a freshness alert to the senior engineer without checking the orchestration logs first.
Dampeners
Business context for the data domain has not been well-communicated to the junior engineer.
Progression Signal
Begins diagnosing pipeline issues before escalating, even partially.
Asks a question about business context before making a data modelling decision.
Business Impact
Impact
Pipeline designs optimised for ease of delivery rather than consumer needs create rework downstream.
Undiagnosed escalations consume senior engineer time that could be spent on higher-value platform work.
Examples
A grain mismatch in a fact table caused analyst rework and a delayed reporting deadline.
Dampeners
Business context gaps are a shared responsibility between the engineer and the team.
Progression Signal
Downstream rework caused by pipeline design decisions reduces as business context improves.
High
Individual
Impact
Delivers pipeline work but avoids complexity - gravitates toward familiar SQL patterns and resists stretch tasks.
Data quality test coverage is present but not improving over time; no evidence of learning from incidents.
Feedback from senior engineers about data modelling approaches is acted on minimally and not retained.
Examples
Consistently picks simple transformation tasks in sprint planning and defers complex dimensional modelling work.
Repeated the same SCD handling mistake across two separate pipelines despite it being addressed in a previous review.
Dampeners
May require a confidence-building intervention rather than a performance one.
Progression Signal
Accepts a stretch pipeline task and engages with it genuinely rather than deferring.
Business Impact
Impact
Growth trajectory is below expectation for tenure; data platform independence not developing at the expected pace.
The team cannot rely on this engineer for moderately complex pipeline work without additional oversight.
Examples
Eight months in and still requires the same level of data modelling support as at month three.
Dampeners
Business impact is low; risk is in medium-term team capacity and coverage.
Progression Signal
Delivers one moderately complex pipeline task with noticeably less support than before.
Level 3
Consistently Delivers
Low
Individual
Impact
Delivers well-defined ETL/ELT pipeline tasks independently with appropriate data quality tests and documentation.
Follows the team's SQL conventions, dbt standards, and orchestration patterns without needing reminders.
Manages their own task queue - breaks down work, estimates effort, and flags when estimates change.
Examples
Delivered a complete ingestion pipeline with source-aligned dbt models and passing data quality assertions in one sprint.
Flagged a scope change mid-sprint with a revised estimate and a clear explanation, preventing a late miss.
Dampeners
Work is still on well-defined, bounded pipeline tasks; independent scoping of new data domains not yet demonstrated.
Progression Signal
Begins contributing to the design of pipeline components before being told what approach to take.
Business Impact
Impact
Reliable sprint contribution within the scope of assigned pipeline work improves team predictability.
Data quality tests landing consistently with pipelines reduces the rate of downstream consumer issues.
Examples
Delivered all assigned tickets in three consecutive sprints with zero post-deployment data quality incidents.
Dampeners
Contribution scope is still bounded; business impact is primarily team-local.
Progression Signal
Scope of reliable contribution begins to extend to moderately complex data domains.
Mid
Individual
Impact
Delivers pipeline work reliably and is beginning to contribute to data modelling design conversations with substance.
Provides specific, actionable data review feedback on graduate and junior peers' SQL and pipeline work.
Monitors pipelines they have built after deployment and responds to alerts without being prompted.
Examples
Identified a missing index strategy on a large fact table in a peer's PR and proposed an alternative.
Spotted and resolved a freshness alert on their own pipeline within an hour without escalating.
Dampeners
Still working within defined data domains; not yet independently identifying new platform improvement opportunities.
Progression Signal
Starts proposing improvements to the team's pipeline patterns, not just implementing them.
Business Impact
Impact
Consistent delivery and proactive pipeline monitoring reduce the volume of consumer-facing data issues.
Quality review feedback on peers' work prevents data quality issues from reaching downstream consumers.
Examples
Caught a grain error in a graduate's model during review that would have caused incorrect aggregations in production.
Dampeners
Impact still primarily within the team; limited contribution to cross-domain data quality strategy.
Progression Signal
Begins contributing to data quality improvements that benefit consumers across multiple analytics teams.
High
Individual
Impact
Delivers independently across a range of ETL/ELT patterns and is beginning to drive data quality improvements proactively.
Takes on stretch data modelling tasks - dimensional design, SCD handling - and delivers them with appropriate support.
Shows growing awareness of the business context behind the data they build, not just the technical pipeline.
Examples
Designed and delivered a slowly changing dimension implementation after researching the approach independently.
Raised a data lineage concern to the senior engineer that prevented a breaking change to a shared dataset.
Dampeners
Still operating within well-understood pipeline patterns; not yet leading technical design decisions.
Progression Signal
Begins taking the lead on the technical design of a pipeline workstream, not just its delivery.
Business Impact
Impact
Growing independence and data quality ownership reduce the overhead on senior data engineers.
Proactive identification of data issues before they reach consumers builds trust with analytics stakeholders.
Examples
Analyst team lead noted that data quality issues in this engineer's domain had dropped significantly over the quarter.
Dampeners
Business impact still primarily within assigned domains; broader platform influence not yet established.
Progression Signal
Contribution to data quality and pipeline reliability begins to be recognised beyond the immediate team.
Level 4
Leading
Low
Individual
Impact
Delivers reliably and is beginning to lead small pipeline workstreams, coordinating across junior and graduate engineers.
Contributes substantively to data modelling discussions - proposing dimensional structures and flagging trade-offs.
Mentors graduate engineers in SQL, dbt patterns, and data quality practices through pairing and structured review.
Examples
Led the delivery of a new data domain ingestion pipeline, coordinating work across two graduate engineers.
Proposed a star schema design for a new reporting area and presented the trade-offs to the senior engineer.
Dampeners
Leadership is emerging; not yet consistently driving technical direction across the team.
Progression Signal
Is sought out by graduate engineers for data modelling and pipeline advice without prompting.
Business Impact
Impact
Beginning to multiply team output - their leadership of pipeline workstreams increases throughput.
Mentoring contribution means graduate engineers produce better data quality work, reducing senior review burden.
Examples
Graduate engineers they mentored began landing dbt PRs with significantly fewer review rounds.
Dampeners
Multiplier effect is still developing; team-scoped rather than cross-domain.
Progression Signal
Multiplier effect becomes more consistent as pipeline leadership responsibility grows.
Mid
Individual
Impact
Consistently delivers and actively improves the team's data engineering practices - pipeline conventions, test standards, documentation.
Leads data quality improvements in their domain, proactively identifying and resolving systemic issues.
Is a credible mentor for graduate engineers, providing structured feedback that accelerates their development.
Examples
Redesigned the team's dbt project folder structure to reduce complexity, adopted by the whole team.
Ran a pairing session series on complex SQL patterns that measurably improved graduate code quality.
Dampeners
Still at junior level - not yet driving data platform architecture or cross-team technical direction.
Progression Signal
Is described by data analysts and peers as someone who meaningfully improves data reliability in their domain.
Business Impact
Impact
Data quality improvements in their domain directly reduce the volume of analyst queries and consumer complaints.
Practice improvements they drive create a higher baseline for data engineering work across the team.
Examples
Data quality incidents in their domain dropped by over half following improvements they led.
Dampeners
Impact is still primarily domain-scoped; cross-team data platform influence not yet established.
Progression Signal
Impact of their data quality and practice improvements begins to extend to adjacent data domains.
High
Individual
Impact
Operating at the ceiling of the junior role - a clear candidate for promotion to intermediate data engineer.
Drives data platform improvements and pipeline quality initiatives beyond their assigned domain.
Is a visible technical leader within the junior cohort and a development resource for graduate engineers.
Examples
Led the implementation of a new data quality monitoring pattern that was adopted across three data domains.
Independently scoped and delivered a complex dimensional model for a new business area without escalation.
Dampeners
Still operating at junior scope; not yet shaping data architecture decisions or mentoring intermediate engineers.
Progression Signal
Promotion conversation is overdue; this engineer is operating above their current level consistently.
Business Impact
Impact
Delivering data platform value that justifies progression to intermediate data engineer.
Data quality and pipeline improvements they drive have measurable positive impact on analytics consumers.
Examples
Analyst stakeholders cited improved data reliability in their domain as enabling faster self-serve reporting.
Dampeners
Impact ceiling at junior level; promotion unlocks the scope to drive broader platform improvements.
Progression Signal
Promotion case is clear; delay risks disengagement from an engineer performing above their level.
Level 5
Transformative
Low
Individual
Impact
Performing materially beyond the junior level in pipeline design, data quality leadership, and team contribution.
Has driven embedded improvements to the team's data modelling standards or pipeline patterns independently.
Is effectively mentoring graduate engineers and beginning to influence intermediate engineers' technical approaches.
Examples
Identified a systematic grain inconsistency across three domains and proposed a standard fix adopted by the team.
Mentored three graduate engineers through complex dbt tasks, each completing them with minimal senior escalation.
Dampeners
Impact is constrained by the scope of junior-level delivery; the role is the limiting factor.
Progression Signal
Promotion should be imminent; this performance level should not persist for long at junior grade.
Business Impact
Impact
Delivering data platform impact more typical of an intermediate data engineer.
Their presence meaningfully raises the data quality floor for the team and its consumers.
Examples
Attributed with reducing a class of consumer-reported data issues through a pipeline pattern they introduced.
Dampeners
Exceptional but still bounded; promotion unlocks the scope to drive broader platform impact.
Progression Signal
Post-promotion trajectory is expected to continue at this rate of growth.
Mid
Individual
Impact
Anomalously strong for a junior data engineer - operating as a capable intermediate in pipeline design and data quality.
Contributes to data architecture discussions with credibility and drives improvements across data domain boundaries.
Sets a standard of technical rigour that raises expectations for the junior data engineering cohort.
Examples
Contributed a well-received proposal for a new data quality framework to a cross-domain technical discussion.
Independently delivered a complex ELT pipeline incorporating SCD handling and freshness monitoring end-to-end.
Dampeners
This rating at junior level is rare; it should trigger an immediate promotion review.
Progression Signal
Promotion is overdue; delay creates a real retention risk.
Business Impact
Impact
Business value delivered through data platform contributions is disproportionate to the role level.
Cross-domain data quality contributions create value that extends well beyond the immediate team.
Examples
A data model pattern they introduced reduced duplicated transformation logic across two separate data domains.
Dampeners
Exceptional performance that should not persist at junior level; promotion is the right response.
Progression Signal
Post-promotion, data engineering impact is expected to accelerate further.
High
Individual
Impact
Performing at a level that makes their junior title almost irrelevant - they are a mid-level data engineer by impact.
Their pipeline designs, data quality frameworks, and peer mentoring rival those of experienced engineers.
Represents an extreme outlier in the junior data engineering cohort.
Examples
Designed and delivered an end-to-end data domain pipeline with no senior guidance that shipped cleanly to production.
Their dbt model quality, data test coverage, and review contributions are indistinguishable from intermediate engineers.
Dampeners
Keeping this individual at junior level is a significant retention risk and a performance process failure.
Progression Signal
Immediate promotion is required; the performance system has not kept pace with their growth.
Business Impact
Impact
Delivering outsized data platform value; operating effectively as an intermediate data engineer at a junior cost.
Recognised across the analytics function as a driver of data quality and platform reliability.
Examples
Named by analytics stakeholders as a key reason data reliability had improved significantly in their domain.
Dampeners
This situation is a process failure; promotion action should be immediate.
Progression Signal
Promotion resolves the mismatch; continued data engineering growth expected to accelerate post-promotion.