At Leidos, we make the world safer, healthier and more efficient through information technology, engineering and science. It’s work that matters, and a mission we are passionate about.

We are a large scale prime systems integrator. We go beyond the platform by creating solutions that turn complex, mission-critical data in to practical, usable solutions for our customers. Our key asset is the quality of our people – 1,400 in Australia from different backgrounds and with a wide range of skills and experience, working together to deliver innovative answers for our customers’ most complex challenges.

In practical terms, we are Australia’s largest commercial supplier of intelligence services to the Australian Intelligence Community. We also maintain legislative websites for governments, provide critical systems integration projects to the Department of Defence and support the IT environment for the Australian Taxation Office.

Industry Videos

Go behind the scenes with our industry career videos to find out more about some of Australia's most popular jobs.

Find Meaningful Work
Find Meaningful Work
Show More


38,000 Employees
30 Countries
1969 Founded

Why Join Leidos?

You can make a real difference

As an evolving organisation, our people are able to make a real difference not just to the work we do, but to our working environment too. We welcome new ideas and encourage our people to challenge the norm.

We also listen to what our people say. So, we run an annual Employee Engagement survey called Leidoscope. This tells us what is working well and where we can do better. And it helps us with our business planning for the next year.

We are developing a supportive and rewarding culture

We want everyone to be able to be the best they can be and recognised for their contribution. So, every day, we are developing a culture where collaboration, transparency and flexibility are embedded, our people are recognised and opportunities for their personal development are clearly laid out.

Last year alone, ‘Young Professionals’, ‘Defence & Emergency Services’ and ‘Women’s’ Advocacy Groups were established. These are voluntary groups of like-minded Leidos employees who have a common interest, meet regularly and hold open events that anyone in the company can join.

We celebrate our differences

We are proud of and celebrate our diversity – we are all unique – and work hard to help everyone feel accepted as part of the team.

During the year, we participate in events such as International Women’s Day, RUOK Day and Taste of Harmony. And, last year, we were recognised as one of the Best Places to Work for LGBTQ Equality.

We also give back

Last year, Leidos was recognised as one of the World’s most Ethical Companies. So, delivering practical solutions to complex challenges doesn’t just apply to the work we do for our customers. Not only are our people involved in many charitable causes and communityrelated initiatives but, as a business, we also have ongoing relationships with the Australian War Memorial and Bravery Trust, which provides urgent financial support to veterans, current and former members of the Australian Defence Force and their families.

We’re big but small

As a company, we are rare. Whilst we are part of a 32,000 person US-based organisation with a 50 year history, here in Australia we are still a relatively new name. Our business is growing fast and we are building an enviable reputation for innovation and delivery.

Where you could fit in

Whether you are looking to specialise in a technical area – such as Software or Systems Engineering – or in any of the functions that are essential for the smooth-running of our business – HR, Finance, Business Development, Operations or Corporate Affairs, for example, you could be part of our future.

Who are we looking for?

At Leidos, we love a challenge. So, if you are adaptable, eager to get involved and enjoy finding better, more efficient ways of doing things, we should talk.

Early Careers

Graduate Program

We run a one year graduate program, enabling graduates to work on real projects as an embedded and productive team member right from the start. They are surrounded by seriously smart, approachable people, so there’s plenty of scope to push boundaries, learn and grow.

All of our graduates are employed on a permanent basis and are provided support, on the job training, and networking opportunities along with an assigned mentor and buddy to help navigate around our organisation.

At the end of the year, they typically continue to work in the area they started in and further develop their strengths and capabilities. After that, they often progress into technical or managerial positions.

Industry based learning program

We also run a paid industry based learning program for 12 months. Ideal for students in their penultimate year at university, this offers the chance to apply what they have learnt into hands-on work experience by tackling real projects alongside more experienced team members.

What our Graduates Say


Graduate Software Engineer, studied Bachelor of Science (Computer Science) (Honours)

Leidos is a large company and therefore has a wide range of different projects and customers, each at a differing stage and involving differing technologies. This means there is always something new and interesting going on, which is exciting to be a part of and provides constant challenges due to the ever changing technologies that we get to use. One of my favourite things about being a software engineer is getting to design the software architecture and solving problems for the first time. I also enjoy learning new program languages and dealing with technologies that I have never used before. I know that this is the right job for me because I still want to write software in my free time, even after a tough work week.


Graduate Systems Engineer, studied Electrical and Electronic Engineering.

Leidos is a growing business where things can change quickly, even the basic processes have changed in such a short period of time. While navigating all these changes on top of learning the skills required for the job can be challenging, the learning experience is very rewarding. This shows that Leidos is dedicated to continually improving and being a leader in the field. It is an exciting place to work as there is always heaps of new things to learn, and many opportunities to explore.


