On-Site Build Test Criteria

Civilization Design/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 day and are embedded into an active crew with real production goals.

Performance is observed in real time.

What We Are Looking For

1. System Comprehension

Can the candidate:

• Work effectively as part of the team
• Understand and follow build instructions
• Ask the right clarifying questions
• Navigate the workflow without hand-holding while being helpful in the process

Collaboration skill is more important than prior experience.

2. Execution Under Constraint

Can the candidate:

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

We value correctness and speed at the same time.

3. Learning Velocity

Can the candidate:

• Absorb new tools and methods quickly
• Improve visibly over task completion
• Integrate feedback immediately
• Self-correct by asking questions and observing other people

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 or 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
• Basic documentation after the work day: photos (preferably link to Google Photos or other sharing site) especially ones that show result and measurement such as tape measure placed next to finished work to show accuracy.

Outcome

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

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