The two titles are often used interchangeably, and in many teams the day-to-day work is the same. Where a distinction exists, it is usually about scope.
A developer is typically focused on building features — turning requirements into working code. An engineer is typically expected to also think about the system: architecture, reliability, scaling, and how the pieces fit together over time.
For hiring and career growth, the title matters less than the responsibilities. Ask what the role owns: a feature, a service, or the health of the whole product.