Graduate Systems Engineer, studied Bachelor of Environments, Civil Engineering Systems and Master of Engineering

I am in a team that assists other users within defence with their ICT needs such as user account management, remote access, printer access, domain support and various other ICT related things. We also have to assess each ticket that comes through for quality checks to ensure they provide all the required information for easy actioning of the job. One of the things that I like most about my role is the interaction with the clients. This can be both challenging and rewarding just the same. Our interaction with the Department of Defence also gives me a sense of pride that our work is contributing towards our national security, no matter how small it may seem from our end.

Life at Leidos

Job satisfaction and business success thrive in a positive working environment. Every day, we are developing a culture where collaboration, transparency and flexibility are in-built, innovation thrives, individuals are recognized, development opportunities are clear, and new initiatives are being launched all the time.

Celebrating our differences

We want our people to feel valued for their unique qualities, ideas and perspectives. It ensures a sense of belonging and underpins our success as a business. Events such as International Women’s Day, RUOK Day and Taste of Harmony are all central to our calendar.

Sharing knowledge and experience

Our Advocacy Groups and Communities of Practice help ensure likeminded people, irrespective of where they work within the organisation, are able to collaborate and learn within their interest or professional groups.

Listening to our people

We work hard to make sure that everyone feels challenged to do their best work in an environment where they feel they belong. Our annual Employee Engagement survey, Leidoscope, provided rich insights into what our people feel is working well and where we can do better.

Recognising our achievements

Everyone likes to be thanked, so we have developed a range of tools from simple Kudos cards (thanks to a colleague for helping out) and monetary gift vouchers (recognition for a great job well done) through to our annual Leidos Australia Values Award (LAVA) events held simultaneously in Canberra and Melbourne.

Sharing progress

Regular team and company events are held throughout the year to keep everyone informed of our progress as a business. We also produce weekly company updates covering a range of business and social topics.

Giving back

We are involved in a number of community-related initiatives either as an official partner or by raising funds for causes our people believe passionately in.

Learn more about our community partners

A word about diversity & inclusion

At Leidos, inclusion is about creating an environment where everyone feels welcome, valued, respected and supported. Embracing diversity means understanding and recognising that each of us is unique, and that our differences are our greatest strength. These are much more than goals or campaigns. They are central to building a great place to work for each of the 34,000 employees at Leidos across the world. Because together, we are better.

Our global focus on Diversity & Inclusion

Meet Yanny

Yanny Li – Systems Engineer at Leidos

Yanny Li studied ​a double degree in Engineering and Commerce ​at Australian National University in 2018 and is now a Systems Engineer at Leidos.

5.00 AM

The alarm goes off. I have a shower, get dressed, make a cup of matcha latte and catch the train into a yoga studio.

6.30 AM

Free-breathing. I have a 2-hour Ashtanga Mysore yoga session. A daily dose of inner peace keeps me calm and clear-headed throughout the day.

8.30 AM

I try to walk 10,000 steps every day. If the weather is good, I would walk to work from the yoga studio (about 2 km).

9.00 AM

I arrive at work, get to my desk, log in and check the calendar for all meetings scheduled for the day. I get myself a cuppa before checking my emails, attending to any outstanding chat messages on Skype from last night and replying promptly to my colleagues.

9.30 AM

I started craving coffee and so are a few of my co-workers. We all head down to our go-to coffee spot. These coffee runs are a great chance to catch up with my colleagues and get to know them better.

10.00 AM

Time for our regular Stand-up meeting. My work is project-oriented and using the agile methodology. These stand-up meetings keep everyone aware of the project’s landscape and progress. If there are certain tasks or issues we need to focus on, this is the time to discuss and to make any adjustments needed.

As a Systems Engineer, my role is to support the execution of Systems Engineering activities on a large-scale system of a systems integration project. This involves breaking down customer supplied requirements into lower-level service specifications, working design aspects and managing the compliance tracking and evidence gathering back up the lifecycle.

10.30 AM

I go back to my desk and continue working through the task I started earlier today. I read through emails and feedback from the detailed requirements I submitted for review. Collate all of the feedback and comments, I make changes to my work. The changes don’t take too long to make. Once I am done, I would chat with the senior engineers to make any further amendments or arrange new tasks.

12.30 PM

It’s lunchtime. I alternate between a social lunch or a lunch packed the night before. I go for a walk around Collins Square and pick up some snacks from Woolworths. The snacks go to our team’s snack drawer and keep everyone in the team energised throughout the day.

1.30 PM

Back at my desk and continue working through the requirements specification process. The detailed requirements describe the necessary functions and features of the project solution and lay a strong foundation for project success. I write down any questions in my head and walk over to my manager’s desk to discuss them.

