Features
Built for Modern Engineering Auditing.
Every feature is crafted to isolate and highlight your actual engineering problem-solving style.
Gemini Code Interrogator
Runs architectural cross-examinations on why specific design choices were selected over standard alternatives.
Gemini Chaos Challenge
Simulates edge-case stress anomalies — race conditions, sudden load changes — matching your exact code structure.
Gemini Bug Injection
Identifies high-traffic execution logic paths and injects real-world bugs to evaluate your diagnostic approach.
Reasoning Report
Tracks your debugging strategy to create a concise summary detailing your raw developer proficiency.
Verified Understanding Badge
Immutable, public-facing link showcasing solution metrics. Badge state updates with depth of challenges completed.
Recruiter-Ready Scorecard
A 30-second view of architecture grasp, debugging velocity, and conceptual articulation — built for hiring teams.
Why Google Gemini Drives the Engine.
Standard LLMs fail at processing whole applications; ProofWork AI requires next-generation context windows and reasoning.
Gemini 1.5 Pro reads all project files, dependencies, and README text simultaneously — full contextual awareness with no detail loss.
Reviews architectural diagrams, database schemas, and code as a unified ecosystem rather than isolated files.
Acts as an unbiased automated engineering lead, scoring debugging choices against true production standards.
↑ truncated · lost dependencies · partial view
↑ parallel · whole-repo · single coherent reasoning pass
Frequently asked
- What exactly is in a ProofWork report?
- An architecture summary, a reasoning trace covering key design decisions, a fault-injection challenge log (where Gemini probes the author with adversarial scenarios), a final attested score, and an embeddable badge that links back to the public report.
- How does the fault-injection challenge log work?
- Gemini generates targeted 'what if' questions about your repo — failure modes, scaling cliffs, security edge cases — and records how each one was reasoned about. The log shows reviewers which scenarios the author can defend on the spot.
- Why does Gemini's long context window matter for code review?
- Most code-review tools chunk a repo into small windows and lose cross-file context. Gemini reasons over the whole codebase in a single pass, so questions about architecture, module boundaries, and end-to-end flows stay grounded in the actual code.
- Can I embed the badge on my own site or résumé?
- Yes. Every report ships with an embeddable badge (HTML snippet plus image) that links back to the public report. Recruiters click through to the full reasoning trace from any portfolio site, LinkedIn, or PDF résumé.
- Does the report update if my repo changes?
- Each report is pinned to a specific commit so the reasoning trace stays verifiable. Re-running the pipeline on a newer commit produces a new report; the old one remains valid for its commit.