Far too many employers tag every software coder and tester in the business with the title of Software Engineer. There's much more to software engineering than coding. We generally don't put up with titling everyone drafting a blueprint as a Civil Engineer or Structural Engineer, for good reasons. Drafting skills, while darn useful, are not the primary thing I'd be looking for in someone to design and supervise the construction of a dam or a major power line.
As software moves from an interesting peripheral to projects to becoming a major component, good engineering becomes more important. We could tolerate bad software in an automobile entertainment system. Any software glitches in an engine control system are undesirable and could put the driver in a bad situation. With autonomous vehicles like the Google self-driving car, software bugs have the potential to be very dangerous to the occupants and others around them. Good engineering skills, from requirements specifications, through detailed design, proper error handling and safe failure mode specifications, into solid coding and detailed test and test coverage analysis become very important.