Kiran

Strengths

• Demonstrated understanding of basic JavaScript string manipulation (concat method).
• Correctly identified the role of a component in front-end frameworks like React/Angular.
• Understood the use of WebSockets/Redis Pub/Sub for real-time updates.
• Correctly identified SDLC as planning, creating, testing, and deploying software systems.
• Understood the concept of GMP compliance for software systems in the Pharma industry.
• Correctly identified a key difference between SQL and NoSQL databases.
• Understood the primary focus of a dashboard for tracking incidents and CAPAs.

Limitations

• Limited understanding of React Hooks (useContext, useState, useEffect).
• Lack of knowledge regarding React.memo for performance optimization.
• Incorrect understanding of how to update state in React components.
• Poor understanding of React Error Boundaries.
• Limited knowledge of React Fragments.
• Misunderstood the difference between React.Component and React.PureComponent.
• Weak grasp of Node.js blocking functions and common server-side frameworks (Express).
• Incorrect understanding of Node.js callback parameters and readable streams.
• Lack of knowledge on isomorphic programming in Node.js and handling HTTPS requests.
• Did not correctly identify standard server events in Node.js.
• Incorrectly identified the best function in `fs` module for reading HTML files in Node.js.
• Poor understanding of SASS partials and CSS display types.
• Incorrectly identified proper CSS dimension attributes.
• Limited knowledge of MongoDB relationships and update operations.
• Incorrect understanding of MongoDB indexing.
• Misidentified the primary use case for Redis in a full-stack application.
• Incorrectly identified the area of web development for Angular/React proficiency.
• Misunderstood the role of an API.
• Incorrectly justified choosing Angular/React over plain JavaScript for a QA Dashboard.
• Misidentified the type of database Oracle is.
• Incorrectly identified key features of C#.
• Misunderstood the implications of being a Subject Matter Expert (SME) on an Incident Board.
• Incorrectly identified the HTTP method for creating new records via REST API.
• Poor understanding of Python's primary characteristics.
• Incorrectly defined an idempotent API endpoint.
• Misidentified the most suitable Redis data structure for a simple message queue.
• Incorrectly identified a common full-stack combination with C# backend.
• Misunderstood the meaning of CAPA in the Pharma industry context.

Strengths

• Demonstrated strong understanding of reporting metrics (Accuracy, F1, ROC-AUC, PR-AUC, Balanced Acc with 95% CIs and McNemar/bootstrap significance).
• Understood the importance of maintaining repo hygiene (clear structure, env, tests, CI with GitHub Actions).
• Correctly identified the need to provide a concise architecture diagram, model card, and decisions write-up.
• Showed ability to clean and version datasets with reproducible scripts.
• Demonstrated understanding of creating leakage-safe, fixed-seed stratified train/val/test splits.
• Understood the process of building sklearn pipelines with justified feature engineering.
• Correctly identified the approach for building pipelines using LR/DT/RF, nested CV, and handling imbalance.
• Showed confidence in beating a baseline accuracy of 90.16% via a fair protocol.
• Demonstrated understanding of shipping a usable app and JSON /predict endpoint.
• Understood the process of deploying on cloud platforms like AWS/Azure.

Limitations

• The candidate's overall score of 35% indicates significant gaps in core Data Science and Machine Learning concepts, despite some individual sections scoring higher.

Strengths

• Demonstrated strong understanding of cleaning and versioning datasets with reproducible scripts.
• Understood the process of creating leakage-safe, fixed-seed stratified train/val/test splits.
• Correctly identified the approach for building pipelines using LR/DT/RF, nested CV, and handling imbalance.
• Showed confidence in beating a baseline accuracy of 90.16% via a fair protocol.
• Demonstrated understanding of shipping a usable app and JSON /predict endpoint.
• Understood the process of deploying on cloud platforms like AWS/Azure.

Limitations

• The candidate's overall score of 33% indicates significant gaps in core Data Science and Machine Learning concepts, despite some individual sections scoring higher.
• The 'Ability to Adapt' section scored 0%, which is a critical weakness for a senior role.
• Lack of understanding in building sklearn pipelines (ColumnTransformer for impute/encode/scale) with justified feature engineering.
• Did not provide any reasons for 'NO' answers in the essay section, indicating a lack of thoroughness or engagement with the assessment instructions.

Strengths

• Correctly identified the role of a component in front-end frameworks like React/Angular.
• Demonstrated proficiency with data visualization libraries (D3.js, Chart.js, Highcharts).
• Understood the use of WebSockets/Redis Pub/Sub for real-time updates.
• Correctly identified SDLC as planning, creating, testing, and deploying software systems.
• Understood the concept of GMP compliance for software systems in the Pharma industry.
• Correctly identified a key difference between SQL and NoSQL databases.
• Understood the primary focus of a dashboard for tracking incidents and CAPAs.