5 Things to do When Joining a New Company (as a Software Engineer)

preview_player
Показать описание
My personal tips on things to do when joining a new company or team as a Software Engineer.

In this video I'll give you 5 tips to help you join any team in the same company or in a different one and be successful when getting that new position. It can be daunting to know what things to do when joining a new company or team, and many videos focus on generic tips instead of focusing of software developers/engineers.

This video is intended for all levels from junior to principal engineers.

#softwareengineer #newjob

-----------------------
Resources:

🔖 FREE:

📚 Paid (personal recommendations - not sponsored, but I can get some commission if you buy them through the links below, at no additional cost to you):

-----------------------

-----------------------
Remember you can reach me here:

-----------------------
In A Dev' Story I explain Software Development related topics from my point of view. I'll be explaining different topics in "Chapters" according to the stage of the story I think they belong. Hope is as entertaining for you as it's fun for me to create these videos

Thanks again for watching! Feel free to like, comment, share and subscribe, it means a lot to me and helps the channel grow.
Рекомендации по теме
Комментарии
Автор

Totally agree with you!!

Also, going a bit more into the technical side, I found really helpful to follow this learning path:

1) Learn about the products your team provides, how they provide value to the business, and which are the main features
2) Understand the key metrics
3) Learn about the services architecture, how the features fit into it, and why it was built that way
4) Deep dive into the code and learn how are the most critical features architected.

jorge-cmiw
Автор

Great tips. One more thing is to document what you have learnt.

debakarr
Автор

I usually build a dictionary of Words I don't understand that people are using.
I usually tell people I am gonna ask dumb questions and let anyone ask me dumb questions so I become the guy they can ask when they are embarrassed, if i cant explain something it also shows me I dont understand something enough.

Technical things to understand
From a QA side i usually understand the git strategy/environment structure/Pull request process/Ticket management in the SDLC

jacktilley
Автор

I am moving on from my current job and your videos are really helping understand the things that i didnt know before i start looking.
I saw a job description the other day constantly talking about SOLID principles and immediately wondered wtf is that.

jacktilley
Автор

Great tips, I add the task that involve the informal ways to know the key persons in differents support areas, in order to improve you joining the software developer process.

sgssergio
Автор

Hey Cristian, very good advices, I agreed to everything - Saludos amigo!

fugarte
Автор

very helpful advice for someone who just joined moved outside my home country and joined a new company. effectively, the way to cooperate is pretty different compared to my previous companies, and tech stacks & tools are more or less different, first months are good transitional periods for self-training not only technically, and functionally, but also culturally. BTW, for anyone, who wants to move to hong kong and work as a software engineer in a leading investment bank, please reply to me.

jacques
Автор

This got me interested in joining a new team 😆😁

MrNsaysHi