3.00 PM

I take a small tea break whilst chatting to colleagues in the kitchen area.

5.00 PM

Time to catch a train home. I use the commute time to check my social media messages and catch up with my friends.

6.00 PM

I get home, pack my lunch, pick out my clothes for tomorrow and change to my gym outfits.

7.00 PM

The gym is less busy now. It’s time to sweat it out and stay on track with my health and fitness goals.

10.30 PM

Time for bed. I try to go to bed by 10:30 PM so I can start the next day nice and fresh.

Meet Richard

Richard Barsha – Software Engineer at Leidos

Richard Barsha studied ​a Bachelor’s Degree in Computer Software Engineering ​at RMIT University in 2018 and is now a Software Engineer at Leidos

5.30 AM

Snooze and ummmm… snooze again… So here is the thing, I’m just not a morning person. When my alarm starts blaring I will typically indulge my lazy side and snooze it. Once I manage to crawl out of bed, drinking a glass of water helps get the blood flowing (my substitute for the caffeine loaded beverage my partner obsesses over). Lights on, I cover the eyes until they adjust and move onto brushing my teeth, getting dressed and packing my lunch.

6.20 AM

Early bird benefits. By this time, I’m in the car and driving to the train station. Having tried both routines, I can definitely vouch for the idea of being an early bird. Missing the 9.00 AM peak means plenty of parking at the train station, cheaper myki fares and a guaranteed seat on the train. Lately, audiobooks are my jam in the morning, so the earphones go in and I do my best to stay tuned into the book while I fight my forever wandering mind. In case you were wondering, I’m currently listening to “The 7 Habits of Highly Effective People” by Stephen R. Covey.

7.20 AM

Settling in. Just arrived at my desk, greeted the team and signed into my computer. After a quick catch up with the team, it’s time to check my priorities for the day. The development team is made up of approximately 4 seniors, 2 technical leads, a recent graduate and an intern. We are building a data management platform which will be used to store and serve data to millions of Australians – robustness and scalability are imperative. I’ll spend 5 minutes going through my emails, replying to anything urgent. Up next is checking Jira for workflow changes, if I have made a pull request it’s (hopefully) been reviewed and pushed back to me for amendments. I tend to prioritise addressing feedback on a pull request to maintain momentum – a lingering pull request is a bad news. After all, comments have been addressed, I push my code and move onto the next ticket – this should keep me busy for a while.

11.30 AM

Stand up. You may be thinking it’s a bit late for a stand-up, well… kind of but not really. Running standups at this time has two benefits, firstly it gives the team flexibility to start when it suits them, secondly, it means people talk faster as it’s strategically close to lunch – works surprisingly well. Sometimes we will walk the board sometimes we will do a round-robin (yesterday, today, blockers), I personally prefer the round-robin but change is always welcome.

12.00 PM

Lunchtime. I love food, so naturally, I love lunchtime. Resisting the temptation to buy lunch in the city is a tough one but eating dumplings every day gets expensive and the housing market isn’t playing nice these days… oh and I guess it’s not very healthy.

12.30 PM

Busy work. Trying to deep-dive technical challenges straight after lunch is usually a struggle. Using this time to reply to emails and take care of any other “busy work” helps ease into productivity.

1.30 PM

A collaborative effort. Recently we had a new intern join the team, as part of onboarding we do some pair programming – I found pair programming invaluable when I started my graduate program and it’s something we do often. It gives them a chance to follow along and solidify their technical understanding, asking any questions along the way. Similarly, it forces me to consciously explain my approach in a manner which makes logical sense, an excellent way to weed out pesky knowledge gaps.

3.30 PM

Winding down or ramping up? As the day matures, instead of winding down I try and ramp-up to finalise any deliverables before I head off. The sprint review is tomorrow which means its all hands on deck to get the work we committed to during sprint planning over the line. After checking Jira, there are a couple of tickets requiring review so I grab one and jump into it.

4.30 PM

That’s a wrap. Times up, I pack my bag, say my goodbyes and jump on a train. The days can be cognitively demanding so I skip listening to an audiobook, instead, I play some chilled music and reflect on the day during my commute home.

6.00 PM

Home sweet home. I walk in the door, greet my partner and give the cat a scratch. I do my best to be useful while we prepare dinner, she is much more skilled than I. We have dinner, I do the dishes and try to mentally prepare for a trip to the gym.

7.30 PM

It could go either way. Depending on how strong my will power is that day, I may or may not be at the gym. I try to make it there around 4 times a week, exercise is a key ingredient to a healthy work-life balance.

8.30 PM

Lights out. After getting home I jump straight in the shower and prepare for bed.

The day is done.

