A small, intentionally imperfect task tracker. Your job is to review the codebase, identify the highest-value issues, and submit a focused patch.
We want to see how you improve an existing codebase under a realistic timebox — not how much boilerplate you can generate. The strongest submissions are small, focused diffs paired with clear reasoning and genuine understanding.
We care about:
- Judgment — what you fix first and why
- Debugging skill — across frontend, backend, and SQL layers
- Communication — can you explain tradeoffs clearly?
- Understanding — do you actually understand what you changed and why?
We assume all candidates are using modern AI tools (ChatGPT, Claude, Copilot, etc.) — that is completely fine. What matters is that you understand the bugs you find, the fixes you apply, and can explain them in your own words and handwriting.
| Layer | Technology |
|---|---|
| Frontend | React 18 + Vite 5 (JavaScript) |
| Backend | Spring Boot 3.2 + Java 17 |
| Database | H2 (in-memory, zero setup) |
| SQL ref | Oracle PL/SQL artifact in db/ |
The Oracle PL/SQL file in db/oracle/ is a reference artifact — it mirrors the app's query logic but does not run locally. You are welcome to review and improve it.
- Spend no more than 90 minutes (including setup, fixes, and write-up).
- AI tools are expected and completely fine to use.
- Judgment, clarity, and tradeoffs matter more than completeness.
- You are not expected to find or fix everything.
- Run the app locally (see setup instructions below — install dependencies first).
- Explore the codebase — frontend, backend, SQL, and the Oracle artifact.
- Identify and fix the highest-value issues you can find within the timebox.
- Keep changes focused — a small, high-quality diff beats a large rewrite.
- Do not rewrite the app — this is a patch exercise, not a rebuild.
- Add a
NOTES.mdfile at the project root (see below). - Add handwritten explanations — photographed and included in your repo (see below).
For each bug you found and fixed, write an explanation by hand on paper covering:
- Where the bug is (file, line, layer)
- How you discovered it
- What the root cause is
- How you fixed it and why you chose that approach
Photograph or scan your handwritten notes and add the images to a handwritten/ folder at the project root. Clear, legible handwriting is sufficient — we are not judging penmanship. We are verifying that you genuinely understand what you fixed and can explain it without relying on AI-generated text.
Submissions without handwritten explanations will be considered incomplete.
Write a short file (under 300 words) covering:
- Summary of changes — a brief overview of what you fixed (detailed explanations go in the handwritten notes)
- What you chose not to change and why
- The biggest remaining risk you see in this codebase
- What tools/AI you used and how (e.g., "used Claude to draft the debounce hook, then adjusted the delay")
Be honest and specific. We value self-awareness over perfection.
- Java 17+ (run
java --versionto check) - Node.js 18+ (run
node --versionto check) - No Docker required. No external database required.
cd backend
./mvnw spring-boot:runOn Windows, use mvnw.cmd spring-boot:run instead.
The API starts on http://localhost:8080.
cd frontend
npm install
npm run devThe app starts on http://localhost:5173.
The Vite dev server proxies /api/* requests to the backend automatically.
- Start the backend first (port 8080).
- Start the frontend second (port 5173).
- Open http://localhost:5173 in your browser.
- To stop either service, press
Ctrl+Cin its terminal.
| URL | Description |
|---|---|
| http://localhost:5173 | App UI |
| http://localhost:8080/api/tasks | API — all tasks |
| http://localhost:8080/api/tasks?q=api | API — search by term |
| http://localhost:8080/api/tasks?status=OPEN | API — filter by status |
| http://localhost:8080/h2-console | H2 database console |
H2 console connection: JDBC URL jdbc:h2:mem:taskdb, username sa, no password.
- Open http://localhost:5173 — you should see a table of tasks.
- Type a search term (e.g., "api") — results should filter.
- Select a status from the dropdown — results should filter further.
- Try the API directly:
curl "http://localhost:8080/api/tasks?q=api&page=1&pageSize=5"
- Click "Use this template" on the GitHub repo page to create your own copy (do not fork — use the template button).
- Keep the folder structure and startup commands unchanged.
- Make your changes and commit them.
- Add your
NOTES.mdat the project root. - Add your handwritten explanation photos in a
handwritten/folder at the project root. - Push to GitHub.
- Ensure the app still runs with the same setup commands before submitting.
- Share the repo URL with us.
- Earlier complete submissions are prioritized in our review queue and interview scheduling.
- The ideal latest submission time is within 48 hours of receiving the assignment.
- Late submissions may be deprioritized in scheduling.
Before sharing your repo, verify:
- App runs with the original setup commands (
./mvnw spring-boot:runandnpm run dev) -
NOTES.mdexists at the project root -
handwritten/folder exists with photos of your handwritten explanations - Handwritten notes cover each bug you fixed (location, discovery, root cause, fix approach)
- Code changes are committed and pushed
- You have not accidentally included
node_modules/,target/, or other build artifacts
After we review your submission, we will schedule a short call. Be ready to discuss:
- What you fixed first and why you prioritized it
- What you chose not to fix
- Any subtle issues you found or suspected
- Any future risks you noticed in the codebase
- Your handwritten explanations — we may ask you to walk through them
- How you used AI/tools — where you accepted suggestions and where you overrode them
- How you would approach the issues differently with more time
Backend won't start
- Ensure Java 17+ is installed:
java --version - On macOS, if you get
Permission denied, run:chmod +x backend/mvnw - On Windows, use
mvnw.cmdinstead of./mvnw - Check that port 8080 is free:
lsof -i :8080(macOS/Linux) ornetstat -ano | findstr :8080(Windows)
Frontend won't start
- Ensure Node 18+ is installed:
node --version - Run
npm installbeforenpm run dev - Check that port 5173 is free
API returns errors in the browser console
- Make sure the backend is running before the frontend
- The Vite proxy forwards
/api/*tolocalhost:8080— if the backend is down, requests will fail
H2 console won't connect
- Use JDBC URL:
jdbc:h2:mem:taskdb - Username:
sa, password: (leave blank) - The console is only available while the backend is running
This codebase has issues at multiple levels — some obvious, some subtle, some that are really future risks rather than current bugs. You are not expected to find or fix everything. Focus on what you believe is highest value, explain your reasoning, and stop when the timebox is up.
Good luck.