Eleos Technologies is a growing 10-year-old company building communication software for truck drivers and field workers. We’re helping a diverse mix of customers—from mom and pop operations to household names—improve how they communicate with their employees by tackling information overload, reducing phone calls, and eliminating obsolete technologies. Our app is used by thousands of big-rig and small truck drivers, day and night, every day, and we’ve been on a sustainable growth curve for long enough that we’re ready to grow our backend team!
My name: Phil Calvin
My position: VP of Engineering
Company name: Eleos Technologies
Company info and history (how you’re using Elixir etc):
Alongside native iOS and Android apps, our core product is powered by a Elixir/Erlang OTP backend. It began life as an Erlang app, and we started using Elixir in this app about two years ago for all new features and tests. We love the language and the additional boost we get from a highly active library and tooling community.
About the job
Job title: Senior Software Engineer
Job description: Elixir/Erlang product engineer driving the development of new product features and functionality. Providing timeline and risk estimates for new efforts to help optimize our roadmap.
Position on remote work: Permanently remote, team get-together once a year
Qualifications or experience required:
- 4+ years professional experience implementing and operating production systems on a major cloud platform (AWS, GCP/GAE, Azure)
- 2+ years professional experience working with Erlang or Elixir (and thus the BEAM runtime and OTP)
We’ll happily teach you everything else you need to know.
What the successful job applicant will be working on: You’d be adding new web endpoints, extending and evolving both internal APIs used by our mobile apps and collaborating systems, as well as public-facing APIs used by our customers. You’ll be architecting and implementing new data flows, storage mechanisms, and integrations with external tools to meet business needs and product requirements, and helping set direction for the codebase, deployment model, and QA methodology.
About the interview process
We’re a writing-focused team, and try to use meetings only when they’re the best tool, and not as our first tool. As a result, I typically email directly with applicants a bit before asking them to take time out of their workday to “hop on a call.” If there’s mutual interest and fit, we’ll talk by phone, then schedule a screenshare session (with Google, using your preferred tools) to pair on a lightly-contrived codebase, then finally a call with our CEO, CTO, and an opportunity to (virtually) meet the whole engineering team. At that point, we’ll make an offer.
Our engineering team has been 100% distributed since day one. This means we’re tooled up to handle product, architectural, technical, and ops work all from home or remote. You won’t miss out of office conversations, and you won’t have to learn to drive a telepresence robot.
We began life as a bootstrapped startup, which allowed us to focus on building products our customers love. Today, we’re part of the Knight-Swift family, which has allowed us to keep our focus and the freedom to build the best products we can for the transportation industry. We offer robust healthcare (dental, medical, vision), paid time off, and a generous equipment budget.
Our driver-facing mobile app does some unique things, including assisting drivers with planning their trips, finding stopovers, managing their electronic duty log, and more.
As a remote team (since founding!), we’re super lucky to have some great folks who use the ability to work from home to spend more time with their kids, help volunteer at a school, or otherwise be more fulfilled than they would be working from an office. You could join us!
If that sounds fun and rewarding to you, the full description and info about applying are here: