How to Determine If You Are Junior / Mid / Senior Level Engineer

Podcasts Course

Intermediate Training Core Data

Instagram Firebase Course

Facebook Group

Completed Source Code

[ShenderRamos]

Hey Brian you should make a tutorial using each of those skills for junior developers... giving real world examples like you always do... also help building a resume for a junior developer... your tutorials are awesome 👏.. thank you

[nordicvolkan]

I found Jr developers often don't ask questions in fear being perceived unfit or incompetent for the role. Also Imposter Syndrome tends to paralyze Jr developers as well . So if there are Jr developers in your team you should always make it clear to them that it's OK if they don't know or understand something .

[ImeXoplay]

I'm totally a Junior dev... I'm so going to apply for a job as a Junior iOS dev...

[tobiomotayo]

I'm glad you finally made a video about this. Thanks Brian

[ryankanno]

I remember watching this video last year and feeling overwhelmed at the junior dev requirements. Now a year later I actually know almost al of it. Finally applying for my first dev job atm. Thank you for all the help!

[kelvinfok]

Hi Brian, sleek hair! 👍🏻 This video has been really helpful to give especially Junior Devs a general direction to pursue to the next tier. Appreciate your very consistently videos release. Wish you well mate!

[ivelinful]

Thanks for the nice video Brian! I have learnt many things from your channel and I have been working for 4 months as an iOS developer. My level covers every point of your description for a junior developer. This video helped me set new goals for development! Thanks a lot for the good work!!

[JoeWong]

Great vid Brian, looking forward to your analysis of the other two tiers.

[dongshuowu]

Nice to see you again Brian. As always a thumb up.

[samircarvalho]

Great Video! I will use as a roadmap to increase my knowledge! Tks!

[laiqueahmed]

Junior now but slowing developing my skills to become mid level . Thanks Brian !!!

[LucasLima-yumb]

Hello Brian, nice video as always. I guess I'm at the junior level.
Btw, thanks for the kotlin youtube series, youve worked there with picasso and also recycleview. Those topics and how you worked with them, explaning everything really well and clean helped me a lot getting a job as an Android Developer. I got the job this week and im starting next monday. Ive been into java for mobile for over 6 months. I hope you continue with Android (Also mobile in general) showing us all new trends that are coming.
You may not have an idea of this but your videos/work are helping people from all over the world like it helped me a lot. Thanks for sharing your knowledge with us and making such nice videos, caring about the quality not only of the information youre trying to pass to us but also with the editing (audio, video) quality.
You rock bro! You have a long road to go on yet!
Hugs from brazil man!

[MrFarmerarmer]

Hi Brian! Another great video which has been incredibly helpful! Please do a follow up video talking about middle & senior iOS Development. The breakdown you did in this video has clarified some of the points on the table for me, and I would love to get the same sort of breakdown for middle and senior roles.

[RnRoadkills]

In my 25+ years as professional developer a “skill matrix” is of the target and kind of irellevant. My own 2 importent rules (or what I think makes me a senior):

1) Think ahead. - If you suspect some function/option/extra will come later on, prepare for it. Example, if you are making a messagesystem and you guess there will come a “blocking” stuff in the future, then prepare for it. Even if it is “empty” methods/store procedure/other. Make it easy to add later on or make the software easy to add/edit/change the source in the future.

2) Add comments to your code. Write comment on the logic (not what your code does, but the logic and why). Lets say you have a codeline “if (error == 7)” then comment what error 7 is and why. Even if it is pure logic for you when you write the code. You will be happy when you have to edit/change/bugfix the code later on. When you fix a bug, then comment on your fix in the code. What the error was, why and how you fixed it. Because when you see that same code later on, you might have forgotten why it is how it is. The risk is you could change it back to a bug again, because it looks odd. If you have “if” statements for data, then comment on what the data you are “if’ing” are and why. If you are settings values (type = 34) then comment what and why (specially if it is database field values).
When you are coding and in the process are finding out that the way you are doing it is not the best way, then write it as a comment by the code. Because when you later on goes back to that code, your mind will return to the original (not best solution) again. The comment will bring you forward and prevent you from making the same mistake again at that spot.
My commenting on my code has been the best thing I have done the last 2 decades.

Most critical errors are messed up data in the database, because the logic somewhere was bad and not discovered in time.

[luismiguelss]

What a rush with so many videos!! Actually this was really hepful for me to determine my level. Keep up the good work!

[mubin]

Thank you Brain! Your videos are really so cool.

[tomrogers]

Another great video. I'm probably one of the least experienced iOS developers here; I've been doing it for about a year in terms of building my own apps (looking to change that soon). I think this is an interesting perspective but, like anything in life, has dangers if it is applied too rigidly (it could be quite intimidating to those who are just starting out). One thing that I take some issue with is the idea that Junior developers can just rely en stack overflow. I actually think it's the other way around; when your beginning, you need tutorials to give you Direction instead of just copying code. However, once you get more advanced, you hopefully have the decision-making abilities to intelligently adapt the solution to work to your specific problem.

Definitely an interesting video though.

By the way, target-action is exactly what you assumed it was. It's the event handling system from the days of Objective-C that allows us to have a target on an object to say that it responds to certain action messages (methods).

[quotipi]

Thank you so much for this. Super inspiring. I'm going to brush up, get to work and start applying for a real job soon

[soundfonts]

Very informative, thank you for sharing!

[-nz]

Thanks Brian, your video is very helpful!