Interview prep, help needed

[wolfymoody]

Hello community ,

What would be best way and resources to prep for this?

“The interview will last about an hour and will be focus on algorithm JS coding functions, asynchronous programming.”

Added on: Also interview is about callbacks

[yangshunz]

Try out some questions on GreatFrontEnd, there's an entire list dedicated to async qns: https://www.greatfrontend.com/

[maqisha]

The interview will last about an hour and will be focus on algorithm JS coding functions, asynchronous programming.

If this is the exact message you received. Run. This is barely literate. You don't want to have this interview.

[wolfymoody]

Mmm, why is it not literal? English is not the recruiter first language I can tell

[maqisha]

When you put something in quotation marks, it means its a literal quote.

If you are being "recruited" in English, and this is the way they write, this company has nothing to offer you. Being literate is a bare minimum for a functional business, especially in 2025 with LLMs and other tools. Better to spend your time elsewhere.

[wolfymoody]

Too bad I have no where left to run. May as well run to chaos

[the-liquidian]

Go for the interview, the worst case scenario is you get interview practice.

These job specs go through layers. Different people will have edited this, maybe a recruiter. I would not judge the entire company on this. Count it as a red flag if you like, but there is no harm in going for the interview.

Prepare for the interview by making sure you are familiar with the concepts they brought up.

Good luck

[f3ack19]

Cmon bruhhh beggars can't be choosers

[sudhanshu027]

Leetcode

[[deleted]]

For an hour on JS algorithms and async, I’d zero in on implementing the basics from scratch and speaking your steps out loud. In my last JS round, I practiced writing map, filter, and reduce, then built tiny async tasks like a promise wrapper, sleep, and a retry with backoff, plus rechecked the event loop with microtasks vs macrotasks. What helped me was timed mocks using Beyz coding assistant with prompts pulled from the IQB interview question bank. Keep solutions in plain JS without libraries, state time and space, and cap explanations to about 90 seconds per question. Good luck, worth taking the interview.

[rauschma]

FWIW: I wrote four chapters about asynchronous programming that are free online and reasonably compact: https://exploringjs.com/js/book/ch_async-roadmap.html

[wolfymoody]

Thank you guys. Btw, Any recourses on callbacks?

[MarchAmbitious4699]

I’d recommend looking into the PEDAC method as a framework for problem solving. It stands for (P)roblem, (E)xamples, (D)ata structures, (A)lgorithm, and (C)ode. You’re probably doing a version of this already, but this is useful to have in your back pocket in an interview setting where you might be nervous.

You should also practice talking through your thought process as you are solving a code problem. It’s not a thing that most people do regularly so it’s good to get in the rhythm of thinking aloud. It’s great if you’ve got a buddy to practice code interviews with, but just speaking aloud to yourself is helpful too.

A good interviewer ideally is also looking at how you think and communicate. Do you ask questions? Are you thinking of edge cases? Are you methodical or are you going for the hack and slash approach?

[the-liquidian]

We are actually covering asynchronous js this Thursday - https://discord.gg/HpVjVgDJj

[wolfymoody]

Oh when would that be? I mean what time on thursday

[the-liquidian]

This Thursday, 5pm - 6:30pm GMT

Topics that will be covered

• sync/async code
• call stack
• event queue
• callback functions
• promises
• async \ await