Ambrook

Product Designer

• You'll own product design at Ambrook and build your designs into the product autonomously.
• You're as comfortable prototyping in code and opening a PR as you are in Figma, and you treat coding agents as part of how you work.
• We care about your taste, judgment, and willingness to try things.
• You'll report to Jeff Anders (co-founder and head of design) and collaborate closely with Calvin Ku (product designer), Dan Schlosser (co-founder and head of product), Tiffany Yue (product manager), and Ali Aas (creative director), as well as many other diverse folks across the company.

Mechanical Engineer

• Grow our design system — Build and evolve component libraries, interaction patterns, and design tokens that work seamlessly across web and mobile platforms
• Ship beautiful, functional experiences — Design and build user-facing features from concept to production, translating complex agricultural finance workflows into interfaces that feel natural for ranchers and farmers
• Champion product craft — Establish quality standards and processes that ensure every feature we ship solves real problems elegantly
• Scale our frontend architecture — Contribute to improving design system infrastructure, development workflows, and tooling as we grow
• Collaborate across disciplines — Work with design on visual standards, product on feature requirements, and engineering on technical architecture

Design Engineer – Contract

• Ship beautiful, functional experiences — Design and build user-facing features from concept to production, translating complex agricultural finance workflows into interfaces that feel natural for ranchers and farmers
• Own our design system — Build and evolve component libraries, interaction patterns, and design tokens that work seamlessly across web and mobile platforms
• Champion product craft — Establish quality standards and processes that ensure every feature we ship solves real problems elegantly
• Scale our frontend architecture — Lead improvements to design system infrastructure, development workflows, and tooling as we grow
• Collaborate across disciplines — Work with design on visual standards, product on feature requirements, engineering on technical architecture, and directly with customers on real-world usage
• Shape what we build — Influence product direction through user research insights, design explorations, and deep understanding of agricultural operations

Design Engineer

Analytics Engineer

• Own the entire data layer downstream of production databases — warehouse, dbt models, Airbyte pipelines, orchestration — plus primary company-wide dashboards, data access patterns for AI agents, and an advisory role on data modeling in external systems (e.g., HubSpot) to keep upstream data clean.
• Teach data literacy across the company — how to think about metrics, write better queries, and self-serve in Hex. Best practices for structuring data in the tools teams own. Metrics definitions and consistency so the team asks the right questions of the data.
• Improve the data model. Grow our capacity by resolving gotchas, improving documentation, and building trust. Enable teams to self-serve on reliable data.
• Get deep into Ambrook's business model, product, and customers to understand how we make money and who we serve.
• Trace the full data lineage from product databases through Airbyte into the warehouse to understand the plumbing and where things can break.
• Audit the existing warehouse schema, dbt models, and Hex dashboards; document the known gotchas and tribal knowledge.
• Meet with Growth, Ops, CS, Product, and Engineering to understand their data needs and pain points.
• Own the primary company-wide dashboards — have audited, corrected, and taken accountability for the core dashboards the whole company relies on.
• Begin evolving the data model — started refactoring dbt models to address the highest-priority gotchas and quality issues identified in month one.
• Establish a plan for agent data access — define clean naming conventions, clear data access patterns, and a recommendation on what level of data LLMs should be able to query (raw vs. curated semantic layer.)
• Stood up initial systems that enable teams to self-serve with confidence. The team has processes and tools to unblock themselves with occasional intervention.
• Deliver a significantly improved data model with well-documented models and a meaningfully more trustworthy warehouse.
• Have agent data access operational or in progress with a clean semantic layer or access patterns in place so LLMs can pull data reliably.
• Actively educate the team on data concepts through documentation, 1:1s, and workshops so the team becomes more data-literate and self-sufficient.
• Shape the future of the data function — actively evaluate how AI is changing the data stack and make recommendations on how Ambrook's infrastructure should evolve.

Product Designer

Design Engineer – Contract

Design Engineer

Founding Analytics Engineer