I have an upcoming on site interview with Atlassian and want to make sure the recruiter isnt yanking my chain. The interview is for a senior dev role (P5). But I see the schedule is very short; one round of coding, one system design, manager round, and values round. I am being considered for level 5 at FAANG and am a tech lead with 8 yoe. I thought P6 at Atlassian was comparable to Staff at other companies, but the recruiter told me it was an architect role with only 30 percent hands on coding. Is this true?
We don’t know how to interview, enjoy your luck I hope it will change in the future
The higher levels usually have more rounds. That’s why I am asking
I know, but not us, we know better 🙈
There are some formal team architects who are only P6 but they are definitely not the norm for P6. P6 is usually either be really senior coder, but still well over 50% or what other companies would call tech lead at about 50/50 (our team lead/managers are non coding and largely procedural)
The recruiter lied to me then.
Recruiter probably believed they had correct information, so it's not a lie exactly, but yeah, wouldn't be the first time a recruiter didn't know what they are talking about here or elsewhere P6 is the next level up from senior, comparable to staff or principal at places where that's the next grade up. How much architecture vs coding vs backfilling manager stuff you will do depends on the team I saw above that you are looking at Confluence, how much I'd recommend the team depends on the hiring manager although there are no outright bad ones (IMO)
At Atlassian, the interview process is pretty much the same for everyone up until P6. The only difference is the panel. The interviewers levels are the same or higher than the level you are being interviewed for. For e.g A P5 will interview P5s and below, they can’t interview P6. But there are exceptions sometimes.
With regards to whether or not the recruiter lied to you, it’s best to clarify with them. A recruiter has more insights into what the team is looking for. Some managers have higher expectations than others. Also, as fast as I know the levels are only decided after your interview and not before.
Any insight on what to prepare for interviews phone and onsite both.
Read the company values. For the most part, the values interview will be standard behavioral but much lower bullshit than the last time i went through Amazon's for "leadership principles." Usual behavioral interview tips apply: keep examples positive and it is better to stretch an analogy than to be like "no, I have no example of that" Coding is like everybody else's coding (at least as we do it in MTV) but interviewers are not standardized. Some people do multiple LC easy, some LC medium, a few people LC hard. Design and architecture interview is pretty standard. Look at how FB does it and you won't be far off. While we're not supposed to be testing AWS knowledge in particular, it helps because almost everything here is on AWS. Hiring manager interview is whatever the manager wants it to be. Sometimes its tean match, sometimes it's behavioral, and I know one Senior Manager who is pissed about losing the algorithms round and has decided to just do it as a technical round. Technical phone screen is like everybody else's
P5 is a Sr. Developer role and P6 is a Principal level role. At P5, the emphasis on coding and design is equal. Again, leveling and titling is different at every company. What team are you interviewing with?
confluence