This mostly sounds good but I wonder if you'd make it better by dropping the strict postgres requirements.
I've never used postgres. I've worked with umpteen technologies over the years, including lots of gis, just never needed to use postgres yet. But I know it's out there and I'm confident if I needed to, it wouldn't take more than a few days to catch up.
Not a dig at you specifically but a lot of companies seem to look for specific tech experience rather than a track record of just learning whatever tech is needed.
I hear you! We’ve definitely had candidates we’ve talked with in the past who didn’t have experience with the tech stacks involved. In our case, we’re not suffering from a lack of qualified candidates (quite the opposite!), so we can afford to be more strict in requirements.
I remember a friend describing interviewing as a search problem. How long and how much resource is one willing to spend on a search? And then, adjust the hiring process (for employer) or job search process (for candidate) accordingly.
I've never used postgres. I've worked with umpteen technologies over the years, including lots of gis, just never needed to use postgres yet. But I know it's out there and I'm confident if I needed to, it wouldn't take more than a few days to catch up.
Not a dig at you specifically but a lot of companies seem to look for specific tech experience rather than a track record of just learning whatever tech is needed.