On-Site Build Test Criteria

From Open Source Ecology
Revision as of 03:09, 21 January 2026 by Marcin (talk | contribs) (Created page with "= Civilization Engineering Track: On-Site Build Interview = == Purpose == The on-site build interview replaces conventional hiring screens with direct observation of how a candidate operates inside an expertise-embedded production system. We are not testing trade mastery. We are testing whether a person can function as a civilization-scale builder inside structured, open, collaborative systems. == Format == Candidates join a live build for 1–3 days and are embedded...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Civilization Engineering Track: On-Site Build Interview

Purpose

The on-site build interview replaces conventional hiring screens with direct observation of how a candidate operates inside an expertise-embedded production system.

We are not testing trade mastery. We are testing whether a person can function as a civilization-scale builder inside structured, open, collaborative systems.

Format

Candidates join a live build for 1–3 days and are embedded into an active crew with real production goals.

They receive:

  • Canonical CAD and drawings
  • Bill of Materials (BOM)
  • Build instructions and acceptance criteria
  • A facilitator, not a supervisor

Performance is observed in real time.

What We Are Looking For

1. System Comprehension

Can the candidate:

  • Read drawings and extract intent
  • Understand interfaces and tolerances
  • Ask the right clarifying questions
  • Navigate CAD → BOM → Build flow without hand-holding

This is more important than prior trade experience.

2. Execution Under Constraint

Can the candidate:

  • Build accurately from documentation
  • Follow acceptance criteria precisely
  • Work within time, material, and safety constraints
  • Correct errors without defensiveness

We value correctness over speed.

3. Learning Velocity

Can the candidate:

  • Absorb new tools and methods quickly
  • Improve visibly over hours or days
  • Integrate feedback immediately
  • Self-correct by referencing documentation

Rapid learning matters more than initial skill.

4. Documentation Discipline

Can the candidate:

  • Take photos and log work
  • Update build notes or mark documentation gaps
  • Treat documentation as part of the build, not an afterthought

Civilization engineering requires executable documentation.

5. Collaborative Literacy

Can the candidate:

  • Coordinate with others without ego
  • Respect interfaces and shared standards
  • Ask for help early
  • Help others without derailing their own task

We are building systems, not heroes.

6. Tool and Safety Maturity

Can the candidate:

  • Use tools responsibly
  • Maintain situational awareness
  • Protect people, equipment, and schedule
  • Stop work when something is unclear or unsafe

Judgment is more important than bravado.

What We Explicitly Do NOT Optimize For

  • Certifications or credentials
  • Years of experience
  • Trade purity
  • Charisma or self-promotion
  • Speed without correctness

Pass Criteria

A candidate passes the build interview if they demonstrate:

  • Reliable execution inside structured systems
  • High learning velocity
  • Respect for standards and interfaces
  • Clear potential to scale impact beyond individual labor

Outcome

Successful candidates are invited into the Civilization Engineering Track, where:

  • Expertise lives in systems
  • Individuals amplify, not bottleneck, production
  • Civilization-scale build capacity is the objective