So there are 2 components to your question.
1) How do I figure out what kind of job I want to do later?
2) What skillset should I acquire to do that job later?
Thanks for listing out what your current experience with programming languages has been so far.
Alrighty. Regardless of what you will end up doing, you NEED to know C. C++ is a close 2nd.
A plethora of languages are based off or around C, not to mention you will need it at some point regardless of what you do.
1 or 2 scripting languages like Python are also going to be incredibly useful.
Now, from there on out it's going to be extremely important that you know what general kind of job you want to do.
Don't set out to do a job because there are a multitude of jobs in a specific industry.
That being said, Haskell, PHP, Ruby, and Perl are generally fantastic for just about any back-end stuff you will encounter. Personally not a big fan of PHP, but it's widely used, so it's good to at least be familiar with it.
Java and JScript are commonly (mis-) used for a lot of UI and front-end stuff. Not a fan. Websites are bogged down terribly.
Still, widely implemented (by idiots), so important to be familiar with their quirks (if only to know how to cut down on how much of it is being used).
I recommend reading something general like the Sedgewick book on Algorithms to gain a good understanding of all important fundamental aspects of programming, before specializing. There's a reason why it's been used for several decades to teach CS courses around the world.
If you can, see if any companies you would be willing to work for have a place where they have job-listings. Compare what job listings you are able to find for one kind of job over another.
Also see if you can get a meeting set up with someone from an HR department. I don't know how much of their work is covered by NDA's, but you might be able to get some good advice from them on the average "lifespan" of a certain position that they have observed during their career in the industry. That might be life-saving information.
For example, typical video-game devs only last 5 years before "burning out".
Find a relevant statistic might help you gain a better understanding of what to do.
The best way to figure out, however, if a particular job is for you, is to work on projects.
Vary what roles you have in a team.
Gain some experience in working with others.
See what parts of a project are the most fun to code.
At the end of the day, it's a general understanding of coding principles and the ability to work well as part of a team that's going to help you get a job and be happy, and not how many programming languages you know.
Someone close to me spent almost 2 decades working for Microsoft, and he told me how important it is to have an adaptable and permeable skill-set when working at a company like that.
My best advice is to get to know 2 or 3 languages REALLY well, as the skills and knowledge will translate pretty well between any relevant language.