"Do you have any (further) questions?" sounds common to you?
It's one of those questions that is often asked at the end of an interview (stage), and it's one question that you shouldn't answer with "No, not at the moment".
Here is why.
🧵⬇️
1️⃣ Why Is This Question Important At All?
This question gives you a chance and not a small one. You can use this question to show that you actually paid attention to the interview and to clear things up for yourself.
Simply stated:
Before you leave the room (be it virtual or physical), you can give your interviewers a very positive impression. And they will leave the room with exactly this positive impression, going into further internal discussions.
Often, your interviewers use exactly this question to test how prepared you really were. Yes, they have tested you for your skills and your personal fit already, but how invested in getting this job at this specific company are you really? How much research have you done?
2️⃣ Important Rules
1. Don't use this question to ask about salary 2. Make the questions meaningful 3. Show that you paid attention to everything they said 4. Show that you did your research before you applied
Salary Questions:
If you only ask about salary, you'll only show that you're interested in your own benefits, and although that's perfectly valid on a personal level, the company should hire you because you do something for them.
Meaningful questions:
Don't make it seem as if you prepared some random questions only to have something to ask. Most interviewers will smell your cheating and you won't be able to make a positive impact.
Show you paid attention:
If you really paid attention, you can easily come up with some questions that give you more insights into certain details you've already talked about. You just need to get one level deeper.
Show that you did your research:
Companies usually offer a lot of information. Through their website, their blog, and their social media presence.
Use this to your advantage. You can use nearly everything they put out on the internet to ask questions about.
3️⃣ Some Examples
"Yes, I have. We talked a bit about your current plan to invest heavily into training your technical staff in soft skills. Could you tell me more about whether you consider your employees participating in creating a curriculum? I'd love to help with this!"
This one shows that you paid attention to the overall interview. You specifically recall one topic the interviewers talked about. And next to that, you also show that you are willing to jump into something that seems important to you.
"What would you say is the best way for me to prepare for my first two months at your company? How can I ensure that I have the best preparation so that the onboarding phase can reach its full potential?"
This one shows that you are really interested in making your arrival at that company a full success with a large impact. You are willing to go the extra mile to ensure that you are ready to crush it, as soon as you land.
But it also gives you some information about their expectations. Will they give you a huge list, or will they ensure you that there is no preparation necessary because they do their very best to manage all that through their onboarding?
"We talked about your next innovative product launch. Can you explain how large you think the impact will be on your company's growth in the next five years? What are some risks you see and what are potential consequences?"
The company you are applying to is not the only one that has something to offer. You offer your skills, your time, all your expertise. And you want it to last a bit longer than only a few months or two years. Are they on the right course? Do they believe in what they do?
Can they ensure that you'll have a good job in two years from now? It is your good right to also take care of your personal interests.
You are still at risk of them not replying openly because you aren't an employee, yet. But you can evaluate them based on their answer.
4️⃣ Conclusion
The little things can usually make a difference. Such as using a very simple question to make your interviewer's impression of you even better than it already was.
You don't need much more than some preparation beforehand, and the willingness to jump ...
... right in and take your chance. That's not a huge investment.
The ROI of this investment, however, can be a new job, and this alone should be well worth it!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Here are some resources that help you getting started.
🧵⬇️
1️⃣ "The Book"
This is the official Rust book. It covers everything the language has to offer and introduces feature after feature while enabling especially newbies to follow along from the simpler to the more difficult topics.
This project gives you small exercises that aim at getting you comfortable writing Rust code. Especially if you don't feel creative enough to think of a new project, this is a great way of still writing code.
The most-loved language, according to StackOverflow's yearly developer survey that not enough people seem to use professionally.
🧵⏬
1️⃣ What Is Rust?
Rust is a systems programming language that is compiled to binary. It has no runtime and instead uses a concept called "borrow checking". Developers don't need to explicitly free memory, the compiler does it for them.
The language itself is multi-paradigm, offering functional, generic, imperative, structured, and concurrent programming with a huge emphasis on performance, memory safety, and developer productivity.
You hear some people talking about it, you might have a basic idea, but let's take a closer look because, in the end, it's not as difficult as it might seem from the outside!
🧵⏬
1️⃣ What Is It?
Test-driven development (short: TDD) is a software development technique.
Instead of writing all your code first and only then writing your tests, you start with tests, then code a little, then test again, and so on.
It is one specific form of the test-first approach and aims at making software development faster, more reliable, and safer to do. And it especially forces developers into a user role.
By writing tests first, you become a user. You are the first one to ...
"What is your current salary" is one of the most common questions you'll be asked in an interview.
But you should never answer this question and be ready to accept they might not choose you anymore.
Here is what you can do to deal with this question.
🧵⏬
1️⃣ The Reason This Question Is Asked
The reason for this question is pretty simple. Salaries are one of the hugest cost factors for companies, and minimizing those is one of their main goals.
Why should a company pay you 200k if your previous salary was only 120k?
Well, that's at least their reasoning. Especially when your previous and future tasks are comparable, why should you magically be worth so much more?
Having a number at hand makes it pretty easy for them to negotiate with you. A little more salary is okay but too much? Nah!