> 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/umh-engineering-handbook.md). # UMH Engineering Handbook How the engineering team at UMH works. **If you don't know UMH yet**, start with [Why we exist](/company/why-we-exist.md): we want data to become what electricity already is, infrastructure every factory is built on. We keep the handbook public so you can see how we work, and hopefully get excited about our company, our product and the engineering behind it, before you apply. **If you are just getting started at UMH**, welcome! Start with [Your first months](/career/your-first-months.md). We do many things differently from the rest of the industry, for example [opinionated simplicity](/product/product-standards/opinionated-simplicity.md). That can take some time getting used to. When you face a trade-off, the handbook gives you the background to decide closest to our company vision, our existing engineering standards and where we want to move to. **If you are a product engineer**, use the handbook as a reference when you make a decision. --- # 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/umh-engineering-handbook.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.