O3 World Wide · 03/2026 - Present
Shipyard Operations Software
Software Engineer
Make a disrupted production plan actionable.
Built and deployed a planning application around installation dependencies, parts, personnel, and shared resources. Planners can trace what a disruption affects and evaluate schedules against the constraints of the work.
ImplementationReact · TypeScript · Rust · Python · FastAPI · PostgreSQL · OR-Tools CP-SAT · Docker
- Operational result
- O3 and its defense-industry partners began using the planning model as a framework for organizing upcoming shipyards and distributed shipbuilding.
- Relevant to Hadrian’s FDE role
- Customer discovery, full-stack implementation, operational data models, and iteration based on planner feedback.
- Understand the operating model
- An installation requires parts to be available, workers and shared resources to be assigned, and prerequisite work to be complete. I represented those relationships in a shared ontology so scheduling could account for more than calendar dates.
- Build the application with AI assistance
- Used agentic coding tools to implement a React/TypeScript interface and Rust/Python services backed by PostgreSQL. I owned requirements, scheduling logic, historical-replay validation, and deployment.
- Respond to changing requirements
- When planners needed late deliveries and unavailable equipment reflected in schedules, I extended the dependency model and scheduler to propagate the consequences through affected work.
- Validate and deliver
- Replayed historical schedule delays to validate revised behavior before release. Docker packaging, role-based access, event history, and audit records supported deployment and review.