Interviews aren't only about technical skills.

Here are some questions to help you prepare.

🧵👇

Explain what you have been working on for the past few weeks.

What are the most exciting parts about that work?

What portion of it do you consider boring and why?

[2 / 10]
What specific libraries and frameworks are you familiar with?

What's the minimum set of libraries and frameworks that you'd recommend to any practitioner?

[3 / 10]
What kind of problems have you worked on in the past?

Can you list the specific use cases related to each one of these?

[4 / 10]
What is the most exciting project you have ever worked on?

What was your role and responsibilities on that project?

Why do you think your work on that project was important?

[5 / 10]
What are some of the common issues that you have faced before while working on a project?

How have you approached these problems?

[6 / 10]
How would you organize a team to create and deliver end-to-end applications?

What specific roles would you include in that team?

How would be the interaction among team members?

[7 / 10]
What are some of the specific areas where you'd like to do more research to improve your knowledge and skills?

How do you keep your skills fresh nowadays?

[8 / 10]
When dealing with non-technical stakeholders, what tries your patience?

How do you deal with these situations?

[9 / 10]
If we imagine one year in the future, and we are high-fiving because you succeeded in this position, can you list what went well?

How about if you failed? What went wrong?

[10 / 10]
Hope this helps.

If you want more content on software engineering, machine learning, and adjacent topics, give me a follow. I post threads like this every week.

You can enjoy more of this content here: @svpino.

More from Santiago

You gotta think about this one carefully!

Imagine you go to the doctor and get tested for a rare disease (only 1 in 10,000 people get it.)

The test is 99% effective in detecting both sick and healthy people.

Your test comes back positive.

Are you really sick? Explain below 👇

The most complete answer from every reply so far is from Dr. Lena. Thanks for taking the time and going through


You can get the answer using Bayes' theorem, but let's try to come up with it in a different —maybe more intuitive— way.

👇


Here is what we know:

- Out of 10,000 people, 1 is sick
- Out of 100 sick people, 99 test positive
- Out of 100 healthy people, 99 test negative

Assuming 1 million people take the test (including you):

- 100 of them are sick
- 999,900 of them are healthy

👇

Let's now test both groups, starting with the 100 people sick:

▫️ 99 of them will be diagnosed (correctly) as sick (99%)

▫️ 1 of them is going to be diagnosed (incorrectly) as healthy (1%)

👇

More from Life

“We don’t negotiate salaries” is a negotiation tactic.

Always. No, your company is not an exception.

A tactic I don’t appreciate at all because of how unfairly it penalizes low-leverage, junior employees, and those loyal enough not to question it, but that’s negotiation for you after all. Weaponized information asymmetry.

Listen to Aditya


And by the way, you should never be worried that an offer would be withdrawn if you politely negotiate.

I have seen this happen *extremely* rarely, mostly to women, and anyway is a giant red flag. It suggests you probably didn’t want to work there.

You wish there was no negotiating so it would all be more fair? I feel you, but it’s not happening.

Instead, negotiate hard, use your privilege, and then go and share numbers with your underrepresented and underpaid colleagues. […]

You May Also Like