Here are my 2¢: Leverage platforms that offer mock technical interviews (e.g., Pramp, Interviewing.io, probably there are others too). This approach lets you simulate the interview experience in a risk-free environment, getting you accustomed to the format and the pressure. It’s crucial to receive feedback, and these platforms pair you with industry professionals who can provide just that. This method is effective because it targets your interview skills directly, allows for rapid iteration based on feedback, and builds your confidence in a more controlled setting than actual interviews.

Aside from just technical skills, these mock interviews can help you articulate your thought process clearly, which is often as important as the solutions themselves in ML roles. Remember, it’s not just about getting the right answer, but also showing how you approach problems.

A side note based on a pattern I've observed so far: candidates who practice like this tend to perform better not just in technical assessments but also in explaining their past projects and teamwork experiences, which are equally critical parts of the interview process.

Hope this helps. Dive in, get that feedback, and refine your approach. Good luck!

Before paying for mock interviews, it might be a good idea to first get practice with something like https://grow.google/certificates/interview-warmup/

There are also plenty of virtual groups around that offers p2p interviews (each side interviews another).

These might be better for initial warmup as the only cost is an extra hour of your time (but it also allows you to experience the interview from the interviewer's perspective).

Isn't the feedback "get better at leetcode" and "talk while you're solving the problem"? These seem to be the universal reasons for rejection.

The key to interviewing well and confidently is to understand that you are not the only one being interviewed. You are interviewing them! And you want to ask probing questions that reveal the employer's mindset and working conditions.

Many employers go into these discussions thinking that they are going to put you under the microscope. But if you direct hard questions in their direction, the power dynamic changes. Suddenly they are trying to convince you that you should work for them.

One of the best questions to ask early in interviews is "Outside of what's in the job description, what are the qualities that you are looking for in the ideal candidate?" Then you can frame your responses in a manner that aligns with their description.

Another great question to ask: "What are the circumstances that led to the availability of this position?" I asked this question recently and the employer revealed that 1) a former employee in that position had left, and (after further probing) 2) this employer tended to hire inexperienced engineers, who frequently left after a couple years to pursue better jobs. Needless to say, that info prompted me to end the conversation.

Remember: It's far better to be rejected by a good employer than it is to end up working for a shitty one because you didn't ask the right questions.

Is your current employer hiring? Are you / can you be involved in that process?

Your employer is only one company, but understanding its side of interviewing can help guide you in how to present yourself as a candidate.

Also, yeah, the best way is practice and self-reflection. And the best way to get practice is to do it, so submit resumes to jobs you aren't sure you really want rather than only your OMG I want this job. This gives you a chance to do some negotiation practice too, and maybe have some offers to play against.

The only way to get better at interviews is to do interviews.

The best advice is to get as much practical, real interview practice at companies that aren't your #1 choice before you go interview for your dream job.

This is the best advice. Interviewing is not like riding a bike. It’s not something you master and then pass all subsequent interviews.

Go and interview. Most importantly, don’t get discouraged by rejection and ghosting.

One thing you can practice is leetcode if you are applying for programmer jobs. This gets a bad rap in some circles but the reality is that coding exercises often are part of the interview process. It’s hard to pass these without practice for many people.

Wow the answers are bad. I can tell you for sure practice does nothing and can actually turn into confidence which can be read as arrogance. Researching the company is also a waste of time, it will maybe give you a 5% boost.

The reality is that people that do the hiring are usually workaholics, so they turned interviews into dating. The only way to get a job is if all the people involved like you outside the job.

So look into networking, nepotism and cronyism.

You're not wrong. You need to be top-top talent to get offers on skill alone (I've seen it with one individual, it's rare).

The real kicker is that "All the people liking you outside the job" is going to be radically different at each place. There is no way to calculate for that.

This is why workplace culture is stupid. We don't need to be a substitution for real friends. Just let us do our jobs. Socializing is a great skill, but it doesn't equate to being able to debug Golang or detect accounting fraud.

Save some blackpill for the rest of us. I've hired people who i don't like personally, but they were a great fit for the role.

>they turned interviews into dating

lmao, it's true. You show up on time, put your best foot forward, talk about your experience, passions, skills, and then they'll consider whether you're tall enough.

Practice can also give you this look up table of canned responses that makes you sound robotic.

People won't like your answer but I pretty much agree.

