saltypal

Eleos Technologies (https://eleostech.com) | Remote Senior iOS Engineer | Permanently Remote (US-based applicants only) | Full time

Eleos Technologies is a growing company building communication software for truck drivers and the back-office workers who support them. We’re looking to scale up a second product engineering team to ship more advanced driver planning tools, automate outdated workflow, and a bunch of other wins to make drivers’ lives easier and more efficient.

We're looking for someone who has the experience to move fast on new stuff and knows how and when to pick their battles on old stuff. You'd be one of four iOS engineers at a company that's big enough to survive an economic downturn, but not so big you can't make immediate, direct impact that'll be seen and appreciated by the whole company. (We've also spent the last decade working really hard to make sure our tools, processes, and culture respect everyone's work/life balance. I'm the CTO and I don't text people on my team, and they don't text me, and that's true throughout.)

It's a native iOS app written in a mixture of Objective-C and Swift, leaning on Swift for new features. (But that said: if you chafe at the idea of maintaining or fixing bugs in battle-tested Objective-C that's paying our salaries, please look elsewhere!) We have about 1/3rd functional/UI automated test coverage and the rest is human-powered by our QA team.

If you're interested, please share your info via https://jobs.lever.co/eleostech/b4866f22-fab3-4f84-abec-6e74... and we'll get in touch!

Check out https://github.com/anthropic-experimental/sandbox-runtime, which tackles this problem using the built-in userspace sandboxing on macOS and Linux.

