> I felt like that I should've got promoted after reporting those issues, especially since I found them within my frist two weeks.
> Even though I meet the qualifcations.
Your pattern of reasoning about your professional past seems to involve saying what you think "should have" happened as a result of your presupposition of deservedness, rather than considering how your approach might have effected the outcome negatively.
For example, finding a security bug in the first few weeks of a job is usually not a basis for promotion anywhere. Promotion is usually based on consistent dedication to improving something for the company or team over a long period of time.
This takes not only technical, but also emotional and interpersonal skills and awareness as others have mentioned, and the ability to balance your immediate personal desire for a promotion (which we all share) with the goals of the team or organization.
Basically, to progress in your career, you need both the grit to put your nose to the grindstone to stick through the tough part of any job, while also being open to others both in the technical and social sense, and developing a mindset of gratitude for all experiences, which is essential for learning.
Many of us have taken jobs we don't love, or that aren't at A-list employers, while simultaneously laying the groundwork for our personal growth. I spent a summer when in college literally filing the metal cases of networking equipment at a no-name network switch maker - effectively manual labor.
Sure, it wasn't a Google internship, but it sure taught me a lot about work, and I got to talk to some great network hardware and software engineers about their jobs. I work at Google today and sometimes when I have to do something that tests my need for instant gratification, I remember that experience and I'm grateful that I had it.
> I felt like that I should've got promoted after reporting those issues, especially since I found them within my frist two weeks.
> Even though I meet the qualifcations.
Your pattern of reasoning about your professional past seems to involve saying what you think "should have" happened as a result of your presupposition of deservedness, rather than considering how your approach might have effected the outcome negatively.
For example, finding a security bug in the first few weeks of a job is usually not a basis for promotion anywhere. Promotion is usually based on consistent dedication to improving something for the company or team over a long period of time.
This takes not only technical, but also emotional and interpersonal skills and awareness as others have mentioned, and the ability to balance your immediate personal desire for a promotion (which we all share) with the goals of the team or organization.
Basically, to progress in your career, you need both the grit to put your nose to the grindstone to stick through the tough part of any job, while also being open to others both in the technical and social sense, and developing a mindset of gratitude for all experiences, which is essential for learning.
Many of us have taken jobs we don't love, or that aren't at A-list employers, while simultaneously laying the groundwork for our personal growth. I spent a summer when in college literally filing the metal cases of networking equipment at a no-name network switch maker - effectively manual labor.
Sure, it wasn't a Google internship, but it sure taught me a lot about work, and I got to talk to some great network hardware and software engineers about their jobs. I work at Google today and sometimes when I have to do something that tests my need for instant gratification, I remember that experience and I'm grateful that I had it.