My career opportunities are what my friends can help me with because I don't have Terence Tao's CV to beat out the highly recommended candidate by the friend of the hiring manager. I think many really underestimate the high probability of being up against the hiring manager's friend of a friend and delusional in their own ability to beat that friend out. If someone is such a standout and genius they really shouldn't be giving advice to the average person anyway in this area.

Interviewing is a skill and via the right practice you can get better at it. I went down that path and got much better at it. Some things to think about:

- you can do practice interviews with peers, some people will be good and some will be bad. Anyway, record them, play them back, take notes on how to get better, and repeat.

- get a list of sample questions, all of them, and figure out through some thought what the best answer to each is, and then drill on that. I used Anki, made hundreds of cards

- learn about MECE and make your answers MECE compatible

YMMV but I was able to really make a leap via some deliberate practice over the course of a couple months.

Practice for 4 weeks, then go interview. It's useful to practice a bit, but it's more important to just go do the interviews soon. Pick whatever practice makes the most sense, but don't worry too much about getting the exactly right practice. Review descriptions of what interviews will be like generally, and try to solve a handful of practice problems.

The best way to learn to interview well is to interview other people. You very quickly see what works and what doesn't. Of course, it's difficult to just make that happen in the short term.

In the end, you should just go interview places. You'll quickly learn whether you're all good (because you get offers), or if there are any problems to address. Only worry about it if there are problems.

Just go for the job you want. Don't burn other companies and waste their time to exercise your experience.

Your limited experience - internship as work history - will already allude to the fact that you don't have interview experience. You can address that up front during the recruiting process.

I couldn't disagree more. If possible, always interview with companies you really want to work at later in the process (its often not possible, but this should be plan A.)

Agree with this.

More practice means better. And the best practice is real interviewing.

Also don't take the first offer given unless its one of your goal companies.

Keep interviewing for a bit more like https://en.wikipedia.org/wiki/Secretary_problem.

Interviewing has a cost to the employer as well. If you are doing it just to practice with zero intention of actually working there, that is dishonest and disingenuous.

I'd argue it's hard to know whether you want to work at a company unless you interview. The cost of interviewing is miniscule compared to the cost of hiring.

I agree, always be courteous and professional, but you have to interview when given the opportunity. The wooing and interview goes both ways.

> Your limited experience - internship as work history - will already allude to the fact that you don't have interview experience.

Sorry if my OP wasn't clear, I'm in a real, permanent job. I meant that I was selected for that through my internship performance, the interview itself was very light. I guess your point still stands though.

> Just go for the job you want. Don't burn other companies and waste their time to exercise your experience.

I'd also like to avoid that. Thanks!

The only way to both get experience and get hired is just to keep trying and just shooting for whatever you'd like to do

After series of failed interviews I got my first job by during interview clicking with my future boss on a personal level and we ended up talking more about Witcher books than job itself lol. Less than a year later I ended up leaving that corpo as despite good performance and good opportunities I was just very wrong cultural fit

So moral of the story is that stuff can be really random and the only way to get it right is to just keep trying

Ask to shadow interviews at your current workplace. You will get a lot of exposure to the process, and will have access to actual feedback about what works and what doesn't (not something a company almost ever provides to an interviewee).

I just find it sad that all the upvoted responses are "practice interviewing", which although is true and good advice, is indicative of a spurious state of affairs, that jobs are acquired not through merit, but by rehearsing an aesthetic ritual unrelated to job's tasks at hand.

https://news.ycombinator.com/item?id=39754083 also puts it well.

I would recommend trying to research what you can about the interview process for specific companies you're interested in. I interview for scientists and engineers for an ML research team but I know that my team (and company's) interviewing process is different to other similar companies. Also, don't neglect software engineering skills in preparation, industry ML is mostly software engineering.

Just do some interviews. Like 10. You'll see what you are good at and what you are not good at. Focus on trying to improve what you are not very good at. You might be okay at interviewing or you might be really bad. You wont know until you do some interview.

You can also do something like interviewing.io or just have a friend interview you to get an idea without actually having to interview with a company.

- I don't know if this will work well to you, but try to find someone in the same field to make some Mockup interview [paid] try more than 1 interview with different people. - Try to know the hiring process of the Corp. Comp. etc. you interested in through asking questions in LinkedIn or even look up through Glassdoor App

If you want to get better at something, do that thing deliberately. So if you want t get better at interviewing, go on interviews. At the very least it will help you get more comfortable doing them, which means you present better.

