This question usually comes to me at different cycles. The experiences we gather from different roles and domains get accumulated and gives us perspectives unique to the domain.
After a decade I had options to choose
- Go forward in same Database space
- Setting up teams from scratch
- Domain-based focus and build expertise
- Professional services, Automation, QA
- Learn something new
Every challenge once you solve becomes boring. Everything is difficult until you find a way to do it. Passion without skills won't get you where you want to go.
Five years back I decided to reboot myself in Data science space. Every other previous experience gave new perspectives to explore. Building expertise in one area, solving problems in a domain perspective, Working on creating unique IP, Learning other related tasks to delivery.
Many times in career I always get discussions and proposals to go back to previous roles. From data science now I get to hear Big Data + Data science skills. Even within data science to build expertise in video, numbers, text aspects, it needs deep dive and consistent focus for a certain period.
Close to two decades in a few years now question remains how long to remain as Individual contributor, Finding a role that uses all the previous experience, keeping up with titles?
The primary aspect of my satisfaction is learning. After a few years, there could be something that would replace today's data science.
As I grow older, I have to pick and choose my areas of interest, areas to focus on. I never met happiness focusing alone on titles or compensation. They also have a priority after satisfaction though. A job that gives you learning, exciting but not overwhelming challenges, manageable work-life, and compensation would be the best thing to look for and have satisfaction till the day of death. Sometimes you need titles to execute your strategy.
Compensation helps you meet your financial goals. The search is to find a role that gives you opportunities that meets your priorities and leverages your strengths. Career is a long term thing
. Keep learning until you find your dream role. Be prepared for the role. Don't wait for titles to learn the role.
How to write a design doc, take feedback, and drive it to resolution, in a reasonable period of time
- Competitive product
- Papers Referenced
- Potential Architecture
- Prototype
- Demo
- Next Steps
How to mentor an early-career teammate, a mid-career engineer, a new manager who needs technical advice
- What would I do if I am in your situation? This is how I look up and advise. We cannot learn everything. We have to pick and focus on few things which are important for us.
How to influence another team to use your solution instead of writing their own
- View it as a joint success. Sometimes you have to give credit to make things work.
How to get other engineers to listen to your ideas without making them feel threatened
- You are not selling your idea, You are conveying how it is done across other industries/companies. You need to have a working demo, deep dive on the benefits of it. It may not work in the first go but over a period of time trust will develop
How to craft a project proposal, socialize it, and get buy-in to execute it
- Everything we pick someone who has already experimented / could be something ongoing. Give the context, potential value and take it to next level.
Keep going!!!
