The first step was to discuss with the recruiter, who provided details about the job and what to expect. The second interview was a system design interview. During this hour-long session, I discussed an example system design, prompted by the interviewer, and drew it out in real time.

A few days later, I received a call back stating I had performed wonderfully in the system design interview and could expect to move forward. I was then ghosted for about a week.

Subsequently, they called to inform me they were no longer hiring and might reach out in a few months if other positions opened.

Honestly, I didn't want to work there, given the rumors about Atlassian being an absolute nightmare of a company. The interview was good practice, but I don't appreciate the ghosting, lack of communication, and then stringing someone along only to deny them in the end.

I asked the interviewer about Atlassian's work-life balance, and their answer was very concerning.

Atlassian wants to build a simple scheduling system that can execute one-off HTTP requests at a specified time.

Consumers are internal Atlassian services only, and they may use this system to schedule requests to be executed in the future. For example:

A consumer can schedule a request to https://myservice.com/api/items/_delete to be executed on Sunday at 1 AM. On Sunday at 1 AM, the scheduling system must execute the HTTP request.

Requirements

The system must:

• Provide an interface for scheduling HTTP requests at a specified time.
• Execute an HTTP request at a specified time.

Initial release expects 10 scheduling requests per minute.