Leidos

What's your job about?

Leidos Australia is a technology company that supplies specialist solutions to the Australian Government and other clients. I am a Cyber Security Analyst undertaking work in a full-scale cyber security project for Defence across multiple environments. I have exposure to GRC (Governance, Risk and Compliance), vulnerability management, cyber engineering, and cyber threat intelligence and threat hunt teams. I am thankful for the opportunity to work across all areas of the project and have used this time to plan which areas of cyber security I want to continue and specialize in.

The work is diverse and uses both my technical and soft skills. Knowing the cyber security landscape and threat vectors is vital. To stay on top of all things cyber, my mornings consist of reading cyber security news and reports. One task I am proud of is the development of a proof-of-concept dashboard for the internal and external stakeholders. I was able to learn a new skill set and supply new capabilities to my team.

What's your background?

I grew up in Melbourne, Australia and have been in Melbourne through primary, high school and university; however, the dream was always to move to Canberra for a graduate role.

My love for technology began at an early age, sneakily playing computer games with my twin sister instead of going to bed like we were told. The idea of working in technology was always my end goal.

While at uni, I had the opportunity to sit the e-council ethical hacking and digital forensics exams and the Information Systems Audit and Control Association (ISACA) Cyber Security Fundamentals exam.

In my final year of university, I landed a six-month internship at Victoria’s Big Build Rail Project Victoria (RPV) project office. Working with a wonderful and supportive team, I was exposed to Microsoft Azure and M365, third-party management, and the Victorian Protective Data Security Framework (VPDSF) attestation and audits. I continued learning and completed two Microsoft fundamental exams and an RMIT micro-credential in public-sector risk management. After the internship, I was asked to stay on as a Security Administrator, incorporating and managing compliance with the VPDSF.

At the beginning of my final year, I began applying for graduate roles. The purple of Leidos stood out to me and the option to work in Canberra appealed to me. I applied for and started my role in January 2023 and have enjoyed the Graduate Development Program and the meaningful work of my project. My Canberra graduate cohort has been so supportive and has been the highlight of my first year at Leidos!

Could someone with a different background do your job?

Yes, however, knowing all about technology helps! This role values and requires a passion for learning and building strong relationships—just as much as technical skills. There are plenty of courses and certificates that can help build technical skills. If you are doing rotations across cyber security domains, it is important to be willing to learn computer networking, security tooling, as well as governance and policy frameworks.

What's the coolest thing about your job?

The coolest thing is that I know there is always someone to talk to and ask for feedback without fear. I have access to a buddy, mentor, People Leader, a talented team of colleagues, and a wonderful graduate cohort. Leidos and the Early Careers team have built an environment that values both your well-being and career growth. I feel so supported in this role.

What are the limitations of your job?

There is a lot of responsibility in this role, and in my experience, I have been very self-driven. The work can have high stakes and challenging time constraints/deadlines. Those coming straight out of university may struggle to adapt to the self-driven nature of the role and tasks. Cyber security as an industry faces an elevated level of burnout due to stress, and this role is no different. The hours will change depending on the requirements of the task or the team, and you must adapt.

What are three pieces of advice you would give to other students?

• There is always something new to learn in cyber security. Continuous learning is vital in this environment.
• Find people who will keep you motivated, supported, and curious. Being around the right people will inspire you to be the best version of yourself.
• Remember to take time for yourself. Burnout is common. Building and sticking to good self-care habits and routines will help you overall.

What's your job about?

Leidos is a global science and technology company that specialises in solving complex challenges in defence, intelligence, civil, and health markets. I specifically work as part of the Mission Software Solutions sector where Leidos provides advanced solutions to areas in data analytics, system integration and critical software products essential to our mission.

The majority of my role in this space is maintaining and developing new functionalities for pre-existing or new critical software products.  Some of the technologies/tools I have been able to work on for different projects are AWS Cloud Services, Dev-Ops tools (Terraform/Ansible), Java, C#, .NET applications, and Apache NiFi to name a few. Don’t worry if you don’t recognise any of these, I didn’t either when I started!!

