Leidos SWE Salary (Location & Pay Outlook)
There is no single verified Leidos software engineer salary: pay depends on the exact role, level, worksite, and offer terms. Start with the salary range in a current Leidos job posting, then compare it with the BLS national software developer median of $133,080 for May 2024. Treat that figure as context, not a promised Leidos salary or entry-level offer.
When comparing jobs, it is easy to focus on base pay and miss the value of health coverage and other benefits. Those can affect your budget and well-being, but the package depends on the role and offer. I recommend checking the written benefits details alongside salary, work location, and any clearance conditions before you decide whether a position fits.
Leidos Software Engineering Roles: Qualifications, Locations, and Pay-Range Context
A Leidos software engineering job can differ from another job with a similar title. The role, level, contract, worksite, and hiring requirements all matter. For a useful salary estimate, begin with the current posting for the exact position, and read the stated range and work arrangement in context.
The BLS reported a $133,080 median annual wage for software developers in May 2024. This is a national figure for an occupation, not a Leidos salary estimate. It includes workers across experience levels and employers, so it cannot tell you what a new graduate will earn in one city or at one company.
Leidos postings may list a pay range for a specific role and location. Check whether the range is current and whether it describes base pay. Do not assume that it includes a bonus, benefits, or other forms of compensation. If no range appears, you can ask the recruiter for the expected base-pay range before investing time in interviews.
| Pay information | What it can tell you | What it cannot tell you |
|---|---|---|
| Salary range in the exact Leidos posting | The employer’s stated range for that requisition | Your final offer or total compensation |
| BLS median of $133,080 | A national benchmark for software developers in May 2024 | A Leidos salary or entry-level wage |
| Salary estimate on a job or review site | A rough point of comparison | A verified offer for your level and worksite |
| Written offer | The proposed pay and terms for your role | Whether another role or location would pay more |
Location matters because employers may set pay ranges for different labor markets. A posting may also require work at a named site, offer hybrid work, or set other attendance rules. Remote work does not prove that pay is the same across the country, and moving to another city does not guarantee a salary change. Ask how location affects the range and where you are expected to work.
Key step: Save the posting and note its title, level, location, range, work arrangement, and application date. Use that record as your starting point, not a general online estimate.
Degree Preparation and Technical Requirements for Leidos SWE Positions
A degree can help you build the technical foundation for software work, but each Leidos requisition sets its own education and experience rules. Read those requirements closely. A bachelor’s degree in computer science, software engineering, computer engineering, or a related field is common in the field, yet some roles may accept equivalent skills or experience.
Before choosing a program, compare the courses with the work you want to do. Useful areas often include programming, software design, testing, algorithms, and systems development. The exact tools and languages vary by job, so use current postings to spot patterns rather than assuming that one technology is required across the company.
Check the education wording in each listing:
- Required degree: Treat this as a stated condition unless the posting also allows an equivalent route.
- Preferred degree or skills: These can strengthen an application, but they are not always mandatory.
- Experience requirement: Note the type and length of experience. A class project may show skill, but it may not count as professional work experience.
- Accreditation: Check a school’s institutional accreditation through the U.S. Department of Education or CHEA. ABET accreditation may be relevant for some computing or engineering programs, but it is not a universal Leidos hiring requirement.
A degree’s value depends in part on its cost and completion time. Compare net price after aid, likely debt, and the program’s completion rate with real entry-level jobs you can reasonably pursue. Do not use the BLS median as a promised starting salary when deciding whether a program is affordable.
Key step: Make a short list of current roles you could target after graduation. Use their requirements to check whether a program’s courses and cost support your plan.
Building a Competitive Profile: Projects, Experience, and Clearance Readiness
A competitive application shows that you can do the work named in the posting. Coursework is one source of evidence; internships, team projects, and prior jobs can add more. A security clearance is a formal eligibility process for some roles, not a general benefit of working at Leidos, so check whether the specific job requires one.
Build evidence in steps:
- Strengthen core skills. Practice writing and reviewing code, testing software, using version control, and explaining design choices. Match your preparation to the tools named in the role.
- Complete relevant projects. Choose work that lets you show your contribution. State what you built, which tools you used, how you tested it, and what changed because of your work.
- Seek experience. Apply for internships, co-op roles, research work, or junior positions that fit your current level. Keep a record of technical tasks and results.
- Tailor each application. Use the posting’s language honestly. Connect each required skill to a project, course, internship, or job on your résumé.
- Check eligibility early. Read any citizenship, clearance, or other eligibility language. Do not assume that every Leidos role has the same rules.
A clearance is authorization to access certain protected information. The posting may say that a clearance is required, that you must be able to obtain one, or that none is listed. These statements are not interchangeable. Ask the recruiter what applies to the role and whether the hiring process depends on clearance approval. Do not claim you hold a clearance if you do not.
Illustrative application scenarios
These examples are not Leidos offers or salary reports. They show how to use the requirements in a real job search.
- New graduate: You find a posting that accepts a bachelor’s degree and asks for software testing and programming skills. You compare those requirements with your coursework and project work, then apply if you can show relevant evidence.
- Career changer: You have experience in another field but limited software work. You check whether the posting accepts equivalent experience, then build a portfolio and target roles whose requirements match your background.
- Clearance-dependent applicant: You find a role that requires or may require clearance. Before relying on it as a career option, you ask about eligibility, timing, and whether the role has other conditions.
Key step: Apply when you meet the stated requirements or can clearly explain how your experience fits. Treat clearance and eligibility language as a screening item, not a detail to resolve after accepting an offer.
Career Pathways and Employment Outcomes: Compensation, Advancement, and Location
Your pay outlook depends on the role you qualify for, the local range, and your experience. A first job can lead to broader technical work or greater responsibility, but the path is not automatic. Compare current openings and offers at each step instead of assuming a fixed salary increase or promotion schedule.
Use this process to evaluate a role:
| Step | What to record | Why it matters |
|---|---|---|
| 1. Identify the requisition | Exact title, level, and posting date | Similar titles may describe different work |
| 2. Check the worksite | City, remote or hybrid terms, travel, and attendance | Location can shape pay and daily costs |
| 3. Review the range | Minimum, maximum, and whether it is base salary | A range is not a guaranteed offer |
| 4. Confirm requirements | Degree, experience, skills, clearance, and eligibility | These determine whether the role is realistic |
| 5. Compare the full offer | Base pay, bonus eligibility, health benefits, and other terms | Benefits and conditions affect the package |
| 6. Assess next steps | Skills gained, likely responsibilities, and role scope | Career value is more than starting pay |
When you receive an offer, ask for the base salary in writing. Confirm whether any bonus is guaranteed or only possible, what health benefits are available, when coverage begins, and whether the position is tied to a specific worksite or contract. Also clarify any clearance contingency and what happens if approval is delayed or not granted.
A higher salary is not always a better fit if the role’s location, schedule, or required travel does not work for you. On the other hand, do not discount a role solely because its first number is below a national median: the BLS figure covers a broad group of workers, not just new hires. Compare the offer with the posting range, your experience, local costs, and other opportunities.
I use a simple comparison when weighing options: list the pay and benefits, then list the requirements and career skills each role can build. This makes trade-offs visible without treating one salary figure as the whole decision.
Key step: Compare written offers on the same basis. Keep base pay separate from benefits and possible bonuses, and weigh the role’s location and next-step opportunities.
FAQ: Leidos Software Engineer Salary and Jobs
These short answers cover the questions most applicants ask when comparing Leidos software engineering roles. Because requirements and pay ranges can change by posting, use the current requisition and written offer as the authority for a specific job.
What is the average Leidos software engineer salary?
There is no single verified figure that applies to all Leidos software engineers. Use the current salary range in the exact posting, or ask the recruiter for the range if it is not listed.
What is the BLS salary benchmark for software developers?
The BLS reported a national median annual wage of $133,080 in May 2024. This is an occupation-wide benchmark, not a Leidos pay quote or an entry-level guarantee.
Does Leidos pay software engineers more in some locations?
Pay ranges may vary by role and labor market. Compare the range and work rules in each posting, and ask how the named worksite affects compensation.
Does remote work mean the salary is the same nationwide?
Not necessarily. A remote label does not confirm that pay is uniform across locations. Ask how the employer sets pay for the role and where you must reside or work.
What degree do I need for a Leidos software engineering job?
Requirements vary by requisition. A bachelor’s degree in computer science, software engineering, computer engineering, or a related field is common, but some postings may allow equivalent experience or skills.
Do all Leidos software engineering jobs require a security clearance?
No single rule applies to every role. Check the posting for clearance and eligibility terms, and ask the recruiter what the specific job requires.
Can a new graduate apply for Leidos software jobs?
Yes, if the posting’s degree, experience, and eligibility requirements fit your background. Look for roles whose level and stated requirements match your experience.
Does the salary range include benefits or bonuses?
Do not assume it does. Ask whether the listed range is base pay, then review bonus eligibility and health benefits separately in the offer materials.
Should I use the BLS median to decide whether a degree is worth the cost?
Not by itself. Compare program cost, likely debt, completion time, graduate outcomes, and realistic local jobs for your experience level. The national median is not a promised starting salary.
How should I compare two Leidos offers?
Compare base pay, benefits, bonus terms, location, work arrangement, clearance conditions, and job scope. Use written terms and consider which role builds skills for your next career step.
(This article was written by one of our staff writers, James Holloway. Visit our Meet the Team page.)
