Full Transcript
Loading transcript…
I was laid off by Atlassian
Watch with subtitles, summary & AI chat
Add the free Subkun extension — works directly on YouTube.
- Watch
- Subtitles
- Summary
- Ask AI
Software engineers and developers interested in system architecture, internal platform engineering, or preparing for high-level technical interviews at major tech companies.
TL;DR
After eight years at Atlassian, a software engineer reflects on their career following a layoff. The video breaks down the technical interview process and provides a deep dive into building internal infrastructure, specifically an open service broker for self-service load balancing.
Key Takeaways
- Asking interviewers to define success for a role 12 months in the future helps candidates understand specific business needs and demonstrates a proactive, results-oriented mindset during the hiring process.
- The 'Open Service Broker' pattern effectively abstracts complex infrastructure provisioning, allowing internal developers to request resources like load balancers through standardized APIs rather than manual configuration.
- Building robust internal platforms often requires an asynchronous architecture, using message queues like SQS to decouple web requests from long-running provisioning tasks, ensuring system reliability and scalability.
- Technical evolution is a natural part of software lifecycles; migrating from library-heavy frameworks like Connexion to more performant, modern alternatives like FastAPI can improve maintainability and performance over time.
- Troubleshooting exercises that require candidates to prompt for information during a simulated incident are highly effective at evaluating real-world problem-solving skills and technical intuition under pressure.
- New hires in large organizations often face a 'drinking from the fire hose' experience, requiring them to quickly absorb vast amounts of information to become productive contributors.
In This Video
- 00:00Reflecting on Eight Years at Atlassian
The author reflects on their eight-year tenure at Atlassian following a recent layoff, aiming to share technical insights and lessons learned.
- 00:56The Interview and Hiring Process
A deep dive into the technical interview process, including coding quizzes, architectural discussions, and the values-based interview that secured the job.
- 04:17Building the Open Service Broker
The author discusses their first major project: building an internal service broker to facilitate self-service resource provisioning for developers.
- 06:52Technical Evolution of the Broker
An overview of the technology stack migration from Connexion and Flask to FastAPI, including the asynchronous architecture using SQS and DynamoDB.
- 09:25Provisioning Infrastructure and Load Balancing
Explaining the workflow of handling provisioning tasks, such as DNS and load balancer configuration, to support internal service traffic.
- 10:00Unraveling Complex Infrastructure Requirements
The author begins to address the necessity of replacing existing load balancers and evolving the platform's edge infrastructure requirements.
Questions & Answers
What was the Atlassian interview process like?
The process included a HackerRank coding quiz, a technical interview involving a Cloudflare white paper, a troubleshooting exercise for a real Atlassian incident, and a values interview.
What was the first project the speaker built at Atlassian?
The speaker built an Open Service Broker (OSB) to facilitate self-service load balancer provisioning for internal developers, allowing them to provision resources like databases or load balancers.
What technologies were used to build the Open Service Broker?
The project was initially built using the Connexion library with an OpenAPI document, then migrated to Flask, and eventually to FastAPI, using DynamoDB and SQS for asynchronous task handling.
How does the Open Service Broker handle provisioning requests?
The web server receives a request, pushes task details into an SQS queue, and a worker processes the task asynchronously. The client polls the server until the worker updates the database with the completion status.
Why did the speaker create this video?
The speaker wanted to reflect on their eight-year tenure at Atlassian, share technical insights from projects they built, and provide inspiration or guidance to others in similar situations.
Key Terms
- Open Service Broker — A standard API specification that facilitates the provisioning and management of cloud services and resources for platform developers.
- Connexion — A Python framework that automatically handles API routing and validation based on an OpenAPI specification document.
- Latency-based routing — A DNS routing method that directs traffic to the server endpoint with the lowest latency for the end user.