What a usual day looks like for me:

• The day usually begins with me logging into Teams to check any updates or messages as well as checking my calendar for the day.
• Check the Jira board for the current ticket I am working on or pick up a new ticket. A ticket represents a specific task or issue that needs attention such as developing new software features or fixing bugs.
• We have a daily standup which are brief sessions held with the project team to foster open communication as well as making sure everyone’s on the same page. Usually, we just tell each other what we are working on, blockers or challenges that we faced.
• I work through the ticket trying to solve the challenge or problem using my knowledge or researching how to solve the issue.
• I usually eat lunch with my coworkers at a communal seating area
• After lunch, I either keep writing code or peer review my co-worker’s code
• Leidos has quite flexible work arrangements, so I don’t finish at 5 pm every day. Some days I come in early and finish early or vice versa.

What's your background?

During school, I didn’t know what I wanted to be when I grew up, but I did know I had a strength in maths, physics and presenting. Because of this, I chose a double degree in Engineering (Honours) and Commerce at Monash University.

During my time at university, I didn’t want to start a corporate job until I finished my degree, so I could spend more time enjoying the different aspects university had to offer. I joined a university club called the Computing and Commerce Association at Monash and was the HR Director for it. It was a great experience and a great way to make new friends. Throughout my time at university, I also worked part-time as a cocktail bartender at a bar!! Mixology has always been a great passion of mine and it was a great job to do alongside studying.

As my final year of university approached, I began looking for graduate positions and I found Leidos through Indeed. Before discovering their job advertisement, I hadn't heard of Leidos, but after researching what they do, I was intrigued by their focus on using cutting-edge technology in areas such as defence. I submitted my application, I was then invited to complete an online assessment and then I was invited to a face-to-face interview. I got the job within a couple of weeks after the final interview!!

Could someone with a different background do your job?

I believe that anyone would be able to do this job. A lot of the job is solving problems but mainly through self-paced learning. When I started at Leidos I felt like I lacked some knowledge that I thought I should have had before starting a software engineering role. Leidos however specifically acknowledges that everyone learns differently, and they put operations in place to help accomplish your job by providing Senior Engineers and learning tools in a way that suits you. As long as you have a willingness to learn and a growth mindset you really can do anything!!

What's the coolest thing about your job?

For me, it’s understanding that I am contributing to something greater than myself and being able to work as part of a team to solve problems every day. Before joining, I always felt like software engineering was a lone wolf career, but I was so wrong. Collaboration and teamwork are such a crucial part of the job and it’s what I love the most about it at Leidos. It's the incredible collaboration of many amazing people who come together to solve a massive problem that seems impossible, yet they somehow make it possible. I think that’s incredible!!

What are the limitations of your job?

Due to the nature of the work, there can be many hours or days waiting for approvals. This can be a little hard even when you think it is quite a simple request. In these situations, you won’t have much work to do which sounds like a good problem to have but it really isn’t at times. Having said this, there is always internal learning that can be done and Leidos provides many different learning resources.

3 pieces of advice for yourself when you were a student...

• Don’t be afraid to try new things whether that be a career, hobbies, travelling or anything really. New experiences broaden your perspective of the world which I think is important.  As I got older, I understood that the “more you know, the more you realise you don’t know”, so be inquisitive!!
• Remember that your career or university whilst important, isn’t your whole life but a part of your life. Remember to balance and prioritize other aspects of your life such as your physical health, mental health and relationships.
• The last piece of advice is a quote I live by. “Don’t practise till you get it right, practise till you can’t get it wrong”. Whatever path you choose, give it your all and try your best. Keep getting better each day by taking space steps and even if you fail take it as a learning opportunity and keep going.

What's your job about?