But don't interview for jobs you don't want or it is a total waste of time for all concerned. It can't be that hard to find jobs you'd like, so interview for those, even if you don't have a hope of getting them.

Start interviewing! Get experience! Don't expect every interview to result in an offer. Take each interview as practice. Honestly, the first 10 companies you interview with, you should fully expect rejection, so don't go after your dream jobs immediately.

Interviewing is a skill just like ML and coding are skills, and you need to practice to do it well. And the best way to practice... is to do it!

And frankly? Everyone should be interviewing on a regular basis, anyway. Always keep an eye on the market and be ready to jump if something better comes along.

Best of luck!

looks at the market for coding skills "hmm... guess I'll interview at McDonald's for practice" ;)

Time to get a real job bro.

I'm European and in a very particular sector, so YMMV, but some thoughts:

I do a bunch of interviews, just finished one about an hour ago actually. If you've gotten as far as an interview, great stuff! Most CVs go right in the bin.

There'll be a few things on your application that caught the recruiters' eye. No-one wants to waste time interviewing people who they don't think can do the job, on paper at least. You're doing well.

When I'm interviewing, I have three broad questions in my head, in pretty much this order of importance.

a) What is this person going to be like to work with?

b) What can they do that we / the other candidates can't?

c) Was this person honest on their CV?

On a) People want to work with nice people. At least one of the interviewers will be spending a lot of time with you. It depends on the role and company, but particularly with less experienced candidates where the need for some learning is a given, I'd much rather have someone nice than a highly-skilled arsehole.

You want to be relaxed and confident. Tough without experience, but don't sweat it, I have a practical suggestion below. Also smile and make some eye contact, and you're allowed to have a light bit of humour about you. You can use that bit before things get rolling properly for a _very_ light bit of banter. Get things off to a good start.

In terms of getting that confidence? Have you got experienced, professional older friends, relatives? In the sector is best, but not essential. You can ask them to help you out with a mock interview. I've done a bunch for friends and family over the years, it seems to help folks get over your exact concern. Bit of roleplay, they'll need to do a bit of research themselves (e.g, on technical questions) so it'll need to be someone who's will to go out their way for you.

On b) side-projects are good here as you suggest, particularly when you're young. You always want to be able to give examples of things you've done (check out the STAR method), and more projects means more to talk about and more chance you're bringing that X factor to the table.

Right now if you're into ML, others in the thread may disagree, but maybe give an LLM project a go? I'm recruiting for an ML-adjacent role (vis/analyst) right now, we're having ML practitioners apply, and only one or two candidates have any experience with LLMs. Total differentiator. We're too busy to learn stuff, would much rather get someone in whose time isn't yet eaten up to check it out. Have a head start.

c) Actually pretty rare and pretty easy to spot most of the time. I hope that's not you, I spent a while on this ;-)

Good luck!

I'm a big fan of the book "The Tech Resume Inside Out"[0], it may be helpful to you.

The best thing I learned from the book was that for some positions, interviewers weigh your experience more heavily than your side projects.

This, like all advice on this topic, highly depends on the company, the individuals interviewing, and your side projects.

I typically think of it this way.

When you are fresh out of college you've had little to no professional experience - the most you've had is probably an internship. For an employer to hire you, they'll probably evaluate your internships, school work, and personal projects. It's evidence of your knowledge and how well you'll fit into a role.

After your first job - it's much different. Employers care much more about your experience, because you've worked within scenarios that you'll work in at their company. With fresh graduates, it would be unfair to evaluate them on years of working experience - because they won't have any - which is how personal projects come into play.

An employer will want to hear more about your experience at X company, because you've worked on things that have users, scale, and issues that come with all of that and more - which personal projects sometimes do not have.

That being said, personal projects can matter more if: 1) You are changing tech entirely, so you have a project to act as evidence of your newly gained knowledge, 2) Your personal project is running somewhere and has users, and/or 3) you work on open source projects. There's probably many more reasons that I'm missing.

I'm typing all this out because for me I weighed personal projects much too heavily. My first company had extremely outdated code and custom frameworks everywhere - I was afraid that my experience didn't mean anything. I kept on trying to find time to work on projects, and which led me to never try interviewing - because my projects were never done. Reading the book I suggested helped me to break out of this belief - and led me to find a new position.

Aside from all that I've said - the other things you suggested are good: taking interviews as practice and going through interview exercises.

Pramp[1], and other resources people have recommended here, are really good to practice with. That being said - the best practice is to be in an actual interview. I highly recommend finding companies that you aren't that interested in and interviewing there.

