How to talk the talk

[Pyception]

Hi Everyone,

I have approximately 7-8 years of experience in Python, SQL, ETL, and data services. Recently, I obtained a cloud/devops certification and transitioned to the Data & AI division. However, I'm finding it challenging to keep up with the rest of the team.

Our colleagues from the UK tend to discuss topics at a high level and delve deeply into technical details. Since I wasn't involved from the beginning, some of the discussions go over my head. Although I often know the answers to their queries, I struggle to explain them in the detailed and structured manner they expect. Their "expectation" involves describing minute details, explaining the impact on decisions, and addressing the why and how aspects.

The second issue pertains to the local team, which is more engaged in office politics and working in silos. Most of the team focuses on resolving JIRA tickets with minimal involvement in sprint-related activities.

Perhaps I'm just feeling overwhelmed by all these changes. Any workaround or how to improve my situation.

 

[pa1]

Disclaimer: Not an expert in talking the talk, not even close.

Is this your first time having this challenge or has it always been this way over your career? Depending on the answer, you know what needs to improve.

If it's only this team & particularly the UK team, it could be due to you unknowingly feeling pressure to have a good impression on them as you have transitioned from different team. Relax, you are on the same team and you'll get plenty of chances to prove yourselves.

If there is already someone in India that you think is doing a good job answering their queries, observe and follow their lead. If you have that responsibility and are feeling overwhelmed, let them lead the meeting but make sure it's a conversation that you actively participate in and not a one sided talk. Do this enough times, you'll get a feel of what they are looking for before they ask and you'll be able to drive the conversation and answer confidently.

 

[Pyception]

Is this your first time having this challenge or has it always been this way over your career?

Nope, I'm having this realization now. In my previous role I was more towards building and shipping stuff. Now more towards project and design/optimization.

If there is already someone in India that you think is doing a good job answering their queries, observe and follow their lead.

I'm already doing this. Plus my roles involves active participation. I'm also thinking to improve my knowledge about infrastructure/code base related with technology. These onsite team is questioning like lawyers (asking the same quesion from different POV) and I think my first impression didn't go well. thanks

 

[pa1]

These onsite team is questioning like lawyers (asking the same quesion from different POV)

Makes sense. You are actually going through the "design interview" phase on the job! It's a good learning experience and if the org is willing to put you through that at 7-8 YoE, it's a good place to be in even if it's difficult.So, make sure you utilize the opportunity, it can take you places.

As a developer, its easy to get hung up on minute implementation details but miss the big picture. you should be able to guess how the high level blocks fit into the design even if you don't know the internal implementation. If you have access to your or any product design and architecture docs, review them in your free time and try to do a mental excercise on what you would do differently and evaluate the pro's and con's of each decision. If you have a colleague you can brainstorm it with, that's even better.

Last but not least, maintain some public or private design notes and document why you have taken a specific path. It will help in explaining to the other team during meetings and also notedown the feedback.

Best of luck.

 

[Pyception]

As a developer, its easy to get hung up on minute implementation details but miss the big picture. you should be able to guess how the high level blocks fit into the design even if you don't know the internal implementation.

Ditto, happend with me more than my finger count.