Skip to main content
ECHELON

Careers

Small team. Operators only.

Echelon builds and runs AI infrastructure inside established companies. Everyone on the team has shipped a system that handled real work in production and stayed on to run it. If that is you, write to Yadel.

The core team is small on purpose. Build capacity comes from Echelon's engineering bench of 100+, so these are operator seats: you run builds with Yadel and a development manager. You do not fill a bench.

Team
Small and senior
Base
Los Angeles, CA
How to apply
One email to yadelf@echelon-advising.com

01The work

What you would be doing.

01

Real installs

You build systems that handle a client's real leads, quotes, and invoices, under approvals, and you stay on to run them.

02

Our own operations first

The engines that run Echelon are built by the same people. Every control ships here before it ships to a client.

03

A direct line to the founder

Small team. You work with Yadel on every build, and your name is on the weekly report.

02Roles

Six seats. Location and type only.

Every role builds and runs. Nobody here only writes the plan.

  • Infrastructure architect

    Maps the operation with the client, designs the five layers, and writes the brief for every agent: what it reads, what it prepares, and what it may do alone.

    Location
    Los Angeles, CA or remote
    Type
    Full time or contract
  • AI systems engineer

    Builds the agents, the limits, and the console into the client's stack, and runs them in review mode until each action has earned narrow authority.

    Location
    Los Angeles, CA or remote
    Type
    Full time or contract
  • Integration engineer

    Connects the CRM, the inbox, the phone line, and the payment tools, both ways. Verifies every connection before anything depends on it and builds the readback.

    Location
    Los Angeles, CA or remote
    Type
    Full time or contract
  • Prompt and evaluation engineer

    Turns each written brief into a working agent, builds the evaluations that prove it, and reads the exceptions queue to find what to fix next.

    Location
    Los Angeles, CA or remote
    Type
    Full time or contract
  • Operations lead

    Runs the weekly report with the client, owns the exceptions queue, and keeps a named owner on every decision from launch onward.

    Location
    Los Angeles, CA or remote
    Type
    Full time or contract
  • Distribution

    Runs the content engine: a real source, an angle, a draft, a review, a published piece, and the measurement afterward.

    Location
    Los Angeles, CA or remote
    Type
    Full time or contract

03What we look for

Five things, in this order.

  1. 01Shipped to productionYou have built a system that handled real work for real people, and you stayed on to run it.
  2. 02Builds inside the toolsYou build into a CRM, an inbox, a phone line, and a payment tool, and you verify a connection before anything depends on it.
  3. 03Writes it downThe brief, the limits, the approval gate, the weekly report. You can explain what a system may do alone to someone who does not write code.
  4. 04Output, not hoursYou measure your week by what ran, not by what was logged.
  5. 05Owns the exceptionsWhen the system escalates, you pick it up, fix the cause, and write down what changed.

04How hiring runs

Three steps, none of them a quiz.

The same shape as an install: a conversation, a map, and a piece of real work in review mode.

  1. 01

    Write to Yadel

    One email. What you built, where it ran, and what you ran after it launched. A link to something in production beats a resume.

  2. 02

    A working session

    One call on a real process. You map it with Yadel and talk through what you would build, where the approval gates go, and what the system may do alone.

  3. 03

    A scoped build

    One scoped piece of real work, in review mode, with the same weekly report we send clients. If it ships, an offer follows.

05Apply

Or use the form.

Same inbox, same reader. Every submission is read by a person.

Explain the difference between review mode and narrow authority, the way you would say it to a client.

Your first department

Bring the process you still run by hand.

One mapping call. You leave with the system design, the price in writing, and the date it goes live. The first build lands in two weeks.

About

Built for our own operations first.

The founder, the systems Echelon runs on itself, the four principles, and the bench in aggregate.

About Echelon