Work in your own development environment.
Complete the scoped task locally and submit one committed repository ZIP within the stated window.
How verification works
Technical capability, evaluated with context.
Anzibloom turns role-specific technical work into structured professional evidence. Expectations are visible before commitment, and every passing decision requires authorized human review.
The process
A clear path from expertise to evidence.
- 01
Choose your role
Select the technical discipline or opportunity that best matches your experience.
- 02
Review the standard
See the assessment format, time commitment, rules, and evaluation criteria before starting.
- 03
Demonstrate capability
Complete practical work through a Git take-home or a scheduled live session.
- 04
Receive human review
An authorized reviewer evaluates the work against the published role-family rubric.
The verification standard
What verified means.
Verification communicates a defined role standard and a reviewed outcome. It strengthens hiring evidence without replacing experience, interviews, or an employer's final-fit decision.
- 01
Role relevance
The work reflects realistic responsibilities and decisions for the selected technical discipline.
- 02
Practical evidence
Evaluation considers correctness, reasoning, judgment, communication, and engineering trade-offs.
- 03
Human oversight
Submitting an assessment never creates verification automatically; an authorized reviewer makes the decision.
- 04
Defined validity
A passing role-family credential remains active for 12 months and can support relevant introductions.
Before you begin
Know the format and commitment first.
A focused, scheduled technical session.
When available, meet an evaluator for a 30-minute session assessed against the same role standard.
A reviewed outcome, not an automatic score.
Your account records the decision and next action. A credential is issued only after a passing human review.
Ready to demonstrate your capability?