Leidos is working to solve the world’s toughest challenges in government, intelligence, defence, aviation, border protection and health markets. As a software engineer, I help develop and maintain software for one of our customers. My team works on three separate projects, two of which are in sustainment and the other being in development. Due to the range of projects, we have a vast tech stack including React, Typescript, Rust, Java, Kotlin and more.

A common theme to our projects is that they all improve our customer’s workflow, helping them achieve their tasks in a more productive and organised manner. The projects I work on are either to replace outdated systems or manual processes.

A typical day for me includes looking at our scrum/work board to find a ticket/task to work on. This could include accomplishing the ticket/task myself or reviewing someone else’s work. The tickets range in size and can involve developing new features, patching bugs, addressing tech debt, working on research investigations or addressing user feedback.

My team also has different kinds of meetings throughout the week. This includes refinement, where we refine the tickets/tasks we have in the backlog to flesh out what exactly the task incorporates and any ideas on how to achieve it. As well as sprint review, where we demonstrate to our customer all the work we have achieved in the last two weeks.

What's your background?

I grew up in the western suburbs of Victoria where I still live today. I struggled a bit trying to figure out what I wanted to pursue as a career. As a teenager, my interests were in film and psychology. I initially went to university to study psychology but decided to stop to pursue something more creative. After self-studying creative writing for a while, I realised that I wanted to keep my creativity side for myself instead of monetising it. So, I ended up a bit lost. That was until my cousin told me all about her life as a software engineer. She let me borrow her HTML/CSS book, which I read and enjoyed very much! I had heard of coding before but seemed too low-level for me. But after reading this book, my perspective changed. Not only was it easier than I thought, but also very creative!

I ended up applying to Deakin University again and completing a Bachelor of Information Technology. Near the end of my degree, there was encouragement from staff to apply for graduate programs. I found out about Leidos’ graduate program and applied after reading about the important work they do for our society.

I was fortunate enough to be offered a role and started in 2024 as a graduate software engineer. I am currently at the end of my second year at Leidos and I am very happy!

Could someone with a different background do your job?

I believe so. When it comes to coding, people often think of a specific type of person. However, there is really no limit to what you can create with code. I often compare programming languages to a paint brush or a tool. It really depends on the individual to decide what they want to create with it. And one of Leidos’ values is innovation. In order to achieve this, and seek out the best solutions and ideas, you need a diverse group of people who come from a range of different backgrounds with life experiences. 

So, I would say not only could you do my job if you had a different background, but your uniqueness would be very valuable!

What's the coolest thing about your job?

I love the constant opportunities to learn. With each new ticket comes new experiences that improve my skills, making me feel like I am constantly improving and becoming a better developer. I never feel bored or stagnant at work, there is always a new challenge around the corner to keep my brain stimulated. I’ve gotten to learn a lot about myself and how software is created and maintained.

What are the limitations of your job?

Unlike other graduate programs, there aren’t any rotations. Leidos will find a team/project for you to be on. Sometimes this can take a bit of time depending on current state and logistics of the team/projects. I was lucky and got on a team straight away, but some of my fellow grads/interns had to wait a bit. Leidos does try their very best to put you on a project that matches your skills and interests though. 

It can also be a bit overwhelming starting as there is a lot to learn, but eventually you will get the hang of things.

Three pieces of advice for yourself when you were a student...

1. Remember to be kind to yourself and celebrate the small wins. The only person you should compare yourself to is your past self!
2. Try to get out the house more and be a part of more communities.
3. Learn about testing, Docker, Helm and Kubernetes!

I’ve landed in an amazing team that has given me great development opportunities; because of this I’m now responsible for delivering a body of work within my project. My favourite part of the job is when my team and I achieve a key milestone after many months of hard work. My role also requires me to interact with lots of people including the technical team, upper management and external suppliers. I enjoy building relationships with team members and suppliers outside of Leidos as most people I’ve worked with have a really good sense of humour which makes work really enjoyable. 

