Introduction At IBM Software, we transform client challenges into solutions. Building the world’s leading AI-powered, cloud-native products... ...at the magnitude of your impact. About the Role As a Software Engineer on…
Software Engineer jobs in San Jose, CA
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 2,192 · sorted by freshness
Senior Full-Stack Software EngineerBackend-Focused | Java & SaaS | Full-Time | Remote (United States)Compensation: $120,000-$150,000 annually... ...integrations.We're seeking a senior, backend-focused software engineer w…
help us shape the future of data security and work towards a safer digital future. Job Description We are looking for a Software Engineer – Infrastructure & Platform Engineering to help build, maintain, and improve the i…
world! Our outstanding people deliver creative decarbonization energy solutions to our customers. We are seeking a Senior Software Engineer to join Electric Hydrogen's Digital Team, where you will develop mission-critica…
Our team is on a mission to build innovative infrastructure and tools to help other engineers be more productive and make software easier to create build and distribute. We believe that streamlining software engineering…
generate real-time observability dashboards across billions of tokens and complex data types.n We are looking for a Full-Stack Software Engineer to own the user-facing UI of our evaluation platform. Teams across Siri and…
For the engineer that obsesses on how software can enable OS developers to evaluate and improve their features there is no better place than Apples Experimentation team. The Experimentation team builds an end-to-end plat…
complex real-world problems for businesses and unlock significant value. We are a dynamic and collaborative team of researchers and engineers who thrive on pushing the boundaries of what's possible, dedicated to deliveri…
Summary: This job delivers complete solutions spanning all phases of the Software Development Lifecycle (SDLC). It involves advising management on project-level issues guiding junior engineers operating with little super…
accessible over time. That’s where we come in. We combine deep engineering expertise with global-scale manufacturing to deliver the... ...Rochester, Minnesota San Jose, California System Tools Software Engineering : Buil…
It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy... ...work for people. Job Description Job Summary The Software Engineer designs, builds,…
Category: Coding, SWE & Agent Evaluation · Pay: $130 / hr · Location: Remote — US-eligible · Contractor Software Engineer, Platform Engineering is a remote engineering review track for evaluating production code, debuggi…
What software engineers earn in San Jose
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $50–$70 | $103k–$145k |
| Mid level | $70–$100 | $145k–$207k |
| Senior | $96–$133 | $200k–$276k |
Adjusted for the San Jose 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 San Jose?
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.