MTA is an Alaskan ISP serving the southwest area of the state. The software team consists of 7 devs who support a relatively complex business enterprise environment. We're looking to add another Software Engineer and a dedicated Systems Engineer (DevOps) to our team.
As the hiring manager I want to be clear about a few things:
- This is a 70 year old enterprise telecom, not a high speed startup
- This job may interest you if you want great benefits and long-term job stability
- We have an existing environment running onsite on VMWare; the Systems role is designed to support, improve, and make adjustments to our tech stack over time
- Our core backend language is F# these days (replacing Haskell after 5+ years in production), frontend is React
- Our DevOps tooling is built around Terraform, Chef, Nomad, Vault, Concourse CI, Sensu, Prometheus, etc
- Must be authorized to work in the US
Software Engineer: https://mta.csod.com/ux/ats/careersite/4/home/requisition/59...
Systems Engineer: https://mta.csod.com/ux/ats/careersite/4/home/requisition/60...
If the team had been full of diligent Haskellers they'd have stuck with it, but they aren't really the type to align with a language/paradigm, and so a slow pivot into F# was decided ~2 years ago via a well documented RFC process.
I'm personally still a Haskell fan, but my hand isn't on the keyboard anymore. Not my place to make the tooling choice for them.
No one above me cares about this type of choice since we're a small backend department to internal customers. As long as the team is delivering results by the deadlines we commit to we get a lot of freedom to use whatever tooling we think makes sense.