7 Signs You're Underperforming as an Engineer

The piece argues that self-serving bias hides low performance from the person doing it, so it offers a checklist to self-assess instead of waiting for a manager to flag it. Each sign comes with warning indicators and an action to take.

After the checklist, it lays out a process for fixing what the self-assessment turns up: separate personal causes from team-level ones, ask managers and peers for specific feedback, then set a plan with measurable goals and regular check-ins.

Fichamento

#

• Sitting on blockers for days instead of raising them early is framed as a habit common among junior engineers; escalating isn’t weakness, it’s a way to keep project momentum.
• Consistently picking simpler tasks and avoiding hard ones stalls growth; the underlying cause can be domain mismatch, low motivation, or burnout.
• Superficial or absent code reviews signal disengagement from teamwork, not just a time problem; reviews are also a way to learn and build domain knowledge.
• Frequently missing deadlines points to poor task estimation or workload management, not just external circumstances.
• Work that’s invisible to stakeholders (managers can’t describe what you do, your name doesn’t come up in updates) calls for choosing higher-impact tasks and keeping a record of accomplishments.
• Always waiting for instructions instead of checking the backlog or proposing improvements is contrasted with proactive engineers, who don’t wait for tasks to be assigned.
• Getting the same feedback repeatedly across review cycles without an action plan means the feedback isn’t being acted on, not that it wasn’t heard.
• The recommended fix: identify causes (personal and team-level), get specific feedback from managers and peers, then build a plan with measurable goals and scheduled check-ins.