the more i looked into this, the more i realized this isn't really hypothetical anymore
companies like bloomberg and goldman are already experimenting with AI-assisted interviews where you're dropped into a codebase and expected to actually figure things out.
and tbh for actual engineers, that part isn't new. that's basically the job. you get a repo, you get a ticket, you find the relevant code, make the change, test it, etc.
what i'm more curious about is people who've mostly learned through AI/vibe coding and are now trying to prepare for interviews like this.
because prompting something into existence is very different from being dropped into a repo you've never seen before and having to know where to look, what to ask, whether the AI is wrong, and how to verify the change.
that's mostly what i've been building Groundwork around — unfamiliar repo, ticket, IDE, terminal, tests and an AI assistant.
i'm mainly trying to figure out whether this would actually be useful for interview prep though.
if you were preparing for this kind of interview, would you use something like that?
and what part would you actually want to practice?
When you make a post, there is a separate field to enter it.
Son of a biscuit… To the Docs!!!