Skip to main content
PProfileMatch

457 open Software Engineer jobs

Real, currently-open Software Engineer roles synced directly from company career pages. Upload your resume to see which of these match your skills, or browse all open roles. New to the role? Read our Software Engineer guide.

Hiring snapshot for Software Engineer

The most common locations right now are Mountain View, California (HQ) (27), Remote - USA (20), New York, NY (19). 106 of these 457 roles (23%) list a remote option. 306 were posted in the last two weeks. By team, the biggest groups are Engineering (457).

Computed from the 457 open listings shown below.

Guide: working as a Software Engineer

Software engineers design, write, test and maintain code that solves a product or business problem, often moving between layers of a system as needs shift. Much of the job is reading existing code, breaking vague requirements into small changes, reviewing teammates' pull requests and keeping quality steady as the codebase grows.

Core skills employers look for

  • Data structures and algorithms
  • One language in real depth
  • Git branching and code review
  • Unit and integration testing
  • Debugging unfamiliar codebases
  • Modular, object-oriented design
  • Basic SQL and data modelling
  • Writing clear technical notes

How to stand out when you apply

  • List two or three projects with a one-line problem statement, the stack you chose and why, and a repository link with a readable README and passing tests.
  • Contribute a small fix to an open-source project you actually use; a merged pull request shows you can navigate someone else's code and respond to review.
  • Replace duty lists on your resume with outcomes: what you changed, which constraint you worked within, and how you verified it, such as a test suite or benchmark.
  • Practise explaining trade-offs aloud, for example why you picked a hash map over a sorted list, since generalist interviews reward reasoning more than memorised answers.

What the interviews usually cover

Expect timed coding problems on arrays, strings, trees and graphs, a walkthrough of a past project, and behavioural questions about teamwork and owning mistakes. More experienced candidates usually get a design round where they sketch components, data flow and failure handling. Interviewers watch how you clarify requirements and test your own code before calling it done.

Prepare for free on ProfileMatch

Browse jobs by role

Browse jobs by company