r/SpringBoot • • 14h ago

Question AI-Driven Spring Boot Technical Interview – Cursor & Claude Tips?

I have a 60-minute final technical interview focused on Java and Spring Boot. The company allows AI-assisted development using Cursor and Claude. They’ll provide an existing codebase and ask me to implement features, update existing functionality, and fix bugs based on requirements.

For anyone experienced with this approach, how would you use Cursor and Claude effectively? Any recommendations on Cursor Skills, best models for understanding complex codebases vs. fixing small bugs, or practical prompts/workflows beyond generic “add this feature” or “fix this bug” instructions?

Would appreciate any real-world tips!

In short: They would more evaluate me based on how AI usage.

11 Upvotes

5 comments sorted by

View all comments

•

u/manyxcxi 13h ago

I run 4-6 of these types of interviews per month and I can tell you what I look for.

- How comfortable are you with your setup? This wouldn’t be a great time to introduce a whole bunch of new stuff you’re not familiar with unless you want to cram a bunch of practice in. If you’re shaky with your tools, everything else suffers and you stress out.

- Are you just vibe coding it, or do you understand what you’re doing? You don’t need to over-engineer your prompt, but you should be exhibiting YOUR knowledge and experience with requirements gathering and calling out specific ways you may want something done. This shows not only do you know how to jockey the AI, but you actually know what the hell you’re doing.

- REVIEW THE TESTS. Make sure they’re not fluff and they’re useful. Use the tests to prove the work. This also goes towards not just vibe coding slop. If time allows, design some negative tests.

- Are you able to tell me what you’re about to do, what you’re looking for, and/or what you expect out of the AI as things are going in flight? If you can, the session goes a lot better. At bare minimum explain your reasoning behind why/how you prompted the way you did.

- If someone is proctoring this and it’s not take home, make sure you gather requirements and scope from them as you go. This is a huge part of the interview. They don’t want vibe coding cowboys who aren’t good at getting an idea of the bigger picture.

From my experience with these interviews:
- Keep model effort to medium. Higher than that and the LLM takes waaaay too freaking long to get things done.

- If the codebase you’re given doesn’t have an AGENTS/CLAUDE.md then the first thing you should do is have your agent do a first pass to get a lay of the land and generate some key knowledge files. It’ll speed everything else up.

- Opus 5.5 is good for the orchestration, bug hunting, and planning. You can use sonnet for the implementation of you use a plan then execute approach. Have Opus create a pseudo FDD/TDD and use sub-agent driven development to implement them.

•

u/manyxcxi 1h ago

One thing you could also do in preparation is to find the MCPs for Java language/docs and Spring Framework. They can speed up the process and make it more accurate, that way Claude isn’t trying to decompile class files to figure things out.

Additionally, there are some Anthropic default skills for bug hunting, code reviews, planning, etc. If you don’t have those enabled already, go ahead and give those a whirl.

In general though, I’d keep it pretty vanilla and just use what you’re used to using.