I live in the NE, close enough to Philly to get some of the "big business" overflow.
I'm a "temporary" contractor (one of four still here 9 months in... out of about ten originally hired for 5-6 months). Right now I'm doing some weird Handlebars .NET template writing, alongside writing C# that builds a model of the data needed for each template. Because of my experience, ability to gain understanding of the system, ability to communicate, and rapport with the architect and other contractors, I've also taken on a sort of intermediary team lead role. Basically that means business folks come to me to grease the wheels and get the things moving that will make them happy, and the contractors (and full-time developers that have been here for years) come to me with questions about the architecture, why things work a certain way, how to troubleshoot a bug or get a certain feature working. I still crank out more completed feature requests than any other developer, but I spend more time typing up requirements and asking the business folks for clarification than I do solving tough coding problems. (Also in this role, I've written some C# action filters that make it easy to apply common behaviors to API endpoints, track down exceptions, and generate reports on API activity. I also wrote a C#/Mongo web app that accesses MongoDB records, lets you filter/search, and create some of the desired reports.)
I didn't get a clear picture of what you do now, what you're interested in, or what skills you hope to acquire, develop and master. Depending on role, you may need to be meticulous and wildly patient. You will likely need to learn how to read code, create complex models in your head, and think through how a compiler will interpret code, what state the moving parts are in, and how the code will change those states. You will almost certainly need to get good at reading people, interpreting what they say they want, and thinking ahead to what will make the software do what they really want, even if the user behavior varies wildly.
I've been on LinkedIn for a long time, and it has been a solid provider of connections to recruiters and job leads. Usually too solid. I'm going to have to admit that at this point, I'm a chiseled veteran (though not yet 40), so my experience does have value in the corporate/enterprise world. (It likely has a lot less value in the startup, social media, design and megaCorp world, especially say Silicon Valley.) As mentioned by many here, there is a very wide variety of work, and jobs can either be very focused (implement single classes of code to the exact requirements of your architect, with a given performance profile) to very broad (our insurance company is converting part of our user notification system to email and want you to write some app to help us get there). This isn't changing. What changes, always, is what's "hot" but also what's perhaps more relevant. When I started nearly 20 years ago, just building a web site was the big craze. Knowing HTML, JavaScript and a little server-side language (I went through ColdFusion, classic VB-based ASP, PHP and the whole evolution of VB .NET and C#...) made you massively employable. Then the initial wave of web page building (and DIY e-commerce) died down some, but from the ashes, some more serious software-based web-facing businesses arose, and many traditional businesses learned new ways to use software to automate and streamline ancient (you know, paper pushing from the 80s) processes. If you're going to be flexible and interested in learning (code and how to deal with the business side, as well as user needs), you'll always find work. (Now is a good time to learn big data/machine learning, but whether it interests you is all in your court.)
Oh, now do I have a degree? Oh no - I do not. I did start to study C.S., but I'm a full-fledged college dropout. But I started learning code when I was around 7, both in a special program at my elementary school, and with a second-hand discarded Commodore 64. I didn't keep learning code my entire childhood/teen years, but when I picked it back up in college, it seemed to come more naturally to me. I think the exposure at a young age helped. I was
very interested in making web pages for fun, especially as I learned JavaScript and server-side / database programming. I had a ton of fun in 2006 when I really started to dig into Ajax for the first time! I haven't done as much for fun lately, but I wrote
https://fi.retorch.com over the course of about 4 weeks last winter, and a few months earlier, I did all 50 puzzles of the first
www.adventofcode.com using JavaScript. Do something fun with code, and you'll learn real quick if you enjoy all the problems... and the solving of those problems.