Younger junior colleague who behaves like the bossVery wary boss keeps the team away from empowerment, how to deal with it?Conflict with a colleague: How to explain the situation when askedHow do you balance career growth and technology relevance with obtaining years of experience in one workplace?How do I maintain a healthy relationship with a colleague who is much more experienced than I am?Teammate Excludes Me and doesn't give me infoIs this a case of bad team management, or am I taking this up wrong?How to deal with relatively technically incompetent coworker?How to deal with a colleague who is being aggressive?
Distance vs a distance
Using Terminal` (ASCII plots) in Wolfram 12
Will the size of Bitcoin core full-node be too big to run on a normal computer?
Paper status "Accept with Shepherd". What does it really mean?
Is the value of a probability density function for a given input a point, a range, or both?
Displaying characteristics of the Hero in a console game
Pass a bash variable to python script
What's the current zodiac?
Can you take an Immortal Phoenix out of the game?
Is Schrodinger's Cat itself an observer?
Can digital computers understand infinity?
Why are Starfleet vessels designed with nacelles so far away from the hull?
Did smallpox emerge in 1580?
Is there a historical explanation as to why the USA people are so litigious compared to France?
Where is the 'zone of reversed commands...'?
How many people are there?
Where does the tea come from?
Setting Pull Up/Pull Down mode doesn't work (mostly)
SSD or HDD for server
What is a recommended strategy on exercises in a mathematical textbook at graduate level?
What is the name for a fluid transition between two tones? When did it first appear?
Can it be improved? Help me to fix this code
Ginger Baker dead: Why is he been called the most dangerous drummer?
Island of Knights, Knaves, Spies
Younger junior colleague who behaves like the boss
Very wary boss keeps the team away from empowerment, how to deal with it?Conflict with a colleague: How to explain the situation when askedHow do you balance career growth and technology relevance with obtaining years of experience in one workplace?How do I maintain a healthy relationship with a colleague who is much more experienced than I am?Teammate Excludes Me and doesn't give me infoIs this a case of bad team management, or am I taking this up wrong?How to deal with relatively technically incompetent coworker?How to deal with a colleague who is being aggressive?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I would be grateful for advice on this situation. I'm a senior developer with about 10 years of experience. Until recently my team consisted of myself, my manager, and a staff engineer. We've been working together for about a year. We are all around the same age.
A few months ago we were joined by a new mid level developer. He is bright, clever and confident. He has strong engineering skills and he knows it. He has about 2 years professional experience, and is about 15 years younger than us.
I feel he is trying to assume the dominant position in the team. He behaves like he's the boss. He issues instructions, points out our mistakes, challenges our depth of knowledge.
A couple of specific examples. In a team meeting telling me that it's my turn to run one of our processes, in effect trying to assign me work. Insisting we as a team adopt his preferred continuous integration pipeline, and not taking on board our experience.
My manager and and the staff engineer are gentle people who just seem to go along with it, whereas I feel stressed and threatened. I've been pushing back on this behaviour, refusing to implement changes he wants on my pull requests. I feel like we are heading towards a confrontation.
I'm from the United Kingdom, and this colleague is from the United States. I've not spoken to either my manager or the staff engineer about the problem, as I feel it is at least partly my manager's fault, and that I would be implicitly criticising him.
I would be grateful on how to handle this situation.
communication management software-development
add a comment
|
I would be grateful for advice on this situation. I'm a senior developer with about 10 years of experience. Until recently my team consisted of myself, my manager, and a staff engineer. We've been working together for about a year. We are all around the same age.
A few months ago we were joined by a new mid level developer. He is bright, clever and confident. He has strong engineering skills and he knows it. He has about 2 years professional experience, and is about 15 years younger than us.
I feel he is trying to assume the dominant position in the team. He behaves like he's the boss. He issues instructions, points out our mistakes, challenges our depth of knowledge.
A couple of specific examples. In a team meeting telling me that it's my turn to run one of our processes, in effect trying to assign me work. Insisting we as a team adopt his preferred continuous integration pipeline, and not taking on board our experience.
My manager and and the staff engineer are gentle people who just seem to go along with it, whereas I feel stressed and threatened. I've been pushing back on this behaviour, refusing to implement changes he wants on my pull requests. I feel like we are heading towards a confrontation.
I'm from the United Kingdom, and this colleague is from the United States. I've not spoken to either my manager or the staff engineer about the problem, as I feel it is at least partly my manager's fault, and that I would be implicitly criticising him.
I would be grateful on how to handle this situation.
communication management software-development
Is there a valid technical reason why you decided to refuse his changes on your PR? Is he acting as a reviewer asking for changes before he accepts merges PR? Could you give an example of how 'he challenges the depth of your knowledge'? I want to differentiate between his behaviour and optimal approach to coding.
– Konrad
3 hours ago
The suggestions he makes on PRs are fine, the problem is the wording, as they are written as if he is giving me an order. This is also the way he speaks in meetings. By challenging the depth of my knowledge, I mean that he for example asks me a question on a piece of technology, followed by a series of questions more like he's interviewing me.
– GeorgeX
3 hours ago
thanks, that’s useful. Could be it he genuinely doesn’t know and asks honestly. Situation where people are afraid to “lose face” and ask is bad from a dev perspective. Good products come form collaboration where folk are not afraid to bounce ideas of each other and ask, even at time silly, questions. Could it be that the guy is just curious?
– Konrad
3 hours ago
No, I'm certain he's behaving like he's the manager, he's the most junior member of the team and he's telling us what to do, he is trying to dominate
– GeorgeX
2 hours ago
add a comment
|
I would be grateful for advice on this situation. I'm a senior developer with about 10 years of experience. Until recently my team consisted of myself, my manager, and a staff engineer. We've been working together for about a year. We are all around the same age.
A few months ago we were joined by a new mid level developer. He is bright, clever and confident. He has strong engineering skills and he knows it. He has about 2 years professional experience, and is about 15 years younger than us.
I feel he is trying to assume the dominant position in the team. He behaves like he's the boss. He issues instructions, points out our mistakes, challenges our depth of knowledge.
A couple of specific examples. In a team meeting telling me that it's my turn to run one of our processes, in effect trying to assign me work. Insisting we as a team adopt his preferred continuous integration pipeline, and not taking on board our experience.
My manager and and the staff engineer are gentle people who just seem to go along with it, whereas I feel stressed and threatened. I've been pushing back on this behaviour, refusing to implement changes he wants on my pull requests. I feel like we are heading towards a confrontation.
I'm from the United Kingdom, and this colleague is from the United States. I've not spoken to either my manager or the staff engineer about the problem, as I feel it is at least partly my manager's fault, and that I would be implicitly criticising him.
I would be grateful on how to handle this situation.
communication management software-development
I would be grateful for advice on this situation. I'm a senior developer with about 10 years of experience. Until recently my team consisted of myself, my manager, and a staff engineer. We've been working together for about a year. We are all around the same age.
A few months ago we were joined by a new mid level developer. He is bright, clever and confident. He has strong engineering skills and he knows it. He has about 2 years professional experience, and is about 15 years younger than us.
I feel he is trying to assume the dominant position in the team. He behaves like he's the boss. He issues instructions, points out our mistakes, challenges our depth of knowledge.
A couple of specific examples. In a team meeting telling me that it's my turn to run one of our processes, in effect trying to assign me work. Insisting we as a team adopt his preferred continuous integration pipeline, and not taking on board our experience.
My manager and and the staff engineer are gentle people who just seem to go along with it, whereas I feel stressed and threatened. I've been pushing back on this behaviour, refusing to implement changes he wants on my pull requests. I feel like we are heading towards a confrontation.
I'm from the United Kingdom, and this colleague is from the United States. I've not spoken to either my manager or the staff engineer about the problem, as I feel it is at least partly my manager's fault, and that I would be implicitly criticising him.
I would be grateful on how to handle this situation.
communication management software-development
communication management software-development
asked 3 hours ago
GeorgeXGeorgeX
679 bronze badges
679 bronze badges
Is there a valid technical reason why you decided to refuse his changes on your PR? Is he acting as a reviewer asking for changes before he accepts merges PR? Could you give an example of how 'he challenges the depth of your knowledge'? I want to differentiate between his behaviour and optimal approach to coding.
– Konrad
3 hours ago
The suggestions he makes on PRs are fine, the problem is the wording, as they are written as if he is giving me an order. This is also the way he speaks in meetings. By challenging the depth of my knowledge, I mean that he for example asks me a question on a piece of technology, followed by a series of questions more like he's interviewing me.
– GeorgeX
3 hours ago
thanks, that’s useful. Could be it he genuinely doesn’t know and asks honestly. Situation where people are afraid to “lose face” and ask is bad from a dev perspective. Good products come form collaboration where folk are not afraid to bounce ideas of each other and ask, even at time silly, questions. Could it be that the guy is just curious?
– Konrad
3 hours ago
No, I'm certain he's behaving like he's the manager, he's the most junior member of the team and he's telling us what to do, he is trying to dominate
– GeorgeX
2 hours ago
add a comment
|
Is there a valid technical reason why you decided to refuse his changes on your PR? Is he acting as a reviewer asking for changes before he accepts merges PR? Could you give an example of how 'he challenges the depth of your knowledge'? I want to differentiate between his behaviour and optimal approach to coding.
– Konrad
3 hours ago
The suggestions he makes on PRs are fine, the problem is the wording, as they are written as if he is giving me an order. This is also the way he speaks in meetings. By challenging the depth of my knowledge, I mean that he for example asks me a question on a piece of technology, followed by a series of questions more like he's interviewing me.
– GeorgeX
3 hours ago
thanks, that’s useful. Could be it he genuinely doesn’t know and asks honestly. Situation where people are afraid to “lose face” and ask is bad from a dev perspective. Good products come form collaboration where folk are not afraid to bounce ideas of each other and ask, even at time silly, questions. Could it be that the guy is just curious?
– Konrad
3 hours ago
No, I'm certain he's behaving like he's the manager, he's the most junior member of the team and he's telling us what to do, he is trying to dominate
– GeorgeX
2 hours ago
Is there a valid technical reason why you decided to refuse his changes on your PR? Is he acting as a reviewer asking for changes before he accepts merges PR? Could you give an example of how 'he challenges the depth of your knowledge'? I want to differentiate between his behaviour and optimal approach to coding.
– Konrad
3 hours ago
Is there a valid technical reason why you decided to refuse his changes on your PR? Is he acting as a reviewer asking for changes before he accepts merges PR? Could you give an example of how 'he challenges the depth of your knowledge'? I want to differentiate between his behaviour and optimal approach to coding.
– Konrad
3 hours ago
The suggestions he makes on PRs are fine, the problem is the wording, as they are written as if he is giving me an order. This is also the way he speaks in meetings. By challenging the depth of my knowledge, I mean that he for example asks me a question on a piece of technology, followed by a series of questions more like he's interviewing me.
– GeorgeX
3 hours ago
The suggestions he makes on PRs are fine, the problem is the wording, as they are written as if he is giving me an order. This is also the way he speaks in meetings. By challenging the depth of my knowledge, I mean that he for example asks me a question on a piece of technology, followed by a series of questions more like he's interviewing me.
– GeorgeX
3 hours ago
thanks, that’s useful. Could be it he genuinely doesn’t know and asks honestly. Situation where people are afraid to “lose face” and ask is bad from a dev perspective. Good products come form collaboration where folk are not afraid to bounce ideas of each other and ask, even at time silly, questions. Could it be that the guy is just curious?
– Konrad
3 hours ago
thanks, that’s useful. Could be it he genuinely doesn’t know and asks honestly. Situation where people are afraid to “lose face” and ask is bad from a dev perspective. Good products come form collaboration where folk are not afraid to bounce ideas of each other and ask, even at time silly, questions. Could it be that the guy is just curious?
– Konrad
3 hours ago
No, I'm certain he's behaving like he's the manager, he's the most junior member of the team and he's telling us what to do, he is trying to dominate
– GeorgeX
2 hours ago
No, I'm certain he's behaving like he's the manager, he's the most junior member of the team and he's telling us what to do, he is trying to dominate
– GeorgeX
2 hours ago
add a comment
|
1 Answer
1
active
oldest
votes
GeorgeX, I worked about 40 years in a variety of organizations, with a spectrum of personalities, before I retired. I performed several times as the young colleague, and also as the experienced old one. You have my sympathy.
A young colleague's excessively clear understanding of his or her importance can be thoroughly annoying. It's important to bring it up with your boss and with the team at the your first opportunities. Talking it over with others will generate information for you and your coworkers. This will give all of you an opportunity to improve your approach.
The age differential and the cultural legacy of different nations may generate some friction, though coping with these will strengthen you, the young colleague and the team. Some people have personality quirks they may not intend or even have awareness of that introduce frictions, too. Keep in mind that frictions are part of the social experience of working in groups of humans. It's easy to diagnose the problem incorrectly as caused by these conditions. You must cope with these things in collaboration. But, if that's all you have, then you haven't figured out the trouble yet.
I suspect the true difficulty arises from inadequately understood agreements among the parties. Again, it's part of working in groups, but even employees who must do what the boss says will be more productive if they discuss and agree on overall situation, on strategy, on procedure, on methods, and task by task, whenever practical. There are more-or-less coercive conditions that give a person authority to command others. But well-understood, willing agreements can diminish the value of command authority and enable greater enthusiasm and productivity.
I suggest you take an approach something along these lines...
Start talking. You can't do this by email. Talk and listen. Don't wait to get all your facts straight. Be honest and courageous enough to be wrong about some of it.
First, talk with your boss. Describe your concerns. Say you want to discuss it with all the team within the next week. If you have a daily scrum, that's an ideal time. Be concerned to treat the young one well, and tell your boss that is your intention. Listen carefully to what your boss says.
If a meeting in the next few days isn't possible, gather those of your team that you can to discuss the matter.
When you meet with the young colleague, be courteous and kind and completely straightforward. Let him know candidly that you value his expertise and accomplishments. Tell him you are having trouble working with him. Tell him you need a better agreement with him and the team regarding how you work together. Shut up to give him a chance to respond while you listen carefully.
What happens next depends on your circumstances. Be always courteous and honest. Seek agreement.
Some optional reading you may find helpful:
All these are too wordy, in my opinion, but they contains nuggets of wisdom.
a. Peter F. Drucker, "The Essential Drucker: The Best of Sixty Years ..."
b. Roger Fisher, et al, "Getting to Yes"
c. William Ury, "Getting Past No" (sequel to "Getting to Yes")
Good luck.
New contributor
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f146103%2fyounger-junior-colleague-who-behaves-like-the-boss%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
GeorgeX, I worked about 40 years in a variety of organizations, with a spectrum of personalities, before I retired. I performed several times as the young colleague, and also as the experienced old one. You have my sympathy.
A young colleague's excessively clear understanding of his or her importance can be thoroughly annoying. It's important to bring it up with your boss and with the team at the your first opportunities. Talking it over with others will generate information for you and your coworkers. This will give all of you an opportunity to improve your approach.
The age differential and the cultural legacy of different nations may generate some friction, though coping with these will strengthen you, the young colleague and the team. Some people have personality quirks they may not intend or even have awareness of that introduce frictions, too. Keep in mind that frictions are part of the social experience of working in groups of humans. It's easy to diagnose the problem incorrectly as caused by these conditions. You must cope with these things in collaboration. But, if that's all you have, then you haven't figured out the trouble yet.
I suspect the true difficulty arises from inadequately understood agreements among the parties. Again, it's part of working in groups, but even employees who must do what the boss says will be more productive if they discuss and agree on overall situation, on strategy, on procedure, on methods, and task by task, whenever practical. There are more-or-less coercive conditions that give a person authority to command others. But well-understood, willing agreements can diminish the value of command authority and enable greater enthusiasm and productivity.
I suggest you take an approach something along these lines...
Start talking. You can't do this by email. Talk and listen. Don't wait to get all your facts straight. Be honest and courageous enough to be wrong about some of it.
First, talk with your boss. Describe your concerns. Say you want to discuss it with all the team within the next week. If you have a daily scrum, that's an ideal time. Be concerned to treat the young one well, and tell your boss that is your intention. Listen carefully to what your boss says.
If a meeting in the next few days isn't possible, gather those of your team that you can to discuss the matter.
When you meet with the young colleague, be courteous and kind and completely straightforward. Let him know candidly that you value his expertise and accomplishments. Tell him you are having trouble working with him. Tell him you need a better agreement with him and the team regarding how you work together. Shut up to give him a chance to respond while you listen carefully.
What happens next depends on your circumstances. Be always courteous and honest. Seek agreement.
Some optional reading you may find helpful:
All these are too wordy, in my opinion, but they contains nuggets of wisdom.
a. Peter F. Drucker, "The Essential Drucker: The Best of Sixty Years ..."
b. Roger Fisher, et al, "Getting to Yes"
c. William Ury, "Getting Past No" (sequel to "Getting to Yes")
Good luck.
New contributor
add a comment
|
GeorgeX, I worked about 40 years in a variety of organizations, with a spectrum of personalities, before I retired. I performed several times as the young colleague, and also as the experienced old one. You have my sympathy.
A young colleague's excessively clear understanding of his or her importance can be thoroughly annoying. It's important to bring it up with your boss and with the team at the your first opportunities. Talking it over with others will generate information for you and your coworkers. This will give all of you an opportunity to improve your approach.
The age differential and the cultural legacy of different nations may generate some friction, though coping with these will strengthen you, the young colleague and the team. Some people have personality quirks they may not intend or even have awareness of that introduce frictions, too. Keep in mind that frictions are part of the social experience of working in groups of humans. It's easy to diagnose the problem incorrectly as caused by these conditions. You must cope with these things in collaboration. But, if that's all you have, then you haven't figured out the trouble yet.
I suspect the true difficulty arises from inadequately understood agreements among the parties. Again, it's part of working in groups, but even employees who must do what the boss says will be more productive if they discuss and agree on overall situation, on strategy, on procedure, on methods, and task by task, whenever practical. There are more-or-less coercive conditions that give a person authority to command others. But well-understood, willing agreements can diminish the value of command authority and enable greater enthusiasm and productivity.
I suggest you take an approach something along these lines...
Start talking. You can't do this by email. Talk and listen. Don't wait to get all your facts straight. Be honest and courageous enough to be wrong about some of it.
First, talk with your boss. Describe your concerns. Say you want to discuss it with all the team within the next week. If you have a daily scrum, that's an ideal time. Be concerned to treat the young one well, and tell your boss that is your intention. Listen carefully to what your boss says.
If a meeting in the next few days isn't possible, gather those of your team that you can to discuss the matter.
When you meet with the young colleague, be courteous and kind and completely straightforward. Let him know candidly that you value his expertise and accomplishments. Tell him you are having trouble working with him. Tell him you need a better agreement with him and the team regarding how you work together. Shut up to give him a chance to respond while you listen carefully.
What happens next depends on your circumstances. Be always courteous and honest. Seek agreement.
Some optional reading you may find helpful:
All these are too wordy, in my opinion, but they contains nuggets of wisdom.
a. Peter F. Drucker, "The Essential Drucker: The Best of Sixty Years ..."
b. Roger Fisher, et al, "Getting to Yes"
c. William Ury, "Getting Past No" (sequel to "Getting to Yes")
Good luck.
New contributor
add a comment
|
GeorgeX, I worked about 40 years in a variety of organizations, with a spectrum of personalities, before I retired. I performed several times as the young colleague, and also as the experienced old one. You have my sympathy.
A young colleague's excessively clear understanding of his or her importance can be thoroughly annoying. It's important to bring it up with your boss and with the team at the your first opportunities. Talking it over with others will generate information for you and your coworkers. This will give all of you an opportunity to improve your approach.
The age differential and the cultural legacy of different nations may generate some friction, though coping with these will strengthen you, the young colleague and the team. Some people have personality quirks they may not intend or even have awareness of that introduce frictions, too. Keep in mind that frictions are part of the social experience of working in groups of humans. It's easy to diagnose the problem incorrectly as caused by these conditions. You must cope with these things in collaboration. But, if that's all you have, then you haven't figured out the trouble yet.
I suspect the true difficulty arises from inadequately understood agreements among the parties. Again, it's part of working in groups, but even employees who must do what the boss says will be more productive if they discuss and agree on overall situation, on strategy, on procedure, on methods, and task by task, whenever practical. There are more-or-less coercive conditions that give a person authority to command others. But well-understood, willing agreements can diminish the value of command authority and enable greater enthusiasm and productivity.
I suggest you take an approach something along these lines...
Start talking. You can't do this by email. Talk and listen. Don't wait to get all your facts straight. Be honest and courageous enough to be wrong about some of it.
First, talk with your boss. Describe your concerns. Say you want to discuss it with all the team within the next week. If you have a daily scrum, that's an ideal time. Be concerned to treat the young one well, and tell your boss that is your intention. Listen carefully to what your boss says.
If a meeting in the next few days isn't possible, gather those of your team that you can to discuss the matter.
When you meet with the young colleague, be courteous and kind and completely straightforward. Let him know candidly that you value his expertise and accomplishments. Tell him you are having trouble working with him. Tell him you need a better agreement with him and the team regarding how you work together. Shut up to give him a chance to respond while you listen carefully.
What happens next depends on your circumstances. Be always courteous and honest. Seek agreement.
Some optional reading you may find helpful:
All these are too wordy, in my opinion, but they contains nuggets of wisdom.
a. Peter F. Drucker, "The Essential Drucker: The Best of Sixty Years ..."
b. Roger Fisher, et al, "Getting to Yes"
c. William Ury, "Getting Past No" (sequel to "Getting to Yes")
Good luck.
New contributor
GeorgeX, I worked about 40 years in a variety of organizations, with a spectrum of personalities, before I retired. I performed several times as the young colleague, and also as the experienced old one. You have my sympathy.
A young colleague's excessively clear understanding of his or her importance can be thoroughly annoying. It's important to bring it up with your boss and with the team at the your first opportunities. Talking it over with others will generate information for you and your coworkers. This will give all of you an opportunity to improve your approach.
The age differential and the cultural legacy of different nations may generate some friction, though coping with these will strengthen you, the young colleague and the team. Some people have personality quirks they may not intend or even have awareness of that introduce frictions, too. Keep in mind that frictions are part of the social experience of working in groups of humans. It's easy to diagnose the problem incorrectly as caused by these conditions. You must cope with these things in collaboration. But, if that's all you have, then you haven't figured out the trouble yet.
I suspect the true difficulty arises from inadequately understood agreements among the parties. Again, it's part of working in groups, but even employees who must do what the boss says will be more productive if they discuss and agree on overall situation, on strategy, on procedure, on methods, and task by task, whenever practical. There are more-or-less coercive conditions that give a person authority to command others. But well-understood, willing agreements can diminish the value of command authority and enable greater enthusiasm and productivity.
I suggest you take an approach something along these lines...
Start talking. You can't do this by email. Talk and listen. Don't wait to get all your facts straight. Be honest and courageous enough to be wrong about some of it.
First, talk with your boss. Describe your concerns. Say you want to discuss it with all the team within the next week. If you have a daily scrum, that's an ideal time. Be concerned to treat the young one well, and tell your boss that is your intention. Listen carefully to what your boss says.
If a meeting in the next few days isn't possible, gather those of your team that you can to discuss the matter.
When you meet with the young colleague, be courteous and kind and completely straightforward. Let him know candidly that you value his expertise and accomplishments. Tell him you are having trouble working with him. Tell him you need a better agreement with him and the team regarding how you work together. Shut up to give him a chance to respond while you listen carefully.
What happens next depends on your circumstances. Be always courteous and honest. Seek agreement.
Some optional reading you may find helpful:
All these are too wordy, in my opinion, but they contains nuggets of wisdom.
a. Peter F. Drucker, "The Essential Drucker: The Best of Sixty Years ..."
b. Roger Fisher, et al, "Getting to Yes"
c. William Ury, "Getting Past No" (sequel to "Getting to Yes")
Good luck.
New contributor
New contributor
answered 2 hours ago
SquarePowderSquarePowder
111 bronze badge
111 bronze badge
New contributor
New contributor
add a comment
|
add a comment
|
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f146103%2fyounger-junior-colleague-who-behaves-like-the-boss%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is there a valid technical reason why you decided to refuse his changes on your PR? Is he acting as a reviewer asking for changes before he accepts merges PR? Could you give an example of how 'he challenges the depth of your knowledge'? I want to differentiate between his behaviour and optimal approach to coding.
– Konrad
3 hours ago
The suggestions he makes on PRs are fine, the problem is the wording, as they are written as if he is giving me an order. This is also the way he speaks in meetings. By challenging the depth of my knowledge, I mean that he for example asks me a question on a piece of technology, followed by a series of questions more like he's interviewing me.
– GeorgeX
3 hours ago
thanks, that’s useful. Could be it he genuinely doesn’t know and asks honestly. Situation where people are afraid to “lose face” and ask is bad from a dev perspective. Good products come form collaboration where folk are not afraid to bounce ideas of each other and ask, even at time silly, questions. Could it be that the guy is just curious?
– Konrad
3 hours ago
No, I'm certain he's behaving like he's the manager, he's the most junior member of the team and he's telling us what to do, he is trying to dominate
– GeorgeX
2 hours ago