HACKER Q&A
📣 dakiol

Typical tech job interview in late 2025?


A year ago or so, I went through the "classic" tech interview. Not faang, but not an unknown company either, so something one or two levels below faang. Good pay, lots of senior+ engineers, and a tough environment where you can’t really slack off (they call it "challenging").The process was the usual:

* Intro call with a recruiter to get to know you and all that crap

* Live coding or a take-home assignment (plus a follow up to explain the code). No AI or Googling allowed

* System design interview. Again, no AI or Googling

* Interview with an engineering manager. Behavioral interview questions, same rule: no AI

* Team/culture fit

Now I’m wondering how interviews look today. I use LLMs for about 50–70% of my projects (mostly greenfield ones), and they’ve become just another tool in my workflow; like CI/CD, testing, datadog, or debuggers, to name a few. So I’m not sure if I should prepare for interviews like before, or start integrating LLMs into my prep.

It feels odd to imagine a live coding interview with an LLM tbh, where I’d have to pretend to think through the problem while basically guiding the model toward the solution. In practice, my process is more trial and error, almost brute force, but it works nice, kind of like sculpting stone. Like I don't think anyone would judge too harsh on the way you use debuggers, as long as you get the job done... I have the same feeling about how one uses LLMs, but since they are relatively new, I guess one needs to fake how the usage goes (so that one passes the interview).

Thoughts?


  👤 luponius Accepted Answer ✓
Had interviews last year insisting the use of llms and others tolerating it. Our head wants to introduce codex in ohr workflows now so pretending you're not using them or joining a team that swears off them better have a very good reason I suppose?