Most companies that are hiring are doing so because they have a specific problem or set of problems they're trying to solve.
You can usually get a decent idea of what these problems are based on the job posting, talking to people who work there, and even just reading the company's website to learn more about what the company does.
The good news is that many software development skills are portable across jobs and industries. Domain experience is definitely helpful, but lack of it won't always hinder you.
The best way to approach this is to find a way to describe your experience in a way describes how you'll be able to help solve the challenges that that company you're applying to is facing.
This will usually require at at least partially customizing a resume and cover letter for every role you're interested in. Being a generalist is fine, but you don't want to describe your skills in such a general way that someone who is reviewing your resume can't figure out if you're worth interviewing.
When I've had to review applicant resumes at previous jobs, I've seen quite a few that were 5-10+ pages long and listed everything the person had done in excruciating detail. This wasn't helpful. I'd much rather see a concise page or two that tells me why I should want to meet with the applicant.
When asked what kind of role or industry you're interested in, you could say that you're interested in tough but rewarding software engineering problems regardless of industry.
Personally, I think that diverse experience is a desirable trait when hiring a new developer. You'll find some companies and managers who feel differently, but don't worry about them. You're not going to be able to please everyone.