Careers · Client Engineering: Las Vegas metro, onsite · Platform Engineering: remote, Pacific time
Be the engineer clients call first
Greybeard is a boutique IT firm for small businesses. One engineer you know by name, one flat number, a short client list on purpose. Two roles make that promise real. One faces the client. One makes the face look omniscient.
One voice per client. No ticket ping-pong, no "different tech every time." One person is accountable.
A crew behind the face. Humans and AI handlers do the background work; the client never gets passed around.
Writing is the job. Every commitment becomes a same-day record. If it isn't written down, it didn't happen.
Promises with numbers. Our response times aren't marketing copy. The platform we built enforces them.
Two roles. One seam between them.
The division is absolute: the background crew never contacts clients. All client-facing communication is Client-Engineer-voiced. The platform enforces it; it's not a policy we hope people remember. The two roles sit at the same level: different innate talents, same pay band.
Client Engineer
Client voice
Las Vegas metro · onsite + remote orchestration3+ yearsFull-time or contract
You are the face of an MSP that runs on a platform we built ourselves. You never walk into a meeting cold. You never get asked "who is this?" You are the answer.
What you own
- Dedicated clients: every call, email, and visit. One voice, one name, zero ticket ping-pong.
- Kitchen rule: you work the pass, and every dish gets your eye before it reaches a client. When the pass is quiet, you work the line beside the Platform Engineers. The pass always wins.
- Orchestration, onsite and off: between site visits you run your clients' support work remotely through the dossier, keeping onsite visits for what genuinely requires a body.
- The dossier: you run a pre-contact digest before every single contact: open promises, recent history, ready briefs. You never walk in cold.
- The chart: every commitment made on a call becomes a written record the same day. The chart is append-only; your word is the record.
- Per-client briefs: our position, the strongest counter, and the rebuttal, always with evidence. Stale claims never brief.
- Quotes: you never quote a price without an approved brief. No exceptions.
- The crew: you direct the crew: platform engineers and machine handlers. They never contact clients; anything client-facing routes through you.
What you never do
- Never let a crew member contact a client directly. The platform verifies this, not just the handbook.
- Never contact a client before the digest runs.
- Never brief from a stale or evidence-free claim.
What we're looking for
- 3+ years MSP or internal-IT senior experience (Windows domain, M365, networking, backups).
- Writes well under time pressure; the written record is part of the job.
- Comfortable being accountable: your name is on every interaction.
- Based in the Las Vegas or Henderson metro (required; this is an onsite role).
- Bonus: Spanish/English, prior vCIO or account-lead experience.
Platform Engineer
Judgment layer
Remote · Pacific time1-3 yearsJudgment over volumeSquad of 4, max
Taste is the job. The machine crew does the volume; your judgment decides what's true, what's good, and what ships. Every standard you set applies across all our clients at once. A foundational role, not a support one.
What you own
- The review seam: machine output that will harden into a client's record passes through you, same day. You decide what's true, what's good, and what ships.
- The bar: runbooks and acceptance criteria the machine handlers execute. If a machine can't tell "right" from "plausible," that's your spec, not its fault.
- The agent pipeline: acceptance runs before a handler goes live, re-acceptance after every model change, decommissioning when one stops earning its keep. You are the background check for software, as engineering, not HR.
- The residue: ambiguous or political signals escalate to the Client Engineer with a recommendation, not a forwarded blob.
- The human work: charted same day, with references. The machine's output is reviewed; yours is authored.
- The squad: you work in a group of at most 4 Platform Engineers, and review decisions are made together, because taste calibrates best in small groups. Nobody rubber-stamps.
What you never do
- Never contact a client. The platform enforces this, not just policy.
- Never let an unverified machine claim stand as truth: safety-critical facts are machine-attested from the systems themselves.
- Never wave through a marginal pass; never paste credentials into anything.
What we're looking for
- 1-3 years desktop/sysadmin experience (Windows domain, M365, basic Linux), enough to know what "right" looks like on the systems the crew works on.
- An editorial eye: you can tell a right answer from a plausible one, and write down the difference.
- Disciplined written follow-through: if it isn't charted, it didn't happen.
- Same level, different talents: the roles convert in either direction when talent fits. You learn every client through the dossier, and you gain deep platform knowledge either way.
The promises our Client Engineer keeps
These are the commitments our clients hold us to, the same ones you'd be accountable for as a Client Engineer. Some clients negotiate different numbers in their agreement; the signed deal always beats these defaults.
Client-facing service commitments (defaults; per-client agreements may differ)
| Commitment | What we promise |
|---|
| Every call routes | Bridge to the on-duty Client Engineer, or voicemail that lands in the client's dossier. No caller is ever dropped, even if our routing brain is down. |
| Office hours | 8:00 AM to 6:00 PM, Monday through Friday (Pacific). After-hours calls become transcribed voicemails in the dossier, never dropped. |
| Voicemail callback | Within 24 hours, same business day. |
| Commitments | Anything promised on a call is written into the client's record the same day. |
| Quote turnaround | Within 2 business days, and only after internal approval. |
| Emergency line | Response within 30 minutes: a live Client Engineer or an immediate callback, never voicemail-only for a declared emergency. |
And the internal standard behind them: the background crew's work is graded automatically: nothing dropped, nothing silent, everything charted the same day. That's what makes the client-facing numbers keepable.
How we work
Three principles run everything, including the hiring bar. You don't need to know the internals, but you do need to work this way.
01
Humans work the least determined seams
Machines take the determined work. Humans take the judgment. A human doing routine work is a delegation opportunity; a machine doing judgment work is a violation.
02
Time and quality are the gates
Work isn't accepted because it "seems done." It's done on time, at the quality bar, and with evidence. The platform measures both.
03
Nothing gets dropped
Every signal ends resolved, flagged for attention, or on the record. Nothing silently closed, nothing quietly deleted.
04
The dossier is the memory
Every client has a living record: chart, vitals, and briefs. Assembled by the whole crew, voiced only by the Client Engineer. It's why nobody ever walks in cold.
"You never walk into a meeting cold. You never get asked 'who is this?' You are the answer."