> 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 A responsible team would not le

> 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 A responsible team would not let juniors have that much impact. They would monitor you closely, review your work and make sure the mistakes you make don't afftect the team much. Having said that, a lot of the teams are growing and learning and maybe they end up learning things from their experience with you. Have they done something about preventing such problems from future junior hires? Have you suggested anything on how to prevent it in the future? > When I first joined I struggled to even know how to start things. Why do you think you were supposed to know that? They should have explained or one of the seniors should have work closely together with you and helped you along the way. It seems that the big part of the probelm is the teams lack of experience with juniors. You didn't mention how big the team is but if they are too small they may not have the resources to hire juniors and give them the environment to grow. I have written on the topic before: https://news.ycombinator.com/item?id=30464521 https://news.ycombinator.com/item?id=30464521 > no one else on the team had done anything like before, so at times I couldn't even ask the senior devs for help Not true. You should have asked them to help you figure things out anyway. Of course you shouldn't get them to do all of your work but what you should do is do your research on a few different ways on how you think you should start based on your understanding of the problem and try to explain your thinking process to a senior in a short session. If they think that is OK, you can go ahead and do some work and explain it again in a couple of days how it went and again explain how you intend to proceed. They should have thought about this before they decided they will hire a junior... but it's never too late. > senior engineers also seem to assume I know more than I do Do they assume that or do you let them assume that by pretending that you know everything and don't have to ask anything about anything? > an experienced engineer joined the same time I did and is doing great Juniors have to be treated differently. If the team doesn't have a different processes for a junior, it's their fault. You can make it clear to them by communicating more. > The problem is at this point I have been on the team too long to ask any basic questions You ask what you don't understand at any point. If you don't, you just keep adding to the problem. Imagine you have been in the team for 3 years and still don't know what you need to know because you didn't ask now. That would be much worse, don't you think? > one of the senior engineers even pointed out they shouldn't be helping me with certain processes at this point Avoid that one and ask someone else. > I know imposter syndrome is a thing, I don't think it is. I have written about it here: https://news.ycombinator.com/item?id=30924557 https://news.ycombinator.com/item?id=30924557 > I am actively slowing the team down or causing problem As I have indicated before, a good team would not let juniors have that much control. Of course, hiring a junior comes with extra costs (mostly that of senior developers' time with them) but it is supposed to pay off by giving the team some useful value... and some of the pay off will come later as you gain experience (and hopefully stay in the company). > I take a really long time when finishing stories unless one of the seniors is giving input. Exactly! They should never give a junior a task unless there is a senior available to assist them. In fact, they should give the senior the full responsibility of the task and give him you as a resource that they can make use of so that they can spend more time on their primary task which may be more important. > Its hard to imagine anyone who is good at engineering delaying a teams release and causing problems Everyone makes mistakes like that. Maybe different kinds or classes of mistakes as they gain more experience but there will always be mistakes and problems. > my manager has been gone since December So you have nobody to report to since then? Why don't they give someone else this responsibility? > Should I be writing reminders to myself to always double check everything? You can't check if you don't know what to check. A senior should be reviewing all your work. > Should I write down the steps to every process? For whom? Who is going to read this? What you should do is talk to whoever you are supposed to report to... and tell them how you have not been as productive as you have wanted to... and that you think that it would be better for you and the team if there was a senior available for you to assist you with every task until you feel more comfortable to be more autonomous. It seems the team isn't proactively helping you so it is up to you to proactively seek help if you are going to make progress. You should aslo ask for a monthly one-on-one meeting with your manager (or who is supposed to take that responsibility when he's gone) where you can discuss these issues.