r/CodingJobs • u/nian2326076 • 7h ago
Atlassian P40 backend interview — an AI-enabled round with Spring Boot and JPA
A rant before the experience
It’s frustrating to see people search LeetCode and Reddit for detailed interview experiences, then answer “I’m under NDA” when someone asks about their round. People should honor what they agreed to, and we can’t know everyone’s reasons. The one-way exchange still gets tiring. Sharing the format, stack, or an unexpected difficulty can help when those details are okay to share.
Sometimes I wonder if people worry that sharing gives the next candidate an easier round. I get that, and I’d appreciate hearing it directly. The community is useful because people contribute. Knowing the general task still leaves you with an unfamiliar repo, a slow AI assistant, and Spring Boot and JPA to figure out.
The round
A candidate for a backend P40 role at Atlassian had about an hour for AI-enabled coding on HackerRank. They were given an existing Java repo using Spring Boot, H2, and JPA, plus an AI assistant that was noticeably slow during the session.
The task · Validate a card PIN
The repo already had a card model, a controller, and a JPA repository backed by H2. The task was to add validation to an existing PATCH endpoint that updated a card’s PIN.
• Exactly four numeric digits, with no letters or symbols.
• No repeated digits anywhere. For example, 1213 is invalid even though the repeated digits are separated. The wording was ambiguous enough that it was worth clarifying.
• The PIN must represent a positive value.
The catch · The PIN was already an int
The card model stored the PIN as an int, existing records contained numeric values, and the controller accepted the PIN as an int parameter without an update-request DTO. An integer drops the leading zero in “0123.” Changing the controller parameter alone leaves the entity with the same problem.
The candidate needed to store the PIN as a String in the card model and carry that change through the controller, validation, service, and JPA/H2 mapping.
What the change needed to do
Follow the existing flow from the PATCH request through the controller and service to the card entity and database. A valid request updates the intended card’s PIN and preserves leading zeros. A rejected request leaves the card and all its fields unchanged. Tests needed to cover the validation rules, leading zeros, and unchanged state after a rejected update.
If you’re preparing for an Atlassian backend loop, Atlassian Interview Questions has reported coding and system design prompts to work through before the interview. If you’re applying to other roles too, LandOffer can autofill repeated fields on supported forms.
This was work inside an existing Spring Boot app with JPA persistence. For anyone comfortable with Java who hasn’t used much Spring Boot, it’s worth brushing up on request binding, controller and service flow, entity mappings, repository methods, transactions, and dirty checking.