Yash Sharma

Create your portfolio with ProoV
ProoV
DE Verified work portfolio

ProoV Portfolio

Yash Sharma

computer science · Amity University Madhya Pradesh

View the ProoV leaderboard

Projects

Certified

Self-directed project

Business Analytics Sprint

Data Science · September 2026

84/ 100

A ProoV case study · educational project, not employment

Built an end-to-end profitability investigation that framed the paradox structurally, audited the data for issues, and used SQL to isolate margin differences by category and region. Connected the analysis to a Pareto-style root-cause story, a recovery forecast, and a prioritised executive recommendation set focused on discount discipline, logistics efficiency, and input-cost mitigation.

Graded against

  • Problem Framing & Hypotheses10%
  • Data Analysis & SQL30%
  • Root-Cause & Forecasting25%
  • Dashboard & Visualization15%
  • Executive Communication & Strategy20%

Passed · pass mark 60/100

What stood out6
  • Built a sensible hypothesis set around raw-material inflation, discounting, and logistics rather than guessing a single cause
  • Wrote the category margin query with the correct margin formula and grouped by category as required
  • Used a join to connect regional margin with discount data and interpreted Asia as a margin-pressure area
  • Produced a forecast and recommendation stack that ties actions back to the identified profit drivers
  • Structural Problem Framing
  • Leakage-Free Analytical Reasoning
The work I submitted20 tasks

12 tasks · 9.0k characters · 8 written answers · 269 words

  • Hypothesis Sheet535 characters
  • Data Audit100 characters
  • Week1 Update689 characters
  • Sql Category Profit338 characters
  • Sql Region Join331 characters
  • Dashboard58 characters
  • Forecast281 characters
  • AI Reflection426 characters
  • Recommendations1.2k characters
  • Stakeholder Qa1.1k characters
  • Executive Summary1.3k characters
  • Bosch Real Case Study2.6k characters
  • Hypothesis Sheet53 words
  • Data Audit4 words
  • Week1 Update93 words
  • Sql Category Profit26 words
  • Sql Region Join28 words
  • Dashboard1 word
  • Forecast6 words
  • AI Reflection58 words

Summarised on purpose — the submitted code and writing stay private so this page cannot be reused as an answer key. The full submission sits behind the verified certificate.

Verified certificateTamper-proof · issued by ProoV
Certified

Self-directed project

AI-Assisted Code Modernization with IBM

Junior Software Engineer · Software Engineering · September 2026

84/ 100

Based on a public IBM case study · not affiliated with IBM

Built and verified a legacy Python maintenance service modernization: fixed the wear-calculation bug with true division, handled missing service readings safely, corrected fleet-report averaging, and repaired a hidden mileage-conversion helper bug. They also added the missing report test, documented what the AI agent got wrong, and used an acceptance script to confirm the repo met the required behavior.

Graded against

  • Fix and extend the repo with the agent35%
  • Diagnose the bug20%
  • Direct and audit the AI agent25%
  • Explain it like an engineer20%

Passed · pass mark 60/100

What stood out6
  • Correctly identified the floor-division bug and explained why it suppressed nearly-worn cars
  • Caught the quiet helper-module mileage conversion bug that no test directly covered
  • Wrote NOTES.md in their own words and tied it to verification checks
  • Leakage-Free Bug Diagnosis
  • Directed AI Code Review
  • Acceptance-Driven Verification
The work I submitted17 tasks

9 tasks · 1.6k characters · 8 written answers · 141 words

  • Division Predict70 characters
  • Diagnose Line130 characters
  • Diagnose Why170 characters
  • Scope Prompt66 characters
  • Audit Findings149 characters
  • Template Repo Click82 characters
  • Verify Report71 characters
  • Exec Pitch767 characters
  • Repo URL46 characters
  • Division Predict1 word
  • Diagnose Line10 words
  • Diagnose Why24 words
  • Scope Prompt1 word
  • Audit Findings1 word
  • Template Repo Click1 word
  • Verify Report1 word
  • Exec Pitch102 words

Summarised on purpose — the submitted code and writing stay private so this page cannot be reused as an answer key. The full submission sits behind the verified certificate.

Verified certificateTamper-proof · issued by ProoV
Certified

Self-directed project

Frontend Engineering with Prediction Game

