> but it is clear that I am not seen as reliable and definitely not known for completing things fast.
That's what a good company expects from Junior SWE's, what is your manager's expectations? (it should be clear and explicit)
> and I made 2 costly mistake back-to-back that is pushing back the release of a production feature by a while month at this point.
That's what qualified seniors expect from Junior SWE's, where was your team?
> I was sometimes assigned stories no one else on the team had done anything like before, so at times I couldn't even ask the senior devs for help.
Seniors aren't good because they have done specific tasks before. They're good because they're able to adapt their wide past experiences to new unknown ones. Perhaps you don't have a good team?
I generally advise my Juniors that their main job is to 1) Invest deeply in learning, RTFM for everything they touch, do laborious but educational things (eg: read the diffs before vendoring a new version and look at what code will be affected in our current impl). The compounding interest of learning lots early on is worth so much more than learning something late in career.
That's what a good company expects from Junior SWE's, what is your manager's expectations? (it should be clear and explicit)
> and I made 2 costly mistake back-to-back that is pushing back the release of a production feature by a while month at this point.
That's what qualified seniors expect from Junior SWE's, where was your team?
> I was sometimes assigned stories no one else on the team had done anything like before, so at times I couldn't even ask the senior devs for help.
Seniors aren't good because they have done specific tasks before. They're good because they're able to adapt their wide past experiences to new unknown ones. Perhaps you don't have a good team?
I generally advise my Juniors that their main job is to 1) Invest deeply in learning, RTFM for everything they touch, do laborious but educational things (eg: read the diffs before vendoring a new version and look at what code will be affected in our current impl). The compounding interest of learning lots early on is worth so much more than learning something late in career.