Study Plan to crack Product Companies in 6 Months
All of my articles are free to read. If you don’t have a Medium subscription, you can still read by clicking this link.
I wrote this article based on my personal experience serving multiple product companies in the past and listening to thousands of our learners’ success and failure stories with product organization every week.
Many QA engineers are passionate about their career dream of working for a product company one day — you should know that you do need to pull your socks up and spend the next few moments running down this entire story and then next 6 months.
One way to achieve your dream is by learning from failed interviews and the other way is to design and execute a smart study plan.
With reference to the vast content to cover for preparation, working hard is not the best solution; you need to be smart enough to design the best preparation strategy. Which one do you prefer?
You’ve got to be smart so that is what will set you apart from the hundreds of competitors appearing for the same position along with you.
Why Product Company?
Most of the product company hires smart, creative people, and treats them well. Also, they reward right, encourage new ideas, and give employees the freedom to work.
The 1–2–3–4–5–6 Month Study Plan
Disclaimer: This study plan is designed for the average skilled resource and who has about 60–80 hours a month for preparation.
Tip 1: Create your own GitHub public repository and keep pushing your daily learnings with a proper readme document and this repository can be referred to in your resume.
Tip 2: Practice your coding in online platforms like HackerRank, LeetCode
Tip 3: When you learn a concept, practice with different possible problems in that concept. Most of them solve from GeeksForGeeks based on company-wise questions.
Month 1: Focus on any one programming Language
What programming language is best for the SDET role? There is no hard and fast answer for this as it is different for every person according to several personal factors —but look at the recent Job description of your preferred organization and make a choice for yourself.
If being one of you at this moment — I would choose between Python, Java, and JavaScript. Personally, if you are good at one then you can learn others in a short span. Learn deeper and not broader.
There are many free courses in Udemy, Coursera, Pluralsight, and Codecademy are the best resources for learning your new language. You can reach to TestLeaf if you need additional support in learning.
Month 2: Focus on data structures and algorithms
Month 3: Focus on Problem Solving & Testcase Enumeration
Month 4: Focus on any one UI automation tool
Month 5: Focus on any one Services automation tool
Month 6: Practice, Practice, and Practice.
Finally, If you don’t get your job in your desired Product Company after six months?
Certainly, it won’t be the end of the world. Your learning can still be armed with the skills and knowledge required to work as a software automation engineer at any company. Good Luck!
