> Markdown version of [/jobs/ext/4803544-software-engineer-enterprise-apps](https://www.wearedevelopers.com/jobs/ext/4803544-software-engineer-enterprise-apps). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer - Enterprise Apps - **Company:** Hadrian Automation - **Location:** Bodega Bay, CA, United States - **Salary:** $143,000 - $171,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Spreadsheets, Cyber Security, PostgreSQL, TypeScript, Enterprise Software Applications, ReactJS, Software Application Programming, Backend, Kubernetes, Golang - **Published:** November 20, 2026 - **Apply:** https://www.thejobnetwork.com/job/595ea834-9e36-4abc-ab3a-f1babf91d12f/software-engineer-enterprise-apps ## About the Role * Several years of shipping and running production software, across backend and front end. * Comfortable owning ambiguous problems directly with people who aren't engineers. * Care with information security, access and sensitive data * Strong written and interpersonal communication; specs, reviews, and status updates. Tech we use: + Go, TypeScript, React, Postgres, Kubernetes and AWS with leading-edge AI throughout. ## Description Enterprise Applications builds the internal software Hadrian runs on. We build applications with every department, from Legal and People Operations to Finance, Recruiting and Supply Chain. We also build the company-wide systems the rest of engineering works in; how we write code, how we communicate, and how we leverage AI. If part of Hadrian runs on spreadsheets, email threads or automations that don't fit, it's ours to improve. What You'll Do * Own problems end-to-end; understand the work, design it, build it, ship it and support it. * Build full-stack software on secure cloud infrastructure and connect to the systems the company already runs on. * Keep production healthy: monitoring, on-call, incident follow-ups and clear write-ups * Shape company-wide platforms and patterns that other teams build on; shared code, shared tooling, and paved roads. * Use AI deliberately and intentionally in how you build and what you build. * Be the engineer people trust: clear trade-offs, plain language, steady follow-through. In your first few months: * Ship an application a department uses every day, from first conversation to production. * Take on-call for the services you own and leave each incident better documented than you found it. * Contribute to the company-wide platform change that other engineering teams build on.