I run Claude from a mounted volume (but no reason you couldn't make a user for it instead) since the Deny(~) makes it impossible to run from the normal locations.

export CLAUDE_CONFIG_DIR=/Volumes/Claude/.claude

Minimal .claude/settings.local.json:

    {
      "permissions": {
        "allow": [
          "Read(/)",
          "Read(~/.claude/shell-snapshots/\*)",
          "WebSearch",
          "WebFetch(domain:example.com)"
        ],
        "deny": [
          "Read(~)",
          "Write(/.claude/settings.local.json)",
          "Write(/method_filter.py)"
        ]
      },
      "sandbox": {
        "enabled": true,
        "autoAllowBashIfSandboxed": true,
        "allowUnsandboxedCommands": false,
        "network": {
          "allowLocalBinding": true,
          "httpProxyPort": 9655
        }
      }
    }

Eleos Technologies | DNS Consulting | REMOTE (US) | Contractor

We build mobile apps and supporting systems for long-haul truck drivers.

We have a critical DNS registrar/hosting migration to do this year and while I did the last one (on a less-critical domain), I'd really like support from someone who has done >5 of these to help our team get it right. Good news: no DNSSEC. =)

Please reach out to me at [email protected] and mention this post if this is you and you have a reference or two. It should be really easy project for the right person, but we'll compensate commensurate with the business risk.

With two[1] other[2] great articles about the guts of how programs _actually_ get loaded and run, I was reminded of the above great (multi-part) article, which I remember reading on the subway in tiny chunks and being surprised it ever works at all.

My CS degree was from a liberal arts university, and while I wouldn't trade anything for the coverage of ethics, previous AI bubbles/winters, and my time in the business and mathematics departments, these articles along with the glibc author's What Every Programmer Should Know About Memory[4] rounded out my education. I still make use of concepts from both when profiling and debugging programs.

[1]: https://news.ycombinator.com/item?id=45706938

[2]: https://news.ycombinator.com/item?id=45706380

[3]: https://www.cs.dartmouth.edu/sergey/cs108/ABI/UlrichDrepper-...

[4]: https://people.freebsd.org/~lstewart/articles/cpumemory.pdf

See also: https://stackoverflow.com/questions/8126311/how-much-of-what...

I hadn't yet seen it when I wrote this, but 2 is pretty much exactly what Arko says:

> Worried about the possibility of hacked accounts or some sort of social engineering, I took action as the primary on-call engineer to lock down the AWS account and prevent any actions by possible attackers.

https://andre.arko.net/2025/10/09/the-rubygems-security-inci...

Putting myself in Arko’s shoes, I can imagine (charitably!) the following choice, realizing that I still have access and shouldn’t:

1. Try to get in touch, quickly, with someone with the power to fix it and explain what needs to be rotated.

2. Absent 1, especially if it cannot be done quickly, rotate the credentials personally to get them back to a controlled state (by someone who actually understands the security implications) with the intent to hand them off. Especially if you still _think_ of yourself as responsible for the infrastructure, this is a no-brainer compared to letting anyone else who might be in the same “should have lost access but didn’t, due to negligence” maintain access.

Not a legal defense, but let’s not be too hasty to judge.

I would only partially agree that Kotlin is "much safer."

As one example, I just learned (by way of a nasty production app crash) that Kotlin chose to make all checked exceptions silently unchecked. Kind of a stunning own-goal for a language from 2010.

Previously: https://news.ycombinator.com/item?id=3947903

(I feel incredibly old right now.)

Edited to add: Finally found the full form letter [1]. (I filed a copy back then and it still shows up languishing in Feedback Assistant even now!)

[1]: https://gist.github.com/mysteriouspants/1989061

Eleos Technologies (https://eleostech.com) | Remote Front-End Web Engineer | Permanently Remote (US-based applicants only) | Full time

Eleos Technologies is a growing company building communication software for truck drivers and the back-office workers who support them. We’re looking to scale up a second product engineering team to ship more advanced driver planning tools, automate outdated workflow, and a bunch of other wins to make drivers’ lives easier and more efficient.

We're looking for someone with several years of professional web experience who's looking to learn and flourish at a company that's big enough to survive an economic downturn, but not so big you can't make immediate, direct impact that'll be seen and appreciated by the whole company. (We've also spent the last decade working really hard to make sure our tools, processes, and culture respect everyone's work/life balance. I'm the CTO and I don't text people on my team, and they don't text me, and that's true throughout.)

The stack is Erlang/Elixir with a ClojureScript+React frontend with robust automated test coverage.

If you're interested, please share your info via https://jobs.lever.co/eleostech/629c95b5-2205-4d5e-af25-4ca5... or feel free to reach out to me directly if you have questions (email is in my about/bio).

Eleos Technologies (https://eleostech.com) | Senior Android Engineer | Permanently Remote (US-based applicants only) | Full time

Eleos Technologies is a growing company building communication software for truck drivers and field workers, and Drive Axle is our consumer-facing document scanning app. We’re looking to scale up a team to invest further into this product and ship more advanced scanning capabilities, driver planning tools, and other features to make individual drivers’ lives easier.

We're looking for someone with several years of professional Android experience who's looking to learn and grow on a team with multiple members with 10+ years experience on mobile in a company that's big enough to survive an economic downturn, but not so big you can't make immediate, direct impact that'll be seen and appreciated by the whole company. (We've also spent the last decade working really hard to make sure our tools, processes, and culture respect everyone's work/life balance. I'm the CTO and I don't text people on my team, and they don't text me, and that's true throughout.)

If you're interested, please share your info via https://jobs.lever.co/eleostech/edff9316-f691-43be-8947-3ff0... or feel free to reach out to me directly if you have questions (email is in my about/bio).

Oh wow, thank you!

I'd been poking through them with plain old `sqlite3` and then deserializing all the plist data with something like `pbpaste | xxd -r -p > foo.plist` for examination, but had no idea datasette existed and https://datasette.io/plugins/datasette-bplist#user-content-t... seems like the ticket for browsing these.

For others: all the Caches.db files are the per-process HTTP cache that NSURLRequest/NSURLSession keeps, so if you peek at it you can see (partially) a history of network requests that process has made. Most of them seem to pull feature flag configuration from https://bag.itunes.apple.com/bag.xml, but others do more interesting things.

Eleos Technologies (https://eleostech.com) | Android Engineer | Permanently Remote (US-based applicants only) | Full time

Eleos Technologies is a growing company building communication software for truck drivers and field workers, and Drive Axle is our consumer-facing document scanning app. We’re looking to scale up a team to invest further into this product and ship more advanced scanning capabilities, driver planning tools, and other features to make individual drivers’ lives easier.

We're looking for someone with a small amount of professional Android experience (or a substantive side project) who's looking to learn and grow on a team with multiple members with 10+ years experience on mobile.

If you're interested, please share your info via our jobs page (https://jobs.lever.co/eleostech/fd8bbee8-f5c1-4dcd-8e73-fe31...) or feel free to reach out to me directly (email is in my about/bio)

We've got a similar role open for iOS, too, if that's more your speed: https://jobs.lever.co/eleostech/62b47296-9e81-4b1e-be52-3db1...

Email George Blood LP (https://www.georgeblood.com/), they have support to read like 100+ old magnetic formats and are wonderful pros.

Separate teams. We have a tiny team and even _we_ appoint a group to fix and a group or individual to do nothing but communicate.

This. We have a 4-person team and posted our own incident about this 7 minutes before Amazon did. Surely they can aim a little higher.

Based on our telemetry, this started as NXDOMAINs for sqs.us-east-1.amazonaws.com beginning in modest volumes at 20:43 UTC and becoming a total outage at 20:48 UTC. Naturally, it was completely resolved by 20:57, 5 minutes before anything was posted in the "Personal Health Dashboard" in the AWS console.

It takes a while to find a Vice President, I guess.

Eleos Technologies (https://eleostech.com) | Multiple: Infrastructure Observability / Senior iOS Software Engineer | Permanently Remote (US-based applicants only) | Full time

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!

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. These features are (with a couple of specific and thoughtful exceptions) natively implemented, and we take the performance and stability of the app seriously.

Both roles are listed here with a bit more description, and you can apply there, or feel free to reach out to me directly (email is in my about/bio) if you don't trust throwing your resume into a large hiring tool! https://eleostech.com/careers

(I'm the hiring manager and the actual manager for the role, so I'll see it either way.)

Eleos Technologies (https://eleostech.com) | Senior iOS Software Engineer | Permanently Remote (US only) | Full time

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!

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. These features are (with a couple of specific and thoughtful exceptions) natively implemented, and we take the performance and stability of the app seriously.

For more details and to apply, head over to: https://jobs.lever.co/eleostech/f6ccb4be-24c9-4fa0-b695-e83d...

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 in the two links above. If you have questions, feel free to comment here. If something in the post discourages you from applying, I'm also curious to hear about that! I'm happy to share info about our interview process, stack, and vertical.

Eleos Technologies (https://eleostech.com) | Senior Erlang/Elixir Software Engineer / Senior SRE | Permanently Remote (US only) | Full time

Eleos Technologies is a growing 9-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!

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. This is all powered by an Erlang/Elixir OTP application, and we're looking for someone who's used this stack in a production setting before, recognizes the advantages of OTP, and would like a key role in a maintaining and extending such a system. https://eleostech.com/careers/backend-elixir

We're also looking for somebody with more interest or background in the operations side of thing, since we're finally at a point where we need somebody thinking about this full-time in addition to our existing backend team sharing the pager and ops responsibilities. https://eleostech.com/careers/sre

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 in the two links above.

If you have questions, feel free to comment here. If something in the post discourages you from applying, I'm also curious to hear about that! I'm happy to share info about our interview process, stack, and vertical.

Eleos Technologies (https://eleostech.com) | Senior Erlang/Elixir Software Engineer | Permanently Remote (US only) | Full time

Eleos Technologies is a growing 9-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!

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. This is all powered by an Erlang/Elixir OTP application, and we're looking for someone who's used this stack in a production setting before, recognizes the advantages of OTP, and would like a key role in a maintaining and extending such a system.

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 over here: https://eleostech.com/careers/backend-elixir

Eleos Technologies (https://eleostech.com) | Senior Erlang/Elixir Software Engineer | Permanently Remote (US only) | Full time Eleos Technologies is a growing 9-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!

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. This is all powered by an Erlang/Elixir OTP application, and we're looking for someone who's used this stack in a production setting before, recognizes the advantages of OTP, and would like a key role in a maintaining and extending such a system.

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 over here: https://eleostech.com/careers/backend-elixir

We use a homegrown gnuplot version of this at $work, and I can speak from experience that you can immediately spot problems (timeouts, as a set of ghostly horizontal lines, or outlier requests) that would be absolutely hidden in a traditional p50/p95/p99 chart.

I wish more (hosted) monitoring systems would shift to this type of visualization, since computers are fast now (I'm told!)