What I love about my job is the work life balance it offers. This includes being able to work your hours at a time that suits you and being able to leave for the day without expectations of unpaid overtime. As long as you do your hours for the day and are at work for key meetings, the time you come in and leave is pretty flexible. There is trust there from management and it makes work a lot more enjoyable. I also go to work enjoying the idea that what I am doing has a positive impact on people and Australia as a whole, rather than just being about the bottom line. 

The coolest thing about my job is the constant flow of new challenges. Each day brings a new task, so no two days are the same. One day might be focusing on a critical script that needs to be deployed to restore functionality, while another might be developing an entirely new system. This keeps me engaged, continuously learning and growing each day. 

7am – I start my day by waking up to my alarm. I try to aim for 7am but often I end up sleeping in another 15 minutes. I then open my blinds and start to get ready. When getting dressed I like to make sure I’m not in all black, as I like to bring a little style and colour into the office. 

I have breakfast, often with my housemate who is also getting ready for their day. After this I pack my bag and sort out my lunch, which is often a pre-made meal from the supermarket. Unfortunately, I am not one for making extravagant lunches.

8am – I leave to catch the train into the city, which takes me around 40 minutes. Part of this is a 10 minute walk to the station, which is great to give me a little bit of exercise in the morning. On the train I usually listen to some music or read my Kindle to relax a bit before work. 

9am - I get into the office around this time but it can vary, sometimes I start earlier so I can finish up sooner. I walk in and say hi to my friends before getting to my team area and finding a desk. My work is pretty flexible so there is always a range of people working from home as well as in the office. 

I set up for the day and get started on what I was working on yesterday afternoon. Although a lot of my work is based in Java I tend to work in many areas of the project, which allows me to code in a variety of languages.

9:30am – By this time I have refreshed myself on the work I did yesterday and looked at what still needs to be done to finish the ticket. This includes tasks like writing tests and checking the acceptance criteria for anything that I’ve missed. I often write myself notes before I clock off so that I know what to focus on the next day and it’s these notes that I look over before diving into my work for the day. 

My team is made up of a Scrum Master and eight Software Engineers, two of us are part of this year’s intern/graduate intake. A lot of the team have been graduates in the past, which means that there is always a friendly face who is happy to teach me about software I am unfamiliar with. 

10:30am – I attend stand-up where the team and I share what we have been working on and what we are planning to do for the rest of the day. This keeps us accountable and makes sure that if anyone is encountering a problem, someone else in the team with relevant experience can offer their advice and help either by peer programming or brainstorming solutions. 

I update my team on my ticket progress, including when I am likely to finish it. We then discuss some work that I will pick up once I am done, such as reviewing another teammate’s work. This is important to prevent any mistakes that a developer might have missed.

12pm – At this point I might have come across what I think is a bug in the code. When I find something like this, I must confirm a couple of things, like if it is an unwanted behaviour, if I introduced it with my changes or it’s an existing problem. Determining the root cause of a bug can sometimes be tricky in a project with a large codebase like this because there are so many different places that an unwanted behaviour can be introduced.

If I encounter this, I usually ask one of my teammates to help me sort out the bug and we end up spending a fair bit of time analysing and solving. This is one of my favourite parts of my job - working with others and peer programming. I find that it’s the way I learn the fastest and I enjoy a good chat with my teammates.

By this point the bug has usually been fixed and I start to get hungry, which means it’s lunch time. I meet up with some other graduate and interns for lunch. Most days we all bring lunch from home, but I sometimes get something takeaway from some nearby shops. 

3:30pm – I continue working on my ticket. I put on my headphones and listen to some music or a podcast while I’m working to help me focus. 

At the end of each sprint we show the client some features we completed as well as conducting a sprint retrospective. This is where we reflect on how the sprint went and look at what we could have done better. This helps us to continually improve and ensure we are meeting client expectations. A sprint is a short, time-boxed period when a scrum team works to complete a set amount of work and made ready for review.

