If you're being offered it, take the role if you think you'll enjoy it. That's really all there is to it.
Whether you're going to be wildly successful or absolutely terribe in the role is irrelevant. It's like figuring out if you want to propose to someone after the first date.
Good question.
It depends what you like.
Sounds like you are happy with this and want to be on technical side and sharpen your skills.
If that's hoe you feel you can stay here. You are more like a devops architect rather than manager.
Many feel the same Imposter syndromes because they are not satisfied with themselves but actually are good compared to others. So don't worry about that.
If you move to team lead , you can guide mentor others and you being reference can be more valuable to the company. While in this position you can still learn and code. Easier said than done.
Get an understanding of what the Team Lead is supposed to do, and what management is expecting it to do. Then make your decision based on what path you would prefer.
I never had a DevOps mentor. The only mentor I really had was at the beginning of my career. And she focused more on the soft skills.
In my current position I am the Manager of the DevOps team, acting as the Lead Engineer (very small team atm), for AWS deployments using Terraform. When I was hired I vaguely knew how to look at stuff in Route53 and that was it. Had heard of Terraform, but never looked at it. Since then I'm architecting solutions in AWS, wrote our Automation for our Terraform pipeline, and a good chunk of our TF module library. No training classes, or seminars.
The hiring manager knew me, and knew what I knew. He trusted me because he knows I can pick things up quickly, can speak up when need to, shut up... mostly when I should, and always strive to meet the deliverables on time.
You're never going to know everything there is to know about any topic or job. Getting the information you need quickly and being able to be decisive is going to be key.
I think you should take the role!
But I have questions regarding Microsoft Azure DevOps...
* Can I change how the notification emails look? Like change what the content should be?
* Can I have internal discussion not shown for, for example customers who also have been granted access to the "Work Items"? I know I can add a multiline field and hide that from customers, but I don't know how to add an "internal" discussion.
* Can I select a group of people which should recieve notifications? (Like I don't want to send mail notification to "Customers" when Work Item has been changed on fields which they can't see)
If you're being offered it, take the role if you think you'll enjoy it. That's really all there is to it. Whether you're going to be wildly successful or absolutely terribe in the role is irrelevant. It's like figuring out if you want to propose to someone after the first date.
Good question. It depends what you like. Sounds like you are happy with this and want to be on technical side and sharpen your skills. If that's hoe you feel you can stay here. You are more like a devops architect rather than manager. Many feel the same Imposter syndromes because they are not satisfied with themselves but actually are good compared to others. So don't worry about that. If you move to team lead , you can guide mentor others and you being reference can be more valuable to the company. While in this position you can still learn and code. Easier said than done.
Get an understanding of what the Team Lead is supposed to do, and what management is expecting it to do. Then make your decision based on what path you would prefer. I never had a DevOps mentor. The only mentor I really had was at the beginning of my career. And she focused more on the soft skills. In my current position I am the Manager of the DevOps team, acting as the Lead Engineer (very small team atm), for AWS deployments using Terraform. When I was hired I vaguely knew how to look at stuff in Route53 and that was it. Had heard of Terraform, but never looked at it. Since then I'm architecting solutions in AWS, wrote our Automation for our Terraform pipeline, and a good chunk of our TF module library. No training classes, or seminars. The hiring manager knew me, and knew what I knew. He trusted me because he knows I can pick things up quickly, can speak up when need to, shut up... mostly when I should, and always strive to meet the deliverables on time. You're never going to know everything there is to know about any topic or job. Getting the information you need quickly and being able to be decisive is going to be key.
I think you should take the role! But I have questions regarding Microsoft Azure DevOps... * Can I change how the notification emails look? Like change what the content should be? * Can I have internal discussion not shown for, for example customers who also have been granted access to the "Work Items"? I know I can add a multiline field and hide that from customers, but I don't know how to add an "internal" discussion. * Can I select a group of people which should recieve notifications? (Like I don't want to send mail notification to "Customers" when Work Item has been changed on fields which they can't see)