TorchlaneProblem framing
Define the business problem. Show the evidence behind the request, the stakeholders involved, and the decision the system needs to support.
How your work
is assessed.
A completed lesson shows participation. Assessed work shows whether you can apply what you’ve learned.
Seven assessment categories.
Projects use the same published rubric. Passing requires a score of at least 3 out of 4 in every category and no critical failure.
Correctness
Meet the required test thresholds. Meet the project’s test thresholds. Recognize critical cases and explain the errors that remain.
Engineering quality
Document and test the implementation. Make the system reproducible, tested, and understandable. Put calculations and business rules in code.
Security, privacy and compliance
Handle access and data responsibly. Keep secrets out of the repository. Respect the project’s data rules and treat untrusted material as data.
Product and usability
Demonstrate usability. Show that the intended user can do the job. Surface difficult cases instead of hiding them.
Business value
Explain costs and business value. Use the case’s numbers, state your assumptions, and show the cost of operating the system.
Communication
Prepare the project handoff. Make the deck, demo, case study, and runbook accurate, readable, and consistent with the tested system.
Every assessment category must pass.
Strong presentation does not cancel out broken software or unsafe data handling. Each category must meet the standard independently. Distinction begins at a weighted score of 90, with the same passing requirements.
The assessment process.
The assessment process looks at both the delivered system and your understanding of it.
Submit the engagement package.
Provide the running application, repository, test report, demo, client deck, case study, and runbook.
Handle unfamiliar cases.
Project assessment includes a time-limited hidden test using cases you have not seen. The purpose is to check whether your approach generalizes.
Revise against specific criteria.
Review identifies the category and evidence that need improvement. You address those gaps in your next submission.
Defend the capstone.
Answer three reviewer questions in one unedited recording within 72 hours. Explain your code, decisions, tradeoffs, and limitations.
What project
assessment checks.
The assessment asks what your work demonstrates, not just what you have watched.
A learning milestoneTorchlane’s assessment asks
Finished a lessonCan you apply the idea?
Built a demoDoes it handle unfamiliar inputs?
Explained a resultCan you defend the decision?
Submitted a projectCan another person use and maintain it?
Critical failures that prevent a pass.
Examples include exposed secrets, real personal data in a submission, a non-working application, prohibited data sharing, or an inability to explain your own work.
These rules keep the assessment focused on responsible delivery.
Academy credentials and vendor exams.
Torchlane assessment evaluates the program’s applied work. The optional AWS and Google Cloud exams assess their own vendor-defined knowledge.
Neither should be presented as accreditation, a professional license, or a guarantee of employment.
Review the academy program.
Review the training stages, project requirements, and assessment criteria before applying.