You may find that you are much less nervous! Going into an interview not caring about the outcome and maybe even expecting to fail really calms the nerves. Additionally, if you pass the interview and find that you actually like the company - then more power to you. Accept the offer and cut your practice short.

My final piece of advice - I know it is tempting to take time off to practice - but the best time to find a job is when you are employed. It's less nerve wracking knowing that you still have a way to make money if you fail the interview you are in.

As I mentioned previously, this always depends. For example, if you're living with your parents rent-free and your expenses are really low - then it is up to you. For many other people, it could lead to situations where you are running out of funds, and now you have to take the first offer you get.

[0]: https://thetechresume.com/

[1]: https://www.pramp.com

As a hiring manager, there are a few very basic things that any inexperienced candidate can do to radically improve their chances and these have been true in all the institutions where I've been a hiring manager (from big corporates, investment banks, tiny startups, software companies, media companies, whatever):

1) Do some research. Know what the company does and some of the basics of how their industry functions. Try to know where the money is coming from etc. This base understanding will help you not to come across as a total liability.

2) Do some research (2). Read and reread the job description or if unclear give the recruiter a call and ask them what they are really looking for. The job spec should have some info in there and it would be good to decompose it a bit.

- Stuff they will expect you to know. eg "We're looking for a pytorch dev...". OK you need to know python and pytorch. Yes if you've been doing tensorflow still apply, but play around with pytorch a bit going into the interview so you know a bit about the differences. Say you've mainly done tensorflow but you've been using pytorch and it's been faster/slower/more ergonomic/whatever. Try to be positive though - Noone wants to hire someone who is going to spend all their time whining about the tech stack.

- Stuff they will expect you to be able to do. eg "...to help optimise our data ingest and embedding thingummybobber." OK so as well as basic ML dev stuff I'm going to need to know a bit about data wrangling. Maybe brush up on sql and a few other things to do with making data pipelines, cleaning data etc. Or maybe it mentions training so reread your stuff about gradient descent, regularization etc. You don't need to be the world's expert but you want to give yourself the best possible shot.

- Characteristics that are desireable in some way. eg "... The ideal candidate will have some knowledge or experience of ML as it is applied to customer-facing yadda yadda". OK so scratch your head about what you've done that you can say relates to this etc.

Ideally for each of the main things you have thought through how this applies to you in some way and have some bullet points in your head ready to go if you get asked.

For a first job they aren't expecting you to know everything so the main things they'll be looking for is your potential. Do you seem smart? Are you going to be able to learn quickly? Are you likely to be able to get shit done? etc. Try to think through what you might be able to say that is evidence of each of those things. Smart: think of something (even unrelated) that you have learned deeply. Eg you became the resident expert in regexes in your computer lab at school or you got totally into abstract algebra and nerded out on that or whatever. Quick study: When you went to school maybe you only had done Javascript dev and then you had to pick up python or vice versa. Some evidence that you can learn and adapt.

You can really help yourself a lot if you think about these things so you have something at your fingertips when they ask you a question about how you're going to be able to learn.

interviewing.io comes up on HN fairly often. Does anyone have experience with them? On the surface it looks nice and might be "just the thing" in this situation, but can anyone pitch in with whether or not there is substance to it?

accept every recruiter that contacts you on LinkedIn the moment you click "available". Don't filter too strongly, just accept everything that won't be a hassle to try the interview at. Then just practice through real interviews.

Only way to get interview experience is to do a lot of interviews.

my approach on this is consider the first 10 to 20 interviews i get as practice interviews.

just throw yourself in the pool, you'll learn to swim.

Ask friends or strangers online to interview you and give feedback. I do this a lot with my team and do mock interviews. I want my team to promote and make more money. Maybe you can ask your boss for a mock interview and show them a position you are interested in. Lot's of resources to leverage. Hell I bet a lot of people here would help you out.

My piece of advice is to remember your star format, and if you don't know exactly how to do something. Tell them, and then walk them through how you would do it based on what you know. tldr; throw a hashmap at it.

Selling yourself IMO is a pretty distinct skill. I know great MLEs that suck at interviewing, and people who BS their way through interviews, sound great, then suck at the job.

I disagree.

Especially in SWE interviews

Interviewing, and engineering, in this case coding, are two different skills. There are people that are good at only one.

It's wise if this person to seek advice on something they feel less confident and experienced at. This trait will swerve them well in their life.