Atlassian | Full Stack (front-end lean) | Karat
[Atlassian] - [Full Stack Software Engineer] - [Karat]
A recruiter got in touch with me. Based on their email, I expected a longer call with several behavioral questions, but it turned out to be a standard 30-minute conversation where we mainly discussed logistics and salary expectations. I had initially wanted a front-end position, but the recruiter suggested I might have more team-matching options if I went the full-stack route. For the full-stack interview, you can choose to focus more on either front-end or back-end, which slightly changes the interview format. During the call, we also scheduled the Karat interview. Cool thing about Karat is that they provide interview availability almost 24/7, including weekends.
-
(20 mins) Can’t remember everything, but basically: explaining everything that happens on a rideshare app between the user confirming their ride and to the point they get a ride/driver confirmed. Talk about the process while including networking, scalability, security, error handling, etc. [Basically talk for 20 mins about everything that happens from the front-end to the back-end).
-
The interviewer showed me an image of an input bar with a search button next to it. I had to recreate the image using HTML and CSS (no JS needed). There were around 7 things you needed to complete, such as having the input and button next to each other with no space in between. Changing the width of the input to at least 2x of the button. Having placeholder text inside the input, and that text needed padding. Two corners of the input had to be rounded. Two corners of the button had to be rounded. This part was rather easy and straightforward. I used things such as
display: flex; border-top-right-radius: 8px, input::placeholder {padding: 10px},You are allowed to use Google search. Coding is done in Karat Studio (similar to coderPad) and can be run.
- Given an API returning a list of todos, we want to fetch the list and display all todos. Use this endpoint URL to get the todos: https://dummyjson.com/todos?limit=10&skip=80. If time allows, add a button that loads 10 more to-dos every time you click on it. Once 100 to-dos have been rendered, the button should no longer work. A similar question was found here, but I didn’t have to group by userId Atlassian Interview Experience -Frontend Software Engineer | by Tanya Singh | Medium . This all has to be done in vanilla JS, and you are allowed to use Google search. Make sure to brush up on DOM manipulation, such as
Document.createElement('div')andelement.appendChild(otherElement)
The recruiter reached back with my results the next business day. 