owns and operates platform shared capabilities across Justworks engineering, so product teams can build on reliable, well-run foundations... ...but no simpler." Qualifications ~5+ years of professional software engineeri…
Software Engineer jobs in Las Vegas, NV
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 238 · sorted by freshness
clusters in minutes. The Cloud Payments team is part of Cloud Core Engineering, which builds the systems behind Atlas and our other cloud... ...rare What We Look For ~5+ years of professional backend software engineering…
with a great culture with competitive benefits and compensation with a business casual atmosphere. We are currently seeking a Software Engineer with specific Android experience. This is a full time salaried position. You…
digital categories. We’re looking for an experienced C++ Software Developer to join our Las Vegas team and work closely with a... ...identify root causes and implement solutions. Help shape software engineering practices…
Mission Summary: The Data Platform team is the vital link between our company's expansive data and the engineering teams that rely on it. We architect and operate the core services and infrastructure necessary to transfo…
Mission Summary: We are looking for a Senior Software Engineer to join our Actions Sustaining Team to diagnose, develop and deploy solutions to solve the immediate challenges facing our autonomous vehicle software. You w…
Mission Summary: We are seeking a Senior Software Engineer to join our HIL Infrastructure team to scale and automate our offboard testing workflows to be thorough, efficient, and reliable. As a Senior Software Engineer,…
Summary The Software Engineer in Test (SET) is a hands on quality engineering contributor responsible for building, maintaining, and executing automated solutions that ensure the reliability, stability, and usability of…
Role: Senior Software Engineer – Back End Hybrid Role, MUST BE BASED IN SAN DIEGO, CA About Tillster Tillster, headquartered in the USA, is the global leader in digital ordering and customer engagement solutions. For ove…
systems, or a related field, or equivalent practical experience. Minimum two years of experience in test automation or software quality engineering. Proficiency in JavaScript and at least one additional language such as…
Android platforms. Develops, designs and programs various software applications, services and integrations for application performance... ...preferred. ~ Proven ability to lead and mentor junior engineers in design, deve…
– Speechify has no office. These include frontend and backend engineers, AI research scientists, and others from Amazon, Microsoft, and... ...the QA team An Ideal Candidate Should Have ~5+ years of software engineering e…
What software engineers earn in Las Vegas
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $36–$50 | $75k–$105k |
| Mid level | $50–$72 | $105k–$150k |
| Senior | $70–$96 | $145k–$200k |
National ranges — pay in Las Vegas typically tracks these.
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 Las Vegas?
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.