r/SpringBoot • u/Ok_Childhood1395 • 16h 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.
2
u/EternalSoldiers 15h ago
Honestly, I'd spend your time building something small with AI if you haven't yet. It's not going to come off as very natural if you've only thought about what you'd prompt and the workflows you'd use.
If they want to see you effectively use AI, showing you have a workflow that works for you is probably important. "I prefer Claude Code in the GUI (or terminal) over Cursor with a few custom skills for Spring Boot best practices, security and performance reviews. I use Opus 5.5 on high for most things. If it's a larger task and more complex task, I'll use Fable as an orchestrator. While Sonnet saves cost, I've noticed the quality is quite up to par with what I'd expect for production quality code.", etc.
You can glance over what you'd make a skill for in an open source repo to get a good feel for it, like these. Make sure you understand what should go in the CLAUDE/AGENTS md files. Code reviews are also an important topic.
8
u/manyxcxi 15h 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/Tomato_Sky 14h ago
What manyxcxi said is 100% what I’d tell you too.
Please let us know how it goes. We haven’t incorporated Spring Boot and AI in the interview process. As in how to directly use models harnessed in a spring boot environment for maintenance and such.
My own style is to refer to your past projects and gauge how much you understood what and why you were doing at the time. Over in other subs they make it sound like there are pop quizzes and people are measuring your form as an athlete lol. I’ve never experienced that, but I have worked with some people who would.
The key to being a safe candidate to trust with an AI workflow is being comfortable enough to spot the hallucinations and weaknesses.
I used to onboard and develop our interns before we kinda paused it. And as confident as students sound on reddit, they don’t match it- there’s always so much room to grow… even for myself! But imagine agents as a group of wide eye’d interns who do everything mostly right, but take a lot of patience, a strong foundation of knowledge, and good judgment to manage them.
I like to say 80% of the applications meet the minimum technical requirements. The interview is where I see demeanor, personality, poise, and awareness. If I ask you how to how to handle multithreading and you tell me that you had a previous project that had batch submission errors until you used @Async, I’m rolling with you and that’s an A- answer. If you said “I created a battle simulator for my group of friends to settle a beer bet, and needed to shoot off 36 HTTP requests simultaneously…” that’s an A+.
But please let us know how it goes. Best of luck! If they get a little too specific to a Spring Boot specific workflow, be cautious of the environment you’re joining.
•
u/nian2326076 8h ago
Using Cursor and Claude effectively involves understanding their strengths. For complex codebases, focus on prompts that ask them to explain code logic or suggest modifications. For smaller bugs, try specific prompts like "What's wrong with this code?" or "How can I optimize this section?"
Before your interview, practice with similar AI tools to get comfortable. If you're looking for relevant job opportunities, you can use LandOffer to help you find roles that fit your skills in Java and Spring Boot.