Interviews are hard, and sometimes they are nothing like the actual job, which sucks.
Nevertheless, it has caught my attention that A LOT of people ignore things that factor in hugely in an interview and are usually what determines if you get an offer or not.
1_ BE CONFIDENT! But don´t lie.
When you know the question asked answer with confidence, demonstrate your knowledge.
When you don´t know the question give a limited answer and say something like I would like to get more experience with it.
2_ Demonstrate interest in the company.
Even before that, be interested in the company.
If you aren´t, you should probably not even apply there.
It can be their stack, their mission, their culture, something that really clicks with you. Let them know you identify with that.
3_ Guide the interview whenever you are given the chance.
Talk about your projects, tell them about something you accomplished, and are proud of. Let them know about the challenges you had and how you overcame them. Make sure they see the value you bring and how good you are 💎!
4_ Positive attitude and spark
This can go a long way. Sometimes a team already has all the dev rockstars they need but could really use someone who is positive and full of energy to tackle tasks and learn new things. Most dev hiring people like to see that on candidates.
5_ Tech hobbies/ extra courses
If you do like to code outside of work hours let them know. It demonstrates that you really love your field and you are hungry to learn more.
If someone tells me they love to learn but have never taken a course or done a side project I doubt it.
6_ If you had a job before PLEASE be sure to know how to explain the architecture and a full cycle of request-response in your previous project!
If you didn´t have a job before, this applies to the best project in your portfolio.
They will ask you this to test your knowledge.
Those are all for now. Keep in mind these are tips to stand out and caught their attention provided that meet the minimum technical level they are looking for.
You still need to work on your fundamentals and algorithms and such. But if you add this you are miles ahead of others.
And lastly, this is all based on my own experience from both sides, what had worked wonders when I apply and what hasn´t. And also what we look in candidates when doing technical interviews and what our leaders love to see in new members of the team!
Hope it helps you 🚀
• • •
Missing some Tweet in this thread? You can try to
force a refresh
If you are tired of breaking environments or you keep hearing about DevOps but have no idea what that is...
Then this thread is for you!
Let's talk about CI/CD!
This is the ninth thread of the series: Interview Preparation!
🧵THREAD🧵
First, let's get some definitions down.
CI = Continuous Integration
CD = Continuous Delivery / Continuos Deployment
DevOps = Combination of practices of Software Development (Dev) and IT Operations (Ops)
Let's tackle these concepts and it¿s tools and practices
⬇️
CI/CD is a set of principles and practices to deliver code changes more frequently and reliably
It is one of the best practices for both DevOps teams and agile methodologies, as it goes hand in hand with their objectives:
- Focus on business value
- Code quality
- Automation
Most of the systems you will build in your life will need some form of persistence.
That is why when preparing for an interview you should be ready to talk about Databases
This is the eighth thread of the series: Interview Preparation!
🧵THREAD🧵
First, let's get some definitions down.
A Database is an organized collection of data.
A Database Management System (DBMS) is a software for users to define, create, maintain & control access to the DB.
You will also need a language to program and design your DB objects.
⬇️
There are very different types of Databases & also a lot of possible classifications.
I would say the most useful one is:
- SQL
- NoSQL
We are going to focus only on SQL Databases in this thread.
If you are thinking about FAANG companies or similar this is probably the most important topic. Otherwise, this is still a big topic to cover but don't neglect the others
We will cover a roadmap for Algorithms & Data Structures
⬇️
First let's talk about some easy problems that are widely used in interviews, make sure to be able to solve them.
Read each of them and think of the solution now...
If you can't figure them, search on youtube, there are plenty of videos explaining and solving them.
Javascript is a programming language, the one native for web browsers, and one of the most used in the world.
It allows you to create a front end, back end (node), and even mobile with some magic in the middle. Let's go through the fundamentals that you should learn.
Now it's time to get into the specifics. Do you know how to build Front ends?
This is the 3rd Thread on the series of Interview Preparation
Let's get started!
🧵Thread 🧵
A quick note here: This will focus on web devfront end (some things apply to mobile too), but keep in mind if the position is backend developer, desktop developer, or other fields some things might not apply.
This would be the standard front end check for FullStack Web devs.
👇
First of all, you have to understand:
* What is the Web
* Server-client relationship
* How in the end our web browsers can only process HTML, CSS, and Javascript.