still operates without the automated feedback loops that modern software teams rely on. Without real-time observability, issues are... ...Partners and Andreessen Horowitz and with a rapidly growing team of engineers, sci…
Software Engineer jobs in Charlotte, 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.
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.
Open software engineer roles
12 shown of 783 · sorted by freshness
ethical use. Experience with Java, Spring Boot, and Angular is a plus. We require a bachelors degree in Computer Science, Software Engineering, Information Technology, or a related field, or equivalent practical experien…
Job Title: MES Software Engineer / Technical Lead Industry: Manufacturing Location: 100% Remote, East Coast or Central US time zone Shift: Monday through Friday, 8am to 5pm, no overtime anticipated, up to 25 percent trav…
About the Role Wells Fargo is seeking a seasoned Senior Software Engineer to design, develop, and deliver complex solutions within our big data, cloud, and distributed systems ecosystem. This role is critical in supporti…
business goals. Key responsibilities of the job include ensuring that software is developed to meet functional, non-functional and compliance... ...hosted In-Production platform. We are looking for a Software Engineer wi…
with structured tools/knowledge bases. Vertex AI & Platform Engineering Productionize services on Google Vertex AI (Models,... ...deliver business impact. Required Qualifications 7-10+ years software engineering experien…
require a bachelors degree in Computer Science, Information Technology, Information Systems, Engineering, or a closely related discipline. We need at least 7 years of software development experience with .NET, C#, and AS…
Term Contract Location: Charlotte, NC; Minneapolis, MN (Hybrid) Job ID: 178545 Job Overview: We are seeking a Specialty Software Engineer 4 - Contingent to consult on complex initiatives with broad impact and large-scale…
Job Description Job Description As a Senior Full Stack Engineer, you'll design and ship high-performance web applications across our React/Next.js frontend and Node.js/Express backend with real autonomy. You'll make arch…
and stored in a strategic [Chainlink Reserve]( Learn more at [chain.link]( About The Role The CCIP Protocol team is hiring a Software Engineer to design and maintain the services that coordinate fast, fault-tolerant cros…
contract-driven development Working knowledge of cloud-native engineering practices, including containers, Kubernetes, Helm, GitOps,... ...AI use Education ~ Bachelor’s degree in computer science, Software Engineering, I…
people around the globe work on Speechify in a 100% distributed setting – Speechify has no office. These include frontend and backend engineers, AI research scientists, and others from Amazon, Microsoft, and Google, lead…
What software engineers earn in Charlotte
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $36–$50 | $74k–$103k |
| Mid level | $50–$71 | $103k–$147k |
| Senior | $68–$94 | $142k–$196k |
Adjusted for the Charlotte market from national ranges.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
Applying for software engineer jobs in Charlotte?
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.