It's been split between three areas - writing mathematical code that wouldn't really benefit from numpy, at least not at first (think engineering design codes - step-by-step calculations where the output has to be verifiable by a human; charts and graphs aren't the focus (I'm not at this company anymore)), writing testing infrastructure for a legacy client/server application that was designed around the time Ethernet was invented (well before I was born), and writing library code for my QA team to write tests for said application.
Most of these domains are sort of document-oriented - for the math stuff, the hard part is just defining the model, and there is only one "thing" to operate on. For testing, the units of work are test cases and steps, which _could_ be database entries, but work better in practice as a document that a non-technical QA team member could edit by hand. Results are fed to a SaaS that keeps all the historical test result data.
Not that I couldn't pick up either one of these tools and use them (I'm a mechanical engineer by training and got into Python because I didn't like using Matlab/Octave), I've just never needed them professionally. But that doesn't get me past the resume filters :(
