[CornCobs]

Counter-anecdote: I'm working at a non-tech company (we build the in-house technical software that everyone else in the company uses) and the experience has been great. We deliver real and immediate value, our clients are our colleagues and there's a great emphasis on UX, user testing and what not as a result.

Yes, there are loads of other problems, especially on the technical side, because tech isn't the company's strong point (our processes, especially revolving around the DB and deployment, are quite a mess) but the right things are in place that make me enjoy my job.

[drewcoo]

That might be the counter-anecdote that proves the rule.

In my own humble anecdotal experience, the less focused a company is on tech, the worse. Beyond that, if management is not from a software (or engineering) background, they will likely have no clue what to expect from programmers (because such hard things are simple and such simple things are hard) and the treatment will be . . . strange.

[ipaddr]

That gives you more freedom

[bluefirebrand]

I would love to get a job building internal tools that my company needs and uses but I haven't had any luck actually finding those kinds of jobs, so I always wind up building products.

Any advice on how to find those kinds of positions?

[pc86]

Connect with a recruiter (or five) and tell them that's what you want. They exist to act as a filter, and if you work with several from multiple companies/geographies in addition to doing your own searching, you'll eventually find what you're looking for.

[cholantesh]

In my experience, recruiters basically keep your name and skillset on record and don't take into account any of your other wants/needs.

[pc86]

You've worked with shitty recruiters, which is to be expected because most of them are.

Some of them are great and they're the ones worth keeping in touch with.

[bluefirebrand]

I'm honestly surprised how many don't even seem to take your skillset into consideration.

You don't have to know much about programming languages to know that if none of the words on my resume match the ones in the job listing, it's probably not a good match.

Maybe I need to be more clear that while I'm willing to learn new tech for a job, I probably don't want jobs where I have to learn an entire new stack just to get started.

[mriet]

Agreed -- and, even worse, in my experience they don't even know about more than 20% of the opportunities.

[mouzogu]

connecting with recruiters is a meme.

they're basically glorified salespeople. they would only reply to you if they thought there was quick money to be made.

[CornCobs]

I ended up in this current position because I was first interested in their field of work (geospatial work), and secondly skilled in programming. Even if I weren't a programmer I would probably work for them in some other capacity.

I don't feel qualified giving advice but personally I think I would look beyond what is commonly considered "tech". As another poster mentioned, everyone uses tech. When a company's work is sufficiently complex or special, chances are they may not rely on external vendors 100%.

Really out of my depth here but maybe some types of firms where I think there could be some interesting stuff internally:

- engineering - analytics - games - graphics/animations

[aprdm]

Vfx industry