5pm – I finish my workday. Often my partner will also be working in the city where we meet up to run some errands and catch a bite to eat for dinner. I’ll catch the train home and get there around 8pm to allow myself to relax before bed, usually watching a tv show or playing a video game. I’ll head to bed around 10:30pm so I can get some rest before I do this all over again tomorrow.

7am – I start my day by waking up to my alarm. I try to aim for 7am but often I end up sleeping in another 15 minutes. I then open my blinds and start to get ready. When getting dressed I like to make sure I’m not in all black, as I like to bring a little style and colour into the office. 

I have breakfast, often with my housemate who is also getting ready for their day. After this I pack my bag and sort out my lunch, which is often a pre-made meal from the supermarket. Unfortunately, I am not one for making extravagant lunches.

8am – I leave to catch the train into the city, which takes me around 40 minutes. Part of this is a 10 minute walk to the station, which is great to give me a little bit of exercise in the morning. On the train I usually listen to some music or read my Kindle to relax a bit before work. 

9am - I get into the office around this time but it can vary, sometimes I start earlier so I can finish up sooner. I walk in and say hi to my friends before getting to my team area and finding a desk. My work is pretty flexible so there is always a range of people working from home as well as in the office. 

I set up for the day and get started on what I was working on yesterday afternoon. Although a lot of my work is based in Java I tend to work in many areas of the project, which allows me to code in a variety of languages.

9:30am – By this time I have refreshed myself on the work I did yesterday and looked at what still needs to be done to finish the ticket. This includes tasks like writing tests and checking the acceptance criteria for anything that I’ve missed. I often write myself notes before I clock off so that I know what to focus on the next day and it’s these notes that I look over before diving into my work for the day. 

My team is made up of a Scrum Master and eight Software Engineers, two of us are part of this year’s intern/graduate intake. A lot of the team have been graduates in the past, which means that there is always a friendly face who is happy to teach me about software I am unfamiliar with. 

10:30am – I attend stand-up where the team and I share what we have been working on and what we are planning to do for the rest of the day. This keeps us accountable and makes sure that if anyone is encountering a problem, someone else in the team with relevant experience can offer their advice and help either by peer programming or brainstorming solutions. 

I update my team on my ticket progress, including when I am likely to finish it. We then discuss some work that I will pick up once I am done, such as reviewing another teammate’s work. This is important to prevent any mistakes that a developer might have missed.

12pm – At this point I might have come across what I think is a bug in the code. When I find something like this, I must confirm a couple of things, like if it is an unwanted behaviour, if I introduced it with my changes or it’s an existing problem. Determining the root cause of a bug can sometimes be tricky in a project with a large codebase like this because there are so many different places that an unwanted behaviour can be introduced.

If I encounter this, I usually ask one of my teammates to help me sort out the bug and we end up spending a fair bit of time analysing and solving. This is one of my favourite parts of my job - working with others and peer programming. I find that it’s the way I learn the fastest and I enjoy a good chat with my teammates.

By this point the bug has usually been fixed and I start to get hungry, which means it’s lunch time. I meet up with some other graduate and interns for lunch. Most days we all bring lunch from home, but I sometimes get something takeaway from some nearby shops. 

3:30pm – I continue working on my ticket. I put on my headphones and listen to some music or a podcast while I’m working to help me focus. 

At the end of each sprint we show the client some features we completed as well as conducting a sprint retrospective. This is where we reflect on how the sprint went and look at what we could have done better. This helps us to continually improve and ensure we are meeting client expectations. A sprint is a short, time-boxed period when a scrum team works to complete a set amount of work and made ready for review.

5pm – I finish my workday. Often my partner will also be working in the city where we meet up to run some errands and catch a bite to eat for dinner. I’ll catch the train home and get there around 8pm to allow myself to relax before bed, usually watching a tv show or playing a video game. I’ll head to bed around 10:30pm so I can get some rest before I do this all over again tomorrow.