Are you a Senior Developer & struggling to switch your job?

Here's a thread on how you should prepare before sending out job applications:

🧵👇🏻

First of all know that there's a lot of demand for good software developers.

It's hard for companies to hire good mid level developers. Some of the interviewers I've talked to recently have mentioned this!

So, if you're good, you can always get into a high paying job.
I have 6.5 years of experience mainly as a Backend Developer. Although I do work a bit of front-end tasks as well as part of my current job.

In this thread I'm going to talk about how I would prepare if I was going to apply for a job interview.
As a mid level developer having 4 - 8 years of experience, you will be expected to have certain skills to be hired by companies. Skills like:

- Problem Solving
- HLD
- LLD
- Mentoring / Code reviews
- Taking responsibility
- Leading end-end development & release of projects etc
Problem Solving:

Even though we mostly never write a lot of game changing Algorithms and use data structures, you're still expected to know the most common ones and how to use them to solve problems:

- Tree
- Linked List
- Heap
- Hash Map
- Array etc
You should practice solving Algo & DS questions which are typically covered in the first round of your interviews.

Leetcode is a good choice and covers most of the common questions and the concepts one needs to know.
Practice for about 2 months to solve around 100 questions in Medium and Hard categories.

You can start with Easy questions. But that's just to get into the zone since you might not have solved these questions in years.

But focus on Medium and Hard questions on Leetcode.
A very important point to note is that don't try to remember solutions to questions. It's never gonna help you. If you're doing that, you're just wasting your time.

Instead focus on learning the most common techniques used to solve Algo & DS questions.

https://t.co/IfUEwcDuCN
When preparing for this round, practice writing code for each of the solution in any languages of your choice.

Just knowing how to solve a problem is not enough, you should be able to write bug free code in the given time.

This round gives a good idea about your coding skills.
System Design:

System Designing is another important skill you will be evaluated on. This includes both LLD and HLD.

LLD -> Low Level Design
HLD -> High Level Design
Low Level Design:

Typically LLD rounds focus on low level components of a system which covers below skills:

- class design
- design patterns
- OOP principles
- SOLID principles etc

Here's a reference:
https://t.co/lg4z7gPCy0
Here's a great course to prepare for LLD round "Grokking the Object Oriented Design Interview":

https://t.co/COPTtHXPCQ
High Level Design:

In a HLD round, you'll be given a problem statement and you're expected to design the high level components involved in the system. You need to take care of different use cases which cover

- fault tolerance
- high availability
- data flow
- downtime etc
Here's pretty famous course to prepare for HLD round: "Grokking the System Design Interview"

https://t.co/Su63FPMFxH
Managerial / Culture Fit:

Another important round is either a Managerial / Culture fit round. Which typically involves discussions around your previous projects, challenges you faced and other standard questions like:

- Most challenging problem
- Strengths / Weaknesses etc
To prepare for this round you should know your current project in and out.

You should know about all the different corner cases handled in important features, the design decisions taken, the services chosen etc.
For Example you should know:

- why a SQL database is used in your service?
- why a redis cache is used?
- why a SQS queue is used?
- how a particular error case is handled ?
- when an internal goes down how is scenario X handled?
I cannot emphasise enough on knowing your current project thoroughly.

If you're able to justify all the questions asked on your current project, the interviewer will be impressed & will know that you're actively contributing in the project.
Last but not the least, be prepared to ask right questions at the end of every interview. Asking right questions shows that:

- you're genuinely interested in the company
- gives a good understanding of their tech stack, work, work culture, policies etc
- helps to make a decision
Here's a complete guide (by @RandallKanna) for developers on Job Hunting, Acing the Interviews & Landing the job:

https://t.co/JmG4SKCYYQ
If you like this thread please retweet the first tweet to help me reach more people.

Download my free e-book which contains all of my viral content from the past 8 months here: https://t.co/xCLUcGqZMF

More from Sunil Kumar

10 best free resources to learn Python (2022):



1. Introduction to Python Programming on Udemy
https://t.co/NyCm4YoLMI

2. Learn Python - Full Course for Beginners by freeCodeCamp
https://t.co/xqYNc4zJHh

3. Full Stack Python - Matt

4. Learn Python 3 From Scratch by Educative
https://t.co/ftM9moLZIC

5. Python for Everybody on Coursera
https://t.co/HH2f2Y61NY

6. Learn Python 3.6 for Total Beginners on

7. 100 Page Python Intro - Sundeep Agarwal
https://t.co/DYP24QkpW0

8. Google's Python Class
https://t.co/RYOHCg3Sux

9. Microsoft's Introduction to Python Course
https://t.co/7Xu1OdmQ8Y

10. A Byte of Python (HTML, PDF, EPUB,

If you like this thread, follow me (@sunilc_) for more content like this.

It would mean the world to me if you retweet the first tweet to help me reach more people
Are you a web developer?

Here's a list of websites that offer free & beautiful website templates:

🧵👇🏻

1. HTML5UP: Very modern, unique responsive HTML5/CSS3 themes
https://t.co/VmAFs2xEUO

2. Templatemo: Minimal, resume, gallery themes and more
https://t.co/hCVsSqg3dx

3. Templated .co: Tons of minimalistic HTML5/CSS3

4. FreeHTML5: Free & premium HTML5 and Bootstrap themes
https://t.co/HqCj21RVry

5. StyleShout: Brilliantly crafted free website templates
https://t.co/AeNAAvmiYx

6. Start Bootstrap: Bootstrap starter

7. Zerotheme: HTML5, Bootstrap, Prestashop templates
https://t.co/WZtbW1gZzv

8. HTML5xCSS3: Collection of wonderful templates in different categories
https://t.co/g47dzRhSnW

9. Colorlib: Almost any category of theme you can think

10: Free CSS: Huge collection of free templates
https://t.co/JzQgKmBBGJ

11. Hubspot: Templates, infographics, banners and much more
https://t.co/T2jAlXYH8E

12. Mobirise: Great looking HTML5/CSS3

More from Tech

A common misunderstanding about Agile and “Big Design Up Front”:

There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.

You’re allowed to think about a desired outcome from the beginning.

It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.

It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.

It’s not BDUF if you help every team member know what success looks like.

Agile is about reducing risk.

It’s not Agile if you increase risk by starting your sprints with complete ignorance.

It’s not Agile if you don’t research.

Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.

It would be a mistake to assume this research should only be done by designers and researchers.

Product management and developers also need to be out with the team, conducting the research.

Shared Understanding is the key objective


Big Design Up Front is a thing to avoid.

Defining all the functionality before coding is BDUF.

Drawing every screen and every pixel is BDUF.

Promising functionality (or delivery dates) to customers before development starts is BDUF.

These things shouldn’t happen in Agile.
Ok, I’ve told this story a few times, but maybe never here. Here we go. 🧵👇


I was about 6. I was in the car with my mother. We were driving a few hours from home to go to Orlando. My parents were letting me audition for a tv show. It would end up being my first job. I was very excited. But, in the meantime we drove and listened to Rush’s show.

There was some sort of trivia question they posed to the audience. I don’t remember what the riddle was, but I remember I knew the answer right away. It was phrased in this way that was somehow just simpler to see from a kid’s perspective. The answer was CAROUSEL. I was elated.

My mother was THRILLED. She insisted that we call Into the show using her “for emergencies only” giant cell phone. It was this phone:


I called in. The phone rang for a while, but someone answered. It was an impatient-sounding dude. The screener. I said I had the trivia answer. He wasn’t charmed, I could hear him rolling his eyes. He asked me what it was. I told him. “Please hold.”

You May Also Like