Destaca-te nesta função — gera um currículo e uma carta de apresentação personalizados em cerca de um minuto.
Moat is seeking a hands-on staff engineer in Lehi, Utah, to own substantial product work from first customer conversation through release and iteration. You will build across the stack with Go, Flutter, Postgres, and GCP, collaborating with product and design while shaping architecture for growth.
You’ll ensure customer experience and robust underlying systems. The role emphasizes ownership, mentorship, and setting technical direction across related features as the team scales.
Moat is headquartered in Lehi, Utah. We are building the system of record for the built
environment, giving facilities teams complete visibility into the critical assets their buildings
depend on. Our patent-pending AI engine turns the O&M manuals and construction submittals behind
every building into a living maintenance system, so teams can catch problems before something
breaks.
Investor-backed and growing, Moat already manages more than 50,000 assets across over 20 million
square feet for organizations ranging from K-12 school districts to national property portfolios. We're a
small team going after a massive, underserved industry, and everyone here has real ownership from
day one.
We're looking for a hands-on staff engineer to own substantial product work from the first customer
conversation through release and iteration. You'll build across the stack, work closely with product and
design, and help the team make architectural decisions as the product grows. This role needs
someone who cares about both the customer experience and the systems underneath it.
Our stack is Go, Flutter, Postgres, and GCP. Experience with a variety of languages and tools is
strongly valued; experience with our exact stack is not required.We favor straightforward code, frequent small releases, and tests that reflect real behavior. You'll have a direct hand in what we build and how it works for customers.
We actively adopt new development tools and use LLMs heavily in coding. Engineers own every
change they ship, though: you're expected to read and understand the code, verify its behavior, and be able to explain and maintain it, including code generated by LLMs.