Programmers, if your resume isn't getting you job interviews, here's what you're doing wrong:

1. Limiting your scope

Don’t say “React Developer” ❌
Say “Frontend Developer” ✅

Your projects in React will prove understand frontend well and are capable of learning more frameworks.
2. Being very general in your experience/internships section.

Don’t say “Created apis for frontend” ❌

Say “Created express nodejs apis to fetch user data from Cosmos DB” ✅

It helps with keyword matching & also improves credibility of your statement
3. Focusing on certifications instead of projects

“Completed ‘Introduction to JAVA’ course on Udemy” has low/no value. ❌

“Built a JAVA springboot application…” has high value ✅
4. Not being relavent enough

Mentioning your Machine Learning projects for a frontend engineer position isn’t relavent.

Similarly expanding your “Digital Marketer” experience into 6 big points isn’t gonna help for a Software Engineer position.

Keep irrelevant experiences short
5. Telling long stories

Don’t write paragraphs explaining your position, projects or current situation. ❌

Your resume should contain facts and concise single sentence points explaining technical details of your projects and experience ✅

Save your stories for the interview
That's all for this thread. If you find this useful:

1. Retweet and leave a like on the first tweet - it encourages me to write more of similar content.

2. Follow me @ujjwalscript for more useful tips and threads 🙂

More from All

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.