Infrastructure Engineer — Database & Cloud Operations, Heavy Materials and Logistics (Remote)

Infrastructure Engineer — Database & Cloud Operations Remote · Full-time

About XBE XBE is the system of action for businesses that move ready-mix, asphalt, aggregates, and cement — scheduling jobs, dispatching trucks, pricing and quoting work, tracking materials and inventory, managing rate agreements with haulers and customers, and keeping the financial picture and compliance straight. One system instead of a dispatcher’s whiteboard, a stack of paper tickets, and three tools that don’t talk to each other. We’ve tracked 475 million tons of material and $3B in trucking spend for operators who used to run this business on gut feel. Effectiveness first, efficiency second. Accountability as a force multiplier, not a burden. That’s how a small, fully remote, AI-first engineering team ships real software for an industry most tech companies don’t bother with.

The Role You will own the health, performance, and evolution of XBE’s production database and cloud infrastructure. This is a hands-on infrastructure-engineering seat — real Postgres administration, real data-lifecycle engineering, and real cloud operations, not a diagnostics-only or ticket-queue role. We lean toward candidates who are deep on databases and comfortable running production infrastructure on Render, but a strong generalist with the right instincts and a genuine willingness to go deep on Postgres will also be a fit. Work from anywhere, with significant overlap with the US morning shift. We expect real-time availability when production or time-sensitive operational windows demand it

Core stack PostgreSQL, Crunchy Bridge, Render, Linux/Ubuntu, systemd, Bash, Ruby on Rails / ActiveRecord, JDBC, Amazon S3, Terraform, GitHub, Cloudflare, OpenTelemetry, Grafana, Better Stack, Datadog, SigNoz, pganalyze.

What you will own

• Production database infrastructure — Postgres upgrades, roles and permissions, monitoring, backup and restore workflows, partitioning strategy, and performance troubleshooting.
• Data lifecycle automation — OLTP-to-OLAP archival, Postgres partition movement, archive schemas, S3/Parquet data-warehouse flows, cron jobs, and long-running background workers.
• Cloud infrastructure operations — Render, AWS/S3, Cloudflare, and the services around them.
• A JSON API for core services on the Ruby on Rails platform — building and maintaining it as infrastructure needs evolve.

You are a fit if

• You have run production Postgres at real scale — upgrades, partitioning, backup/restore, performance tuning — and can talk through specific incidents.
• You are comfortable in Linux, systemd, and Bash, and you don’t need a GUI to know what a server is doing.
• You have built or maintained data pipelines that move data between OLTP and analytical or archival storage.
• You have shipped production Ruby/Rails code, or can point to strong evidence you would pick it up fast.
• You read EXPLAIN ANALYZE output and execution plans with confidence.
• You use infrastructure-as-code (Terraform or similar) rather than making untracked changes by hand.
• Bias for action, high standards, low ego.

Nice to have

• Direct experience with Crunchy Bridge or Render specifically.
• Observability stack experience — OpenTelemetry, Grafana, Datadog, SigNoz, Better Stack, pganalyze.
• Experience integrating AI agents into infrastructure or database operations tooling.
• Background in construction-tech, logistics, or any operations-heavy domain.

How we build (AI-first, but not careless)

• Coding agents write a lot of the automation and tooling; you own the outcome and the blast radius.
• You verify database and infrastructure changes with monitoring, backups, and staged rollouts — not trust.
• Good runbooks, guardrails, and rollback plans are part of the engineering work, not separate from it.

What success looks like

• Production Postgres stays healthy, fast, and recoverable as data volume grows.
• Data lifecycle automation keeps hot storage lean without losing anything that matters.
• Cloud infrastructure gets more reliable and more cost-efficient at the same time, not one at the expense of the other.
• The team trusts infrastructure changes because they are tested, observable, and reversible.

What you will get

• Stability and long-term runway — an established, growing company with a steady platform and clear priorities.
• High ownership and trust — clear outcomes, minimal bureaucracy, no micromanagement.
• An AI-forward engineering culture — we expect you to use AI coding agents as a force multiplier for automation, diagnostics, and operational tooling.
• Substantive technical growth — you will deepen your expertise in database engineering, cloud operations, and AI-native workflows alongside engineers who take craft seriously.