$110k - $140k
CarolinaSecurity Clearance: No ClearanceBusiness Unit: Piper CompaniesPosition Owner: Jackie AllenPiper Companies is seeking a Software Engineer (IaC) to support a world leading technology organization in the Raleigh-Dur…
Engineering & IT · Raleigh, NC
Software Engineer jobs in Raleigh, NC
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it grows.
344
Open roles today
$36–$95/hr
Typical pay range
$126k
Median, full-time
11
Fresh in this list
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
01
Open software engineer roles
12 shown of 344 · sorted by freshness
$175k - $225k
CarolinaSecurity Clearance: TS/SCIBusiness Unit: Zachary PiperPosition Owner: Jackie AllenZachary Piper Solutions is seeking a Sr. Software Engineer (IaC)- TS/SCI for a world leading technology organization in the Raleig…
$174k - $252k
approaches to leverage offloads efficiently with Google hardware and software so you can build and test software in C++ for use on Google's... ...Science or a related technical field.Google's software engineers develop t…
$100k - $140k
CarolinaSecurity Clearance: No ClearanceBusiness Unit: Piper CompaniesPosition Owner: Anne GreenPiper Companies is seeking a Senior Vision Software Engineer to join a biotechnology organization developing advanced comput…
business requirements, in line with guidance provided Facilitate software application design discussions, and document design decisions... ...• High level of competency in software design and software engineering impleme…
$115k - $135k
CarolinaSecurity Clearance: No ClearanceBusiness Unit: Piper CompaniesPosition Owner: Jackie AllenPiper Companies is seeking a Sr. Software Engineer (Node.js) to support a growing technology organization in the Raleigh D…
$105k - $120k
CarolinaSecurity Clearance: No ClearanceBusiness Unit: Piper CompaniesPosition Owner: Jackie AllenPiper Companies is seeking a Cloud Security Engineer to support a leading organization in the technology industry in the R…
$130k - $150k
Clearance: No ClearanceBusiness Unit: Piper CompaniesPosition Owner: Jacqueline NorsworthyPiper Companies is seeking a Cloud Security Engineer to join a leading technology-focused organization in the Research Triangle Pa…
$125k - $150k
Clearance: No ClearanceBusiness Unit: Piper CompaniesDivision: EnterprisePosition Owner: Jackie AllenPiper Companies is seeking an Azure Engineer for a world leading technology organization in the Raleigh Durham, North C…
$115k - $140k
CarolinaSecurity Clearance: No ClearanceBusiness Unit: Piper CompaniesPosition Owner: Jackie AllenPiper Companies is seeking an Azure DevOps Engineer for a leading enterprise organization in the Raleigh, North Carolina a…
9Reference26-20362Salary$75.48 / hourRemote50% Remote Job Description Project Overview We are seeking a highly specialized Software Engineer for a long-term contract engagement focusing on the modernization of the CLIENT…
Televic Rail is seeking an innovative and hands-on Software Development Engineer to help build the next generation of onboard communication, passenger information, and mission-critical transportation technologies. This r…
02
What software engineers earn in Raleigh
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $36–$50 | $74k–$104k |
| Mid level | $50–$71 | $104k–$148k |
| Senior | $69–$95 | $144k–$198k |
Adjusted for the Raleigh market from national ranges.
03
What employers ask for
The skills these listings keep naming
Data structures and algorithmsSystem designGit and code reviewTesting and debuggingSQL and databasesAPIs and integrationCloud fundamentals (AWS/GCP/Azure)Clear written communicationCross-team collaboration
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through a project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
05
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
01
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
02
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
03
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
04
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
05
Keep the tech list honest; anything on the resume is fair game in the interview.
06
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
06
Where this role goes
Typical progression
01
Junior Software Engineer
02
Software Engineer
03
Senior Software Engineer
04
Staff Engineer
05
Principal Engineer
Ten quiet minutes a day
Applying for software engineer jobs in Raleigh?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.