Meet Jacqueline

Jacqueline – Software engineer associate at Leidos

Jacqueline studied ​a Bachelor of Information Technology (I.T. security) at Deakin University in 2015 and is now a software engineer associate at Leidos.

6.00 AM

I’m awake…just. Don’t bother talking to me; I won’t give you a coherent response. I eat breakfast and drink tea. Tea is good. I spend too long savouring my tea and rush through brushing my teeth and getting dressed to get out of the house on time.

7.00 AM

I drive to the station. As it’s so early, I can usually find parking pretty easily. I get on my train which is 3 mins late, find the last seat in the carriage, grab my phone and earbuds out of my bag and settle in for the journey to work with some head-banging tunes to get me pumped for the day. I’m looking forward to the day ahead.

8.00 AM

My train is now ten minutes late. I choose to take the stairs rather than the escalators to get out of the station because I like to pretend I’m fit. It’s a brisk walk from the station to the office.

8.10 AM

I walk into my office suite and greet the two guys on my team who beat me in. We like to make use of Leidos’ flexible hours and have more home time in the afternoon. The rest of the floor is very quiet as most people don’t get in until a bit later. I unpack my stuff and log into my computers. I check my email and see the weekly update from the chief executive with updates on the organisation as a whole. This is a good way to find out what’s happening in different parts of the business.

.30 AM

My team is currently working on a research and development project and we use scrum software development methodology. Today’s the last day of our two week sprint and I need to finish off the story that I’ve been working on before 11 o’clock so I can get the new functionality into the release.

9.30 AM

I’m happy that my code has built successfully, my unit tests have passed, I have a running instance of my new feature in our Dev environment and I’ve documented how to use the new feature. I need to get my story and code reviewed before I can mark it as ‘Done’. I ask one of my team members to review it for me. I give him a demo of the new feature and explain how it works. He reads through my code and picks up on a couple of things that I could have done better. I go back and fix the minor issues, then he re-reviews my code and approves it. My changes then get merged and my story is marked as ‘Done’.

10.30 AM

The Leidos office in Melbourne holds a morning tea every fortnight, and today’s the day. I get to the kitchen just as the food arrives so I can be sure I won’t miss out on a mini chicken curry pie.

11.00 AM

It’s sprint review time! This meeting only happens at the end of the sprint. We each talk through our moods during the sprint, what we think went well, what we think could be improved next sprint and people we’d like to thank.

11.30 AM

My team demos the stories that we’ve worked on over the sprint to each other. Some sprints, our client will come along to see the progress we’ve made, but this week it’s just an internal demo.

12.00 PM

Lunch time! Half of my team go out and buy food, the other half bring stuff from home. I’m in the ‘bring stuff from home’ category because I’m trying to save a deposit for a house. I head to the kitchen to toast my sandwich and then bring it back and eat it by the window while browsing the housing market on my phone and chatting to my colleagues.

12.30 PM

We merge the code in our Dev environment to our Prod environment and check that all tests are passed. We deploy to Prod and ensure that everything still works as expected. We fix any issues that come up.

1.00 PM

It’s sprint planning time. This always feels like the longest part of the sprint, so I make sure I’ve made myself a nice cup of tea to get me through it. My team gathers in a corner and we sit down and go through each new story in our backlog queue. We vote on the number of points we think each story is worth based on how difficult we think they will be to complete. The higher the points, the more difficult the story. If there’s a large discrepancy between our rankings, then the people who voted for the highest and lowest number explain why they thought it was difficult or easy respectively. After hearing their explanations, we then vote again until we reach an agreement. Once all of the stories have points, stories are added to our next sprint based on how many points we think we can achieve over the next two weeks.

3.30 PM

Sprint planning is finished and as I don’t have any story currently assigned to me, I can pick the next one from the top of the backlog queue to work on. It turns out that the next story is to configure and install a new software that I’ve never worked with before, so I spend a bit of time doing some background reading to try and figure out how it works before I start attempting to write configuration and installation scripts.

4.10 PM

Back to work. I think I’ve got enough of an idea to get started on my story, so I start writing some configuration and installation scripts.

4.45 PM

Home time! It was a good day. I pack up my stuff and log out of my computers. I leave the office and walk up to the station to catch a train home.

6.00 PM

I arrive home, eat dinner, walk my dog, have a shower, catch up on some TV and relax.

10.00 PM

Bedtime! I’ve achieved quite a bit today, so now it’s time for a well-earned rest.

Our Videos

Featured Video

All Videos

Bec had a chat with Lei Lei who has had many roles within Leidos
Bec caught up with Adam, software engineer with Leidos

There are currently no jobs available

Unfortunately there are currently no positions available at Leidos, please check back soon.