Unless you are in Sales, Marketing, or Senior Management, there's very little you can ever do to significantly impact revenue.
Not that Senior Management wants you to think that; it's demoralizing when combined with bonuses being withheld due to missed revenue goals.
Areas where I think good engineering can help include, designing software that minimizes its support costs, attention to code quality to improve customer/users experience, improving up-time, shortening maintenance windows, metrics and telemetry that help marketing and product development understand how a product is being used.
Good product documentation (reference manuals, in-product help, etc) is difficult and often over-looked. This isn't coding but engineering input into documentation is important.
Engineers can also provide significant input into product features and directions.
But the product by itself does not produce revenue. Only selling the product makes revenue.
So, at best, we can avoid costing the company money, but we can't make money. Even customer service can have a bigger impact on the bottom line than we do.
To draw a startup analogy, if you decide you want to take 25% of an established $100m market that's unlikely to happen because that's really hard to do, so people don't value your startup as having a potential $25m revenue. But if you can think of a realistic way to grow that $100m market to being a $125m market then people will readily accept you potentially have a $25m revenue business. Same result, very different impact.
Within your company you need to grow the market for your skills.