Now that you have been preparing for almost six months and adding more value to your daily engineering 1
tasks, it is a good time to update your resume. 2
So here are certain tips that will help you in creating a good resume. 3
First make it at most two pages long. 4
If you have 5 years or lesser experience, then one page is sufficient, as well. 5
Align it with your LinkedIn profile. Linked profile is just point us to what you have been doing. 6
So don't elaborate everything, just mention the frameworks and a brief description. 7
Be sure to mention 8
exact durations of your assignments accurately. 9
This helps the interviewer in tracing if at all. 10
there are any gaps in your career and they can ask you a specific question around that. 11
So you are well prepared for that situation. 12
Mention only currently valid certifications, if any. 13
Here is something that happens quite often, that people have certifications from the past which have 14
already expired and that can lead to a confusion because certifications are bound to certain APIs and 15
behaviors of particular platforms which have changed and the existing organization might not be looking 16
for something or outdated. To avoid that kind of a situation 17
just be specific. 18
Keep education details limited to name of the institution year of graduation and major area of study, 19
computer science, electrical, mechanical, etc.. 20
When describing your particular work assignments, be specific and show numbers to support your claims. 21
Example Improved the performance of multimedia planning by 25%. 22
Be sure that these numbers are real and accurate. 23
This can get you the attention you need, but be sure not to lose it with vague answers because they were cooked 24
up numbers. 25
So be prepared for the follow up questions like what were the tools that you used to get it done? 26
Or if something about scale comes up? 27
At what scale did you achieve this efficiency? 28
So this is you taking control of the conversation. So be specific and give the interviewer some very 29
statistical evidence of what you have been doing. 30
Only mention the frameworks that you have interacted with. Don't try to map framework names based on 31
the job descriptions. 32
Even if you get a job by answering simple questions around it because you have been thinking or trying 33
to find out answers around that framework for a few weeks, you might soon find yourself firefighting in production 34
with the same framework. 35
So might all this a learning curve in general, but it only results in burnout and partial knowledge. 36
The reselling of such partial knowledge is very short lived, so decide accordingly. 37
And finally, choose a simple format like Google Docs. Always share 38
a PDF with recruiters. Have the last updated date at the bottom for your own reference. 39
Because if somebody has your old resume and they reach out to you, there might be a confusion. 40
if you have upskilled yourself and you are better positioned to look at a higher designation. So just 41
to eliminate that kind of confusion, 42
have always a date at the bottom. Have a simple notepad version of your resume ready as well. 43
Sometimes it is easier to post the text version into the servers because initial screening will be done 44
by machines and you don't want the fancy infographics to interfere with that. 45
So PDFs personally I have seen PDFs not getting parsed correctly to autofill forms and it takes a while 46
to correct that thing. 47
So having a simple notepad text of your resume will always be helpful. 48
But remember, this is the first parse of your resume. 49
We will come to the detailed check points in the later section. 50
See you in the next segment.