Working at Atlassian
Atlassian can hire people in any country where we have a legal entity. Assuming you have eligible working rights and a sufficient time zone overlap with your team, you can choose to work remotely or from an office (unless it’s necessary for your role to be performed in the office). Interviews and onboarding are conducted virtually, a part of being a distributed-first company.
With a sufficient timezone overlap with the team, we’re able to hire eligible candidates for this role from any location in Australia and New Zealand. If this sparks your interest, apply today and chat with our friendly Recruitment team further.
Job Description
Atlassian is looking for experienced and talented engineers to join our team! These Product and Platform teams are looking for innovative Frontend developers to help us build for the future. You’ll be responsible for the design, build and maintenance of product and platform services, and infrastructure that powers Atlassian Cloud. We build always-on, low-latency, high-concurrency micro-services and systems that scale for millions of users. This is a role with broad technical responsibilities across all our products with greenfield projects and technologies, not a product maintenance type of role. You will play a key role in shaping the Atlassian Cloud Platform. Using your programming expertise and deep understanding of modern web architectures and distributed systems, you will help future-proof our established products by designing, implementing, integrating, tuning and issue resolution new micro-services, software libraries, tools and applications.
More about our team
Work with a team of amazing developers and designers to build simple, beautiful and consistent user experiences for our web apps. We are always growing, learning, and adapting, in and out of the office. Our teams are crazy smart and direct and we ask hard questions and challenge each other to constantly improve our work. We are driven but team oriented. We’re dedicated to agile methodology and big believers in ‘lean’ (which means we don’t do documentation for documentation’s sake). We know the importance of validating our assumptions about users and implement various types of testing to prove assumptions right or wrong. Our bottom line is improving our user’s experience – no matter what.
On your first day, we’d love for you to have:
It’s great, but not required, if you have: