A career lesson many engineers learn too late: a 1:1 with your manager is not therapy, not a private investigation, and not a place where the criteria change every week.
It should be a navigation system: what is expected, where the gap is, what the next step is, and how progress will be measured.
A recent ExperiencedDevs discussion about uncomfortable manager 1:1s captured a pattern I have seen in many engineering careers: vague promotion promises, personal questions that do not belong in the conversation, unfair comparisons, and moving criteria that leave the engineer trying to guess what game they are playing.
When that happens, the mistake good engineers often make is trying to solve managerial noise with more performance: more hours, more ownership, more proof. But a clarity problem is not always solved by effort. Sometimes it is solved by documentation and boundaries.
When a 1:1 Stops Being Useful
The warning sign is not one difficult conversation. Real feedback can be uncomfortable. The warning sign is when the conversation stops producing clear operating information.
If every 1:1 leaves you with a different interpretation of your level, your promotion path, or your perceived performance, then the meeting is no longer helping you navigate. It is creating uncertainty.
That uncertainty matters because engineering careers compound through visible scope, trusted ownership, and clear feedback. I wrote about this in the context of career leverage in smaller engineering organizations: the title is less important than the learning, ownership, and story you can explain later.
Why More Effort Is Not Always the Answer
Engineers are trained to respond to ambiguity with output. If something is unclear, we work harder, ship more, document more, take another incident, own another system, or become the person who quietly holds the team together.
That can work when the gap is technical. It does not work when the gap is managerial clarity. If the criteria are not written, if the approval path is unclear, or if the goalposts move after each conversation, additional effort can become invisible labor.
This is similar to process design in engineering teams. When workflows change but the process does not, the old signals start lying. That is why engineering process needs to adapt when workflows change before trusting the metrics.
A Practical Checklist for Manager 1:1s
Here is the checklist I would use if a manager relationship starts to feel vague, destabilizing, or too personal:
- Move everything into written criteria. Ask: what exactly is required for the next level, who approves it, and on what timeline?
- Summarize every 1:1 in writing. Not aggressively. Professionally: “Here is what I understood, here are the actions, and here are the criteria.”
- Separate professional feedback from irrelevant personal questions. Salary, age, private life, or other unrelated topics do not need to become part of performance discussion.
- Build support outside the direct manager. A tech lead, another manager, HR, or an external mentor can help calibrate reality without turning the situation into drama.
- Stop measuring your professional value by one bad conversation. A poor manager can damage confidence. They do not define your capability.
- Prepare options quietly. A difficult job market does not mean there is no strategy. It means the strategy has to be staged.
What Leaders Should Take From This
This is not only advice for individual contributors. It is also a warning for engineering leaders. If your 1:1s leave people confused about expectations, promotions, or trust, you are not giving feedback. You are increasing organizational drag.
Good management creates evidence. It makes expectations inspectable. It gives people a fair way to understand whether they are improving. It also protects the company: vague people processes eventually show up in retention, hiring reputation, and the quality of internal signals. That is why hiring signals and business intelligence matters beyond HR dashboards.
Your career needs clear feedback, not a guessing game. If after several conversations there are no criteria, no documentation, and no basic respect, the issue is no longer just performance. It is the work environment.
Context: this article was inspired by a practitioner discussion on ExperiencedDevs, then expanded into a practical engineering-career framework.
Originally posted on LinkedIn: https://www.linkedin.com/feed/update/urn:li:activity:7469600807689056256/
