This document defines expectations for Engineers at FlowFuse.
It exists to:
- Clarify what strong performance looks like
- Define scope at each level
- Support evidence-based quarterly reviews
- Make promotion decisions predictable and defensible
This applies to:
- Software Engineers, including the CTO when operating as an engineer
- Infrastructure Engineers
Levels reflect scope of ownership and influence. "Meets Expectations" at a level represents strong performance. promotion requires sustained demonstration of next-level behaviors.
All Engineers are evaluated across five dimensions.
Quality, maintainability, and soundness of engineering work.
Examples:
- Low rate of bugs, reverts, or rework in shipped code
- Fast turnaround for other engineers to safely extend or modify the code, without needing the original author
- Security and reliability posture, evidenced by incident and vulnerability history in owned areas
- Testing that catches issues before they reach production
- Documentation clear enough to measurably reduce onboarding or support time
Reliable delivery of engineering outcomes that produce real, traceable value — whether or not that value is visible to end users.
Examples:
- Delivering committed work predictably, so downstream teams and customers can rely on the timeline
- Converting ambiguity into plans that ship and hold up in production
- Impact that's traceable to an outcome — adoption, reliability, or support load for user-facing work; incidents prevented, risk retired, or capacity unlocked for work that isn't
- Following through on commitments without needing to be chased
Understanding and improving the broader engineering system — in line with FlowFuse's "think big picture" value: it's not just "your" issue once it ships, the whole system carries the consequences of how it was built.
Examples:
- Cross-service dependency risks caught before they cause an incident, not identified during the retro
- Architectural risk flagged with enough lead time to actually act on it, not surfaced after the fact
- Operational patterns that measurably reduce recurring toil or on-call load
- Design decisions that hold up without rework across multiple future releases, not just the next one
- Reducing systemic friction, measured by fewer repeat issues in the same area
Working effectively with other engineers and amplifying impact through others.
Examples:
- Clear technical communication
- Constructive code review
- Mentorship
- Cross-team alignment
Responsible contribution to the health of our open source and user ecosystem.
Examples:
- Professional engagement in public channels
- Addressing community-reported issues in owned areas
- Improving documentation and error clarity
- Reducing recurring ecosystem friction
Community work is considered real work and should be planned and visible.
Levels represent increasing scope of ownership and influence.
Scope: Well-defined tasks within a team.
Demonstrates:
- Delivers assigned work reliably with guidance
- Provides honest time estimates with guidance and flags when work is at risk of slipping
- Produces maintainable work aligned with standards
- Understands local systems and dependencies
- Engages constructively in feedback
- Acts professionally in ecosystem interactions
Promotion to Level 2 requires:
- Independent ownership of moderately complex work
- Reduced need for day-to-day oversight
- Able to scope, plan, and flag risk without step-by-step direction,
Scope: Features, services, or infrastructure components.
Demonstrates:
- Independently scopes and delivers moderately complex work
- Estimates moderately complex work accurately; raises blockers proactively rather than at deadline
- Anticipates and mitigates local risks
- Improves local system quality
- Participates meaningfully in planning and estimation
- Handles ecosystem issues in owned areas
Promotion to Level 3 requires:
- Ownership of complex systems or multi-sprint initiatives
- Evidence of mentoring or influence beyond individual contribution
Scope: Major systems, critical infrastructure domains, or multi-person initiatives.
A Level 3 engineer operates as a force multiplier within Engineering.
Demonstrates:
- Independently designs and delivers complex systems or initiatives
- Maintains reliable throughput within planned capacity and improves estimation
- Owns a meaningful engineering domain, whether application, infrastructure, or operational
- Anticipates cross-team impact and prevents downstream issues
- Elevates the quality of others through code review and mentorship
- Improves architectural or operational patterns
- Identifies recurring ecosystem or reliability friction and drives reduction
Level 3 performance requires sustained domain-level impact, not isolated strong projects. For most engineers, Level 3 is the ceiling — sustained performance here is a strong, complete career at FlowFuse, and most engineers will not promote beyond this point.
Promotion to Level 4 requires:
- Sustained cross-team technical influence
- Strategic impact beyond a single domain
Scope: Multiple teams or core engineering domains.
Demonstrates:
- Shapes technical direction across teams
- Models and reinforces commitment discipline across team; identifies systemic patterns in estimation drift and drives structural fixes
- Drives systemic reliability or architectural improvements
- Influences roadmap through engineering insight
- Leads resolution of major production or architectural challenges
- Strengthens company credibility in the engineering ecosystem
Promotion to Level 5 requires:
- Multi-quarter strategic impact
- Ensures the organization maintains healthy throughput and delivery trust at scale; sets the standard for how engineering commitments are made and communicated company-wide
- Organization-level engineering leadership
Scope: Company-wide engineering direction.
Demonstrates:
- Defines multi-year engineering strategy and is accountable for its outcomes
- Strategy is judged by what it produces, not by the act of proposing it
- Makes high-impact architectural tradeoffs
- Elevates engineering standards across the organization
- Elevates team throughput across the organization
- Represents FlowFuse engineering at an industry level
- Drives operational excellence company-wide
This level is rare and not time-based.
Each quarter includes an informal mid-point check-in between the engineer and manager. The goal is to identify early whether anything is off-track and course-correct before the quarter closes — not to evaluate, but to make sure no one is surprised.
Quarterly reviews are informal. The manager leads evidence gathering ahead of each conversation, drawing on:
- Completed issues and pull requests (including review comments)
- Geekbot standup history
- Relevant Slack threads and direct messages
- Notes logged during the quarter
The manager synthesizes this into a draft evaluation across the five core dimensions before the review conversation.
In the review itself, the engineer and manager go through the evaluation together. The goal is to make sure nothing meaningful was missed and that the engineer feels accurately and well represented. Engineers should come prepared to flag anything they want to add or clarify.
Annual reviews are formal and synthesize evidence from all four quarters of the year.
The manager evaluates sustained scope and impact across dimensions, identifies patterns, and uses this as the basis for compensation and promotion decisions.
- Your manager is doing the legwork. Both the engineer and manager flag notable things during the quarter as they happen.
- Reviews are based on observable behavior and documented impact. Impact that shows up as reliability, stability, or prevented problems counts alongside shipped work.
- The review conversation is collaborative. If something feels off, say so.