3D Animator/Rigger (Contract - Project Based)

The final production handoff must include:

Master Assets

• Rigged master Blender file

• High-quality master model

• Optimized real-time model

• Approved lower-detail version if required

• Blue, green, and red material presets

• Complete UVs and texture-source files

• Shape keys or blend shapes

• Facial-expression controls

• Speech or viseme controls

• Feather and secondary-motion controls

Animation Assets

• Approved core animation library

• Separate, clearly named animation clips

• Facial-expression presets

• Pose library

• Transition animations

• Real-time optimized animation data

• Animation manifest listing each clip and its intended use

Export Assets

• GLB/glTF

• FBX

• Source texture files

• Transparent-background animation previews

• Still turntable renders

• Rig demonstration video

• Color-preset demonstration

• Test files showing animations running in the target environment

Documentation

• Rig-control guide

• Material and color-editing guide

• Animation naming guide

• GLB export instructions

• Instructions for creating new animations

• Instructions for adding accessories

• Instructions for adding new color variations

• List of dependencies and known limitations

All project source files and custom scripts created specifically for the project must be included in the handoff.

The completed asset must demonstrate:

• Clean topology

• Reliable deformation

• No broken or disconnected geometry

• No visible wing or feather clipping during approved animations

• No foot sliding during grounded movement

• Clean eye and eyelid movement

• Correct wing folding

• Stable feather behavior

• Consistent animation naming

• Clean animation curves

• Predictable animation transitions

• Organized files and collections

• No unexplained dependencies

• Successful GLB playback in the actual target environment

The rig should be intuitive enough that a qualified animator can use it without reverse-engineering the setup.

The following should be finalized collaboratively based on the candidate’s technical approach and our implementation needs:

• Final polygon budgets

• Number and complexity of model LODs

• Bone count and real-time performance limits

• Bone-based versus geometry-based feather system

• Shape keys versus joint-based facial animation

• Exact viseme set and lip-sync workflow

• Level of individual feather control

• Physics-driven versus baked secondary motion

• Exact launch animation list

• Animation clip count by project phase

• Animation frame rate

• Root motion versus in-place movement

• Runtime material-switching method

• Accessory attachment system

• Three.js and React Three Fiber integration approach

• Mobile performance targets

• File-size targets

• Review schedule and animation approval batches

The candidate should explain the tradeoffs behind their recommended approach rather than simply selecting the most complex solution.

A strong candidate may improve the project by proposing:

• A simplified animator-facing control panel

• A developer-facing control API

• Procedural eye tracking

• Procedural blinking

• Runtime gaze targeting

• Emotion-intensity controls

• Animation state-machine recommendations

• A reusable accessory socket system

• A lightweight mobile model

• Automated color-variant generation

• Automated GLB export tools

• Animation compression recommendations

• A browser-based character test environment

• Reusable animation layers

• Better methods for managing feather performance

• A scalable system for future owl personalities

• Integration documentation for developers

• A practical roadmap for expanding the animation library

These are not substitutes for the required deliverables. They are opportunities for the candidate to demonstrate technical leadership and improve long-term scalability.

Applicants should provide:

• Character-modeling portfolio

• Rigging reel

• Facial-rig examples

• Creature, bird, or winged-character examples

• Real-time character examples

• GLB/glTF export examples

• Animation reel

• Rig-control demonstration

• Proposed production software

• Recommended technical approach

• Proposed milestones

• Cost by project phase

• Revision policy

• Testing and quality-assurance process

• Any risks or recommended changes to this scope

Applicants must identify which portions of the work they will complete personally and whether any parts will be subcontracted.

Phase 1: Model and Technical Direction

• Character translation

• Turnaround approval

• Production model

• Topology and UVs

• Initial materials

• Technical pipeline confirmation

Phase 2: Rig and Character Controls

• Complete body rig

• Face and eye rig

• Wing and feather controls

• Expression system

• Color preset system

• Initial GLB export test

Phase 3: Core Animation Library

• Idle states

• Communication gestures

• Product-analysis states

• Score reactions

• Essential emotional reactions

• Basic movement and flight

• Transitions

Phase 4: Optimization and Handoff

• Real-time optimization

• Final GLB testing

• Animation naming and cleanup

• Documentation

• Source files

• Developer handoff

• Final quality assurance

The project is complete when WISEcode receives one fully editable master owl system that:

• Faithfully matches the supplied owl design

• Supports the blue, green, and red character variations

• Provides complete control over the face, eyes, eyelids, beak, head, body, wings, major feathers, tail, legs, feet, and ear tufts

• Supports expressive facial and body animation

• Includes the approved core animation library

• Transitions cleanly between product states

• Exports to a functional, optimized GLB

• Can be placed into any transparent or custom environment

• Can be controlled by developers inside an interactive experience

• Can be expanded without rebuilding the model or rig

• Includes complete source files and usable documentation

• Has been tested in the actual target environment