Let me try hard to add something of value while also saying "contact me, my customers are hiring high-scale, low-latency, C coders by the dozens". :)
I started coding in C 30 years ago when we had machines with 768k of memory and processors that have less power then the cpu in the elevator in my building.
I have a theory that as cpu power, ram and other resources have scaled to amazing levels more and more problems can be solved with higher level languages without the need to eek every single cpu cycle or byte of ram out.
"We should forget about small efficiencies, say about 97% of the time;
premature optimization is the root of all evil"
-- Donald E. Knuth
I think it's perfectly fine to approach many problems with PHP, ASP.NET, Python or any number of solutions as long as the problem is solved in a way that meets the requirements. Not every problem needs to handle millions of queries per second at the lowest latency and best cost possible. The speed from "problem" to "solution" can be many times faster offsetting the potential cost of running a couple extra servers to soak up the inefficiencies of the system.That said in my field of work we see 40 Billion transactions daily with Million query per second spikes. In that world you can't afford to deploy 10,000 servers running a nice django server. You need to dive deeper and deeper, ending up with front-line servers written in C and optimizing with non-locking data structures and sweating over memory fences and cache lines. This however is a rare slice of the total problem set that programmers have to face every day.
IMHO it's the power curve of cpu power and resource availability that creates a wider and wider gap between low level, low latency, high scale programmers and many programmers who "get stuff done" perfectly fine every day of the week.
I have posted before on HN about the strange patterns that are emerging around the shift to "post-desktop" era, and this trend is also another topic of interest to me. I have to wonder as Moore's law levels out who will be contributing to solutions solved with 1,000's of cores on a chip and all the problems associated with adapting problems to massively parallel architectures.
I guess my answer is: Look harder, there are lots of low-level, high-scale jobs out there.