r/Backend • • 15h ago

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

6 Upvotes

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.


r/Backend • • 10h ago

Share Private Client Demos With Six-Digit Email Codes

Thumbnail
instawormhole.com
2 Upvotes

r/Backend • • 23h ago

I built an API client in Go where the desktop app, the CI runner and the load tester all share one send function

0 Upvotes

i'm the author. gostman is an API client for REST, GraphQL, gRPC, WebSocket, MCP and a few more. desktop app, CLI and a web version. i've been building it in Go since april 2025. it's MIT licensed with no account and no paid tier.

i know this sub has seen a few postman alternatives lately, and bruno and yaak are good. i kept going because the things i actually needed for backend work kept sitting behind some tier: data-driven runs, pulling secrets from vault, pushing collection changes from the app. here all of that is in the download.

the backend-ish parts that might be interesting:

one send function for everything. early on there were three copies of the HTTP code: one in the desktop app, one in the CLI runner and one in the proxy the web version goes through. every fix had to land three times and they drifted, which is the worst thing a testing tool can do. now there's one engine.Send(ctx, req, policy). the desktop app, gostman run, gostman load and the web proxy all call it, so a request that passes in the app behaves the same in CI.

collections are plain YAML in a folder. one file per request, so a PR shows the one line that changed (url: /anything/signed -> /v2/anything/signed) instead of a giant JSON export diff. there's a git panel in the app (diff, commit, push, branches) but your normal git works too.

the "one big JSON file" mistake. the desktop app used to keep everything in one gostman.json. turned out a response that set a cookie rewrote your whole collection file, which took 1.4 s next to 10k saved requests. history had the same problem. i split cookies and history into their own files and saving cookies went to about 1 ms. i also stopped writing empty auth and options blocks on every request, which halved the data file (6.7 MB to 3.6 MB with 2,000 requests). nothing clever, just don't rewrite the world on every small write.

CI and load from the same collection. gostman run path/to/collection exits non-zero when a check fails, takes CSV/JSON data files and writes JUnit, HTML or JSON reports. gostman load gives latency percentiles with staged ramps.

secrets. variables can read from vault, AWS, azure, GCP, 1password, bitwarden, keepassxc or the OS keychain, so nothing sensitive ends up in the YAML you commit. gostman scan catches the ones someone typed in anyway.

what it doesn't have: hosted collaboration, SSO or cloud monitors. there's no account, so there's nothing to host them on.

if you run API tests in CI i'd really like to know what makes you drop a tool, because that's what i'm trying to get right.

repo: https://github.com/kunalgoesbyken/gostman

web version, no install: https://gostman.com/web