Code and Coordinates
engineering at Geocodio
We're Hiring: A Software Engineer and a Technical Support Engineer
Two new seats at a small table
By Emily Backe
We've been heads-down on the UK launch, a website redesign, and, if you've seen our Twitter lately, a whole lot of confetti. Somewhere in the middle of all that, we quietly ran out of hands. So we're doing something we've gotten pretty used to lately: adding more people to a team that's still, by design, pretty small.
We're looking for a Software Engineer (Laravel/PHP) and a Technical Support Engineer (GIS). One of these is for people who like working in every nook and cranny of a codebase. The other is for people who feel a huge sense of relief when a tricky address finally geocodes correctly.
Please read before applying
For collaboration reasons, both roles are based in US Eastern Time. We kindly ask you not to apply if you live outside of US Eastern.
The Software Engineer role
We're a dyed-in-the-wool Laravel shop and have been built on Laravel since 2014. Most of what runs Geocodio is Laravel and PHP, with a small corner of Go for the parts that need it.
If you like moving around a codebase instead of living in one corner of it, and you've worked somewhere small enough to know what it's like to wear a few hats at once and even occasionally sew new ones on your own, this might be your kind of place.
The Support Engineer role
Every support ticket we get is really a small data or communication problem wearing a customer service costume. Someone's address didn't geocode the way they expected, and somewhere behind that is a parsing quirk, a missing data source, or a boundary that shifted after the last redistricting cycle. Or perhaps just a missing bracket from their API request that magically fixes everything. We want someone who loves solving problems for people and gets a little bit obsessed with figuring out why, and then goes and fixes the actual cause instead of just closing the ticket.
We mean it when we say entry-level and career-changers are welcome. You'll need some comfort with APIs, some familiarity with geographic data (shapefiles shouldn’t be a new concept), and prior experience solving problems for people in a customer support setting (such as a help desk or retail).
Sound like your kind of problem to solve?
We'd love to hear from you.
Software Engineer (Laravel) posting →
Technical Support Engineer posting →
And if neither is quite right but you'd still like us to keep you in mind, our general application is always open.
Get new posts in your inbox
We write about what we're working on, thinking about, and getting so excited playing around with that we accidentally stay up a bit too late.
Thanks for subscribing!