Systems
AI SystemsMethodWorkOperationIndustriesField Notes
Solutions
EnterpriseRegulated IndustriesProcessesIntake and ServiceDocument ReviewReconciliation
Integration
Systems of RecordModel GovernanceAudit TrailChange ControlBlueprintData Residency
Company
AboutEngagementsSecurityOversightCareersContact
EngagementsNews
Talk to Us

Careers

Build AI that
carries real work.

A senior team building AI systems that run inside other companies' operations. Forward deployed, accountable for what we ship, and still running it a year later.

Why Lyrion

Forward deployed

You work inside the client's business, with the people who do the job, not from a distance.

  • Accountable for what we ship

    The engineer who scopes a system builds it and then operates it.

  • Still running it a year later

    You find out what you got wrong, and you fix it, because the system is still yours.

  • Systems of record

    ERPs, CRMs, policy and claims systems, document stores: the real platforms, not a sandbox.

  • Range

    Insurance, construction, energy and financial services. The work changes; the method does not.

  • A senior team

    Between 11 and 50 people, based in San Francisco, travelling to the client.

  • One system that runs

    We would rather own one system that runs than ship five that do not.

What to expect

How we hire

Applications are read by the engineers you would work with.

  1. Introduce yourself

    Tell us what you have built and taken all the way into production.

  2. A first conversation

    A conversation about the work, where your experience fits, and how you think about systems that run inside someone else's business.

  3. Working sessions

    We work through a real process together: how it runs, where it breaks, and what you would build first.

  4. An offer

    If the fit is right on both sides, we make an offer to join Lyrion.

FAQ

Working at Lyrion

Common questions about working at Lyrion as an engineer.

What is the first conversation?

A conversation with an engineer about the work, where your experience fits, and how you think about systems that run inside someone else's business.

Do you do LeetCode-style interviews?

No. We work through a real process together: how it runs, where it breaks, and what you would build first. If you have taken real systems all the way into production, that's more than enough.

Who reads my application?

The engineers you would work with. Tell us what you have built and taken all the way into production, and they will be in touch if the fit is right.

How much of the work is on site?

As much as the process needs. Our engineers work remotely and travel to the client, and scoping happens with the people who do the job, wherever they are.

What happens after go-live?

You keep running what you built. The engineer who scopes a system builds it and then operates it, so you find out what you got wrong and fix it.

Where we are

San Francisco, and wherever the work is

Our team is based in San Francisco, California. Our engineers work remotely and travel to the client.