Junior Front-End Engineer · Software Engineering · September 2026

92/ 100

A ProoV case study · educational project, not employment

Built a single-file World Cup prediction game end to end: rendered fixtures as pickable match cards, scored picks with the exact 5/2/0 rule, generated bot predictions from a real-results strength model, and persisted a ranked leaderboard in localStorage. Also shipped the project to a live HTTPS Netlify URL for browser-based play.

Graded against

  • Scoring engine correctness30%
  • Prediction model genuinely from real data25%
  • Game completeness and leaderboard soundness25%
  • Shipped and shareable: live deployed URL20%

Passed · pass mark 60/100

What stood out6
  • Implemented scorePick with the exact 5/2/0 rule and verified all four canonical cases, including draw-vs-draw handling.
  • Computed team strengths from real results data and used both teams’ attack/defense values in botPredict rather than a stub or constant.
  • Built a persistent leaderboard that saves to localStorage, sorts descending, and re-renders ranked rows after reload.
  • Leakage-Free Feature Engineering
  • Honest Model Evaluation
  • State Persistence and Ranking
The work I submitted19 tasks

11 tasks · 13 lines · JavaScript, HTML · 8 written answers · 747 words

  • Lab Orientation673 characters
  • Act1 Fixtures FormJavaScript · 3.3k characters
  • Example Score PickJavaScript · 2.0k characters
  • Act2 Scoring FunctionJavaScript · 2.4k characters
  • Act3 Compute Strength108 characters
  • Example Bot PredictJavaScript · 1.6k characters
  • Act3 House Bot108 characters
  • Example Save Rank ReadonlyHTML · 3.5k characters
  • Act5 Assemble2 lines
  • Act4 LeaderboardJavaScript · 2 lines
  • Final Submission94 characters
  • Lab Orientation66 words
  • Act1 Fixtures Form143 words
  • Example Score Pick121 words
  • Act2 Scoring Function126 words
  • Act3 Compute Strength1 word
  • Example Bot Predict159 words
  • Act3 House Bot1 word
  • Example Save Rank Readonly130 words

Summarised on purpose — the submitted code and writing stay private so this page cannot be reused as an answer key. The full submission sits behind the verified certificate.

Verified certificateTamper-proof · issued by ProoV
Certified

Self-directed project

Fundamentals of Cybersecurity

Cybersecurity · September 2026

84/ 100

A ProoV case study · educational project, not employment

Built an end-to-end incident response workflow for a phishing-led breach: triaged the initial email, traced the attacker through auth logs and IOCs, mapped the activity to the cyber kill chain, and chose a sound containment sequence. Also produced a concise GDPR Article 33 notification and an executive incident report grounded in the incident’s actual timeline and impact.

Graded against

  • Threat Triage & Detection20%
  • Log Analysis & Investigation30%
  • Incident Response & Containment20%
  • Compliance & Breach Notification15%
  • Executive Communication & Lessons15%

Passed · pass mark 60/100

What stood out6
  • Correctly caught the impossible-travel login and isolated the anomalous row without false positives
  • Selected the right containment order by cutting access first and avoiding destructive actions
  • Drafted a GDPR breach notice that covered nature, scope, consequences, and mitigations
  • Connected the real-case recommendation to lateral movement and large-scale exfiltration
  • Leakage-Free Incident Triage
  • Evidence-Based Log Investigation
The work I submitted17 tasks

9 tasks · 4.3k characters · 8 written answers · 267 words

  • Phishing Triage189 characters
  • Killchain Map244 characters
  • Log Triage170 characters
  • Ioc Extraction176 characters
  • Containment Plan373 characters
  • Breach Notification676 characters
  • Incident Report1.2k characters
  • Recommendations648 characters
  • Real Case Analysis642 characters
  • Phishing Triage8 words
  • Killchain Map12 words
  • Log Triage9 words
  • Ioc Extraction8 words
  • Containment Plan14 words
  • Breach Notification72 words
  • Incident Report131 words
  • Recommendations13 words

Summarised on purpose — the submitted code and writing stay private so this page cannot be reused as an answer key. The full submission sits behind the verified certificate.

Verified certificateTamper-proof · issued by ProoV
4Projects completed
4Verified certificates
86Average score
Create your portfolio with ProoV
Yash Sharma — Portfolio | ProoV