Granted, zero wrong with a candidate letting me know that he/she does not want to work on the front end but with the understanding that there may come a time where some minor front end/full Stack projects may be needed, and on a case by case basis I may ask them to help out.
Just looking out for you, as I think if you did some front end side projects (simple to do apps, crud apps, or anything like that) it'd make you a much better backend developer.
Even just a simple Django or flask app with angular, or some basic JS/jQuery would show you some of the pitfalls of the front end and how to design your APIs, services/microservices in a way that helps out your front end teammates consuming them.
As for Portland, I believe LaunchPad or Smarsh is based out of Portland, which are pretty cool companies to work for.
Tl;dr . Yes, people look for backend developers a lot. Doing some front end side projects(small crud apps) will make you a better back end developer.
Best of luck!!
My point was if you have intermediate backend programming ability with a DBA background and you're concerned about getting a backend role you should be careful, yet clear about what you're willing to do.
Generally speaking, if a candidate comes across as willing to help out on a case by case basis but the vast majority of their workload is backend that's an easier hire by far. Is the trade-off of a potential 95/5 split of time worth it to the developer? That's a personal decision to the developer.
Unless you're never going to be writing code that is directly consumed by a front end or full Stack developer it is a good idea/practice to understand basics of the front end.
So yes, you are correct that if the poster never was willing to touch the front end he'd be harder to hire for the company but that's just because we want people to be open to new technology and the full Stack.
Either way, I think it'd be unwise to not learn basics of the opposite side you're on to stay relevant and be an attractive hire. N=1.
2.) You can work on the back-end and use Javascript. The two things are not mutually exclusive.
3.) "Services that others developers build upon" do not exclude the front-end. D3 is something other developers build upon, along with front-end interfaces to back-end services. There are many more examples of this.
---
Anyway, to answer your question: it is yes. Large tech companies readily employee developers to work primarily on the back-end. To increase the likelihood that you'd be working on distributed systems, I'd try to join a team that works on a product that is already at scale (Google Maps, Facebook Newsfeed, Amazon AWS, etc.)
Edit: I know JavaScript can be done on the server side via nodejs I was talking more about the client side soup of libraries that I'm not interested in
I'd look at AngelList for companies in Portland.
But yes, that's a role companies hire for all the time. I believe we are currently hiring for those roles as well.