Objective. Students will independently complete a documented end-to-end ML pipeline on an unseen dataset, present findings in a 10-minute defense, and respond to evaluator questions.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
This capstone is your opportunity to demonstrate every skill you have built in this course. You will receive a dataset you have never seen before, work through a complete machine learning pipeline on your own, and defend your decisions in front of a panel. The goal is not perfection — it is evidence of sound, professional practice.
Before touching a model, spend real time understanding your data. Compute descriptive statistics, check distributions, identify missing values, and look for outliers. Plot relationships between features and the target variable. Document every observation in your notebook with Markdown cells — a panel evaluator should be able to read your notebook like a lab report and understand your reasoning without asking you a single question.
Common EDA tasks: shape and data types, null counts, class balance for classification targets, correlation heatmaps, and pairplots for small feature sets. Note any data quality issues you find. These notes protect you during the defense because they show you were paying attention, not just running code.
Raw data rarely enters a model as-is. Feature engineering includes encoding categorical variables (one-hot encoding, ordinal encoding), scaling numerical features (StandardScaler, MinMaxScaler), handling missing data (imputation or removal with justification), and creating new features when domain logic supports it. Document every transformation. Your model card must describe each feature used in the final model.
Choose at least two candidate algorithms. Compare a simpler baseline (logistic regression, decision tree) with a more complex approach (random forest, gradient boosting). Justify your choices in writing: why is this algorithm appropriate for the problem type and the data characteristics? Complexity for its own sake is not a virtue — a simpler model that generalizes better is the correct choice.
Use a train/validation/test split or cross-validation. Never tune hyperparameters on the test set. Evaluate on the held-out test set exactly once, after all tuning is complete.
Use grid search, random search, or another systematic method. Document the parameter space you searched and why. Report both training and validation performance across your search to show you monitored for overfitting. scikit-learn's `GridSearchCV` and `RandomizedSearchCV` are standard tools for this step.
Report at least one primary metric appropriate to the task (accuracy is rarely sufficient alone — include precision, recall, F1, or AUC-ROC for classification; RMSE or MAE for regression). Explain why you chose each metric. Discuss at least one failure mode: a pattern the model got wrong, a subgroup where performance dropped, or a data quality issue that limited results. Identifying failure modes is a sign of professional maturity, not weakness.
Complete the model card template provided. A model card is a short structured document that summarizes what a model does, how it was trained, what its performance is, and where it may not be appropriate to use. Model cards are now standard practice in responsible AI development.
Structure your presentation around four areas: (1) problem framing and dataset overview, (2) your methodology and key decisions, (3) metric results with honest interpretation, and (4) at least one failure mode and how you addressed or would address it. Practice to time — ten minutes passes quickly. Speak to the slide, not at it. The panel will ask follow-up questions; answer what you know, and say clearly if you are uncertain rather than guessing.
Within 24 hours of your defense, submit a minimum 200-word reflection. Describe one concrete thing you would do differently with more time. Then map at least two steps from your project to specific exam domains from CompTIA Data+, IBM Data Science Professional, or Google Data Analytics. This reflection is not optional — it is part of your passing score.
Data safety applies even in a classroom setting. Do not share the instructor-curated dataset outside the class or post it publicly, as datasets may contain synthetic representations of sensitive record types. When working with any dataset that resembles personal information (names, IDs, health indicators), apply the same care you would in a professional environment: do not attempt to re-identify individuals, and flag any concerns to your instructor immediately.
Report your results honestly. Inflating a metric by leaking the test set into training, or omitting a poor result, is a form of data misrepresentation. Employers and credentialing bodies treat this as a serious ethics violation. Your rubric rewards accurate reporting, not the highest number.
The 20-point panel rubric covers: data preparation quality (5 points), model selection justification (5 points), metric reporting accuracy (5 points), and clarity of defense communication (5 points). You must score at least 14 out of 20 to pass. Submit your Jupyter notebook and model card at least 48 hours before your scheduled defense.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.
Does the school offer financial aid?
No. We don’t offer financial aid because we’re free. No, really: completely free.
Do you offer industry certification?
No. We are not certified yet, so we can’t offer that to students. What we do offer is knowledge and understanding of a trade.
Enroll first in the trade you’re interested in. You get your key, your program opens, and you begin studying.
Enroll free →