Software engineers write code, but a lot of the job is deciding what not to build and fixing what broke. Titles change from company to company. What stays the same is how the scope of your work grows.
You pick up small, well-defined tickets and ask a lot of questions. That's expected. The goal is to ship without someone quietly rewriting your pull request.
You own features from design to release. You review other people's code, take your turn on call, and start having opinions about how things should be built.
You own a system, not a feature. People come to you when something is slow or broken, and you spend more time in design reviews than you'd guess.
Here the ladder forks. Staff engineers set technical direction across several teams. Engineering managers hire, coach and run one. At good companies, neither counts as a promotion over the other.
It isn't the languages. A senior engineer and a junior one may write in the same stack every day. What changes is how vague the problem is when it reaches you. Juniors get a ticket. Seniors get a complaint, something like checkout feels slow on phones, and have to turn it into tickets other people can pick up.
Match the stack in the posting where you honestly can. Screeners look for the exact names.
9% of openings are fully remote.
$134,400 – $197,300
Typical range in the 36 of the newest 60 postings that list pay.
It helps with the first job, especially at larger companies that hire from campus. Bootcamp grads and self-taught engineers get hired too. They usually need a portfolio of real, working projects to get past the screen.
Mostly, yes. Companies use both titles for the same work. Engineer tends to show up more at tech companies, developer more at agencies and in-house IT teams.
It depends more on the scope you've owned than on time served. Someone who ran a system end to end at a small company can get there sooner than someone who's closed tickets for years at a big one.