I was contacted by a recruiter via LinkedIn and agreed to interview.
The first stage was a phone screening with a recruiter, which was pleasant. The recruiter had to read some official sales pitches for Jira, Confluence, BitBucket, etc., which was a bit tedious as I’m familiar with these tools. In the end, we scheduled a technical phone interview.
The technical interview began right on time and was conducted via Hackerrank Codepair. The task was to architect a stream API in which users can post values and functions to the stream and subscribe to the changes.
It was pretty difficult for a 45-minute session and was not relevant to front-end engineering, save that it was written in JS. Though I got stuck in the middle, I was able to get unstuck and complete the task, getting all the unit tests passing with 15 minutes to spare. My interviewer was respectful and collaborative and told me I did well.
The next morning at 8 a.m., I received an email informing me I would not move forward. Though I was a bit surprised, I appreciated the quick decision.
Overall, a quick, pleasant process.
Create a basic implementation of a Streams API. The user should be able to push values to a stream and subscribe to values that are pushed to that stream.
For example:
javascript const z = new Stream(); z.subscribe((value) => console.log(value)); z.subscribe((value) => console.log(value * 2)); z.subscribe((value) => console.log(value * 3)); z.push(2);
Should return:
2 4 6
The following metrics were computed from 1 interview experience for the Atlassian Software Engineer - Front End role in Mountain View, California.
Atlassian's interview process for their Software Engineer - Front End roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Atlassian's Software Engineer - Front End interview process in Mountain View, California.