Help us build automation that never guesses.

Businesses trust Lodol with their invoices, payments and records, so guessing isn't an option. We're the small, remote team that builds it.

How we work

We're seven people, and we shipped 124 releases in the past year.

That pace comes from four habits, and they aren't for everyone.

  1. No relay race

    The person who spots a problem is usually the one who fixes it, often that same afternoon.

  2. Small pieces, every week

    A real improvement this week beats a grand one next quarter. Done means in front of customers.

  3. Build for the worst day

    Not for the demo. The unglamorous work gets done whether or not anyone is watching.

  4. Own the outcome, not the ticket

    Whoever builds something owns how it lands, all the way to the customer who depends on it.

Read how a small team ships every week

Who you'd work with

Everyone here, founders included.

We come from places like Stanford, Amazon, Orby AI and Yale.

  • Ricky Grannis-VuCo-Founder & CEO
  • Kevin DuanCo-Founder & President
  • Ryan PengMachine Learning Engineer
  • Eric ZengBackend Engineer
  • Usama KhawarSenior Software Engineer
  • Gregory KlochnykDesigner
  • Nicholas LeeSoftware Engineering Intern
Meet the team

Benefits

Competitive pay and meaningful equity, so you share in what you help build.

Remote
The whole team works remotely, so there's no commute and no office to move for.
Health
Medical, dental and vision insurance, plus mental health resources and a wellness stipend.
Time off
Unlimited time off and paid parental leave.
Equipment
A stipend for your laptop, monitor and anything else you need to do your best work.
Growth
Mentorship, and regular conversations about where you want to grow.
Hack days
Time set aside to explore ideas outside the roadmap.

How we hire

From your application to our decision: four steps, all of them remote.

  1. Apply

    Submit an application when a role opens up.

  2. Meet a founder

    Thirty minutes on video about your work and what you're looking for. Ask us anything.

  3. Work through a real problem

    An hour with the people you'd work with, on a problem we've actually had. No puzzles or trick questions.

  4. Build with us

    One to three days of paid work on a real project, so we both see what working together is like.

Whatever we decide, we'll give you detailed feedback on why.

Open roles

We don't have any open roles right now.

We'd still like to hear from you if the way we work sounds like the way you already do. When a role opens, you'll find it here.

Tell us what you'd build

Send a few lines about the work you're proudest of, with links if you have them, and what you'd want to build here.