[endswapper]

I have to believe that you are intelligent even if you aren't smart about technical aspects. Otherwise, they would not have hired you, and given you the additional probationary time. Let that really sink in. You got a second chance at something most people don't get a first chance at (based on what you described).

I would start by answering two questions: 1) Why did they hire me? 2) Where can I provide the most value?

Apparently, they have a bunch of smart, capable people that are performing at a higher level than you in certain areas. Why, or where are you unique within in the organization, where are they going or trying to get to? These will get you started in answering the first questions objectively.

I don't think blindly focusing on fundamentals will make you competitive with people that are already well beyond you. And if you did become competitive on that level, so what? Do they need another person with the same skill-set?

This brings me to the second question. Other than LISTENING, strategically identifying their weaknesses is the best way to get started on question two. Providing practical solutions in the most efficient way possible is where you provide value. It's great when it doesn't have to be, but often the ideas that move things forward in a significant or meaningful way are cross-functional and collaborative. Perhaps it is part of the reason they can be so elusive. Based on your analyst background, this type of objective analysis might be the right starting point. From there you can drill deeper with more relevance adding further value.

Finally, your commitment will show, and while it may intangible (at first, anyway), that too has value.

[pzk1]

Appreciate this deeply. You have made me think about doing something unique and valuable which they are currently struggling with.

[endswapper]

Glad to hear it. This is the beauty of Hacker News. I, and others I am sure, would like to hear how things proceed. If you can update us at some point I'd appreciate it. I think it would help those in a similar position, and perhaps managers as well.

[pzk1]

Well, it turns out my idea was too farfetched, and someone already did the groundwork. But I do have an action plan now, just stick to the basics which I did not do previously, for a number of reasons, namely: 1) being too overwhelmed and forgetting to merge, 2) forgetting to fix the PR which has been reviewed, 3) taking tasks which are way above my head and not designing things beforehand which makes the code subpar and introducing regressions, 4) not attacking problems as hard as I can which makes tasks longer, 5) not asking questions a lot sooner

I guess it all boils down to completing the tasks I was assigned, improving the quality of the code and then finishing on time.

[endswapper]

Thanks for the follow-up. I applaud the self-reflection.

It sounds like your manager knows a thing or two in that you may just need a little more time to settle in and perhaps the word "probationary" lit the appropriate fire under you. I recommend continuing what you have been doing - listen, reflect, reach-out, repeat.