> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/culture/who-we-hire.md). # Who we hire Who we look for in product and engineering. **We look for people who want to build something and who** [**understand our users and the business**](/product/who-we-build-for.md)**, because every person we hire shapes what UMH builds.** Product and engineering are nine people. Every engineer at UMH is a [Product Engineer](/engineering/product-engineer.md) and decides what to build. The [Product Manager](/product/product-manager.md) gives them the context for it and does not decide for them. We hire for [learning ability, not credentials](/company/why-we-exist.md). What counts is something you built that others actually use. That can be an open-source project, a feature you pushed for at a previous company, or anything else. We hire for where someone is going, not where they are. Because you will work directly with our users and customers, you should be someone who excites them. So we look for people the team is excited to work with. ## What you bring **You bring something an LLM does not have.** LLMs now do much of the work of turning a well-defined ticket into code. They are not good yet at deciding what to build or at writing the ticket. We are experimenting with LLMs that read our product telemetry in PostHog and suggest work. Even then, a person first has to tell them what success looks like for a customer or a feature and agree on it with the rest of the team. * You might know how databases, networks or operating systems work, or how machines share their data through protocols such as OPC UA. * You might have worked in professional software development, run software in production, or worked in a factory. * You might be good with people and want to work with our users and customers. Deep expertise in one area, for example Kubernetes or design systems, is a plus. For a Product Manager, coding is a plus. With LLMs, a Product Manager who can code can build a prototype or look into the telemetry themselves. Our engineering standards are still high. They are on [How to build](/engineering/development-process/how-to-build.md), [Coding standards](/engineering/development-process/how-to-build/coding-standards.md) and [Testing](/engineering/development-process/how-to-build/testing.md). If you don't match everything on this page, but you bring something else, [apply anyway](https://www.umh.app/careers). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://engineering.umh.app/culture/who-we-hire.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.