OXMAN OXMAN is a nature-based research and design company based in Manhattan. We incubate ventures and technologies that reimagine the relationship between humanity and the natural world. Working across disciplines—from architecture and ecology to computation and materials science—we develop nature-centric solutions to critical environmental challenges. EDEN Existing environmental tools are trapped between two limits: remote sensing observes what is already on the ground, while traditional simulations only evaluate fixed plans someone has already drawn. EDEN bridges both. We are building a generative ecosystem digital twin that works from target outcomes, such as carbon sequestration, stormwater retention, microclimate cooling and biodiversity, to discover the optimal earthworks, planting and management sequence that achieves them. Operating at the interface of representation learning, physics-grounded world models and autonomous optimization, EDEN maps satellite and geospatial data into a shared language of species functional traits and physical site fields (topography, light, moisture, wind, thermal, soil). Coupled physical solvers and fast learned surrogates simulate how these ecosystems develop over multi-year horizons, while a hybrid decision engine, combining AI agents with mathematical optimization, searches over procedural graphs to discover interventions whose outcomes can be predicted and validated. EDEN’s technical work spans three teams: one that builds the platform, one that develops and validates the scientific modules, and one that combines those modules into applications. Our core components and first applications work today as research prototypes. As we engineer them into one cohesive system that turns ecosystem restoration and design into an engineering discipline with predictable, verifiable outcomes, we are seeking a System Architect to own the technical architecture across all three teams. Role Overview OXMAN is seeking a System Architect to join the EDEN team as its first System Architect, owning the technical architecture across EDEN’s platform, science and applications teams. This role sits at the intersection of systems engineering, scientific computing and applied AI. The System Architect will design and build the system that composes EDEN’s models, runs closed-loop simulation and optimization at scale, makes sure their results can be trusted, and delivers them to users through a single interface. The role is hands-on: the System Architect builds the first versions of the critical pieces themselves and makes the foundational decisions that are expensive to change later. Few systems have to combine geospatial representation learning, physical simulation, mathematical optimization and AI agents while also producing results that hold up in the physical world. When models of microclimate, hydrology and ecological succession are chained over multi-year horizons, small errors can compound, and naive optimizers will happily exploit flaws in a learned surrogate rather than find designs that work in the field. The ideal candidate cares as much about whether a system’s outputs can be trusted as whether it runs, and understands that the architecture, search harness and validation guardrails they design will decide whether EDEN can grow from one validated application to many. Key Responsibilities • Define the core abstractions: Establish the shared schema of traits, physical fields and world states that every module reads and writes, a common contract for operators and evaluators, and the representation of EDEN’s procedural graphs. These graphs are design processes our teams author from real projects, which AI agents adapt to new sites, the decision engine searches and users inspect; their control nodes hold the executable programs that agents write and optimizers tune. • Architect the search, optimization and agentic control loop: EDEN’s decision engine pairs AI agents that adapt graphs and write design programs with numerical optimizers. Design the harness that translates user intent into formal problem bounds, with guardrails that keep agent and optimizer output within expert-validated physical and ecological limits, while orchestrating parallel search, inner-loop tuning, evaluation budgets and diagnostic feedback. • Design and build the runtime: Orchestrate physical simulation, learned surrogate models and long-running optimization at scale, with deterministic execution, content-aware caching, sandboxed code execution and deliberate trade-offs between fidelity and speed. • Unify the prototypes: Bring today’s components and applications, built across different research and design environments, onto a portable, scalable foundation so new scientific modules and application verticals plug in cleanly without custom glue. • Make validation part of the architecture: Ensure every model carries provenance, calibrated uncertainty and a documented range of conditions in which it holds. Make determinism, out-of-sample testing and physics-grounded checks on optimized designs platform features rather than one-off scripts. • Design the data and delivery platform: Structure geospatial and ecological data ingestion, versioned site and run state, and the backend services and APIs that power EDEN’s interactive web interface and external design-tool integrations. • Set engineering practice: Establish testing, reproducibility, CI and a clear line between research code and production code. Key Goals & Outcomes • First 90 Days: • Map the existing components and applications, documenting what each one does, what it depends on and how it runs end-to-end. • Write the architecture specification and implement the first versions of the shared data contracts and procedural graph runtime, reviewing them with the science and application teams. • Unify the search and evaluation harness so agentic search, numerical optimization and simulation run through a single, cached lifecycle. • Take one applicatio