INTERNSHIP–II (BT-307 / BT-407)  Application Level

• VIRTURL - Kamini Sawasiya

• virtual intern - Ritik Vishwakarma

• veman internship certificate - Vk Jhan

• veman - Vk Jhan.

• Vashu Raja

• Sumit Yadav

• SANJANA SAHU.

• Krishna Kushwah.

• Prince Kumar.

• Pranit Singh.

• Aparna Tiwari

• - Aaliya Khan

• - Tripti Mandal

• PRANIT CERTIFICATE - Pranit Singh

• Sneha Mandal

• Picsart_25-12-29_23-35-04-295 - Prasanjit Mondal.

• Personal - Pranav Choudhary

• Paras Sawant 526381 - Paras Sawant

• Nitin_internship_PPT - Nitin Verma

• Nikita certificates - Nikita Bari

• Nikhil Dehariya

• NIDHI DUBEY

• KHUSHEE LOKHANDE 

• Kamini Sawasiya

• internship ppt & certificate - Anish Kumar

• Palak Mehra

• Amir Hamja

• Sapna Pachlaniya

• Anshika Purohit.jpg

• iMUSKAN BADSHAH

• Sanvi Sahu

• final ppt - Khushi Kumari.

• final Merged - POOJA SONI

• Certificate - Chiranjeevi

• Aryan Raj

• Anish Kumar.

• Akshat Parate AI-ML Internship Certificate - Akshat Parate

• AI-ML Internship Certificate and Report - Akshat Parate

• AD certificate - SAKET MISHRA.

• Abhishek Rajpoot

• Shubham Rajput.

(100 Marks | 3 Credits)

CO1 : Apply engineering knowledge and modern IT tools to analyze and develop software-based solutions for industry problems       with consideration for sustainability and societal impact.

Bloom's Level: K3/K4  

PO Mapping: PO1, PO2, PO3, PO5, PO6

CO2 : Conduct investigations using software tools, data analysis, and modeling techniques to validate solutions and draw               substantiated conclusions.

Bloom's Level: K4  

PO Mapping: PO2, PO4, PO5, PO11

CO3: Function effectively in teams and communicate technical concepts through comprehensive documentation and     presentations.

    Bloom's Level:K3       

   PO Mapping: PO8, PO9, PO10

CO4: Demonstrate professional ethics, project management capabilities, and commitment to lifelong learning in software engineering context.

Bloom's Level:K3       

PO Mapping: PO7, PO10, PO11

Application
Skill development
Guided problem-solving

Level: Application / Analysis
Focus: AI-DS tools, problem solving, investigation

CO1 – Application of AI & DS Tools

1. Explain the problem statement you worked on.

2. Which AI/Data Science techniques were applied in your project?

3. Why did you choose Python for this work?

4. What datasets were used and why?

5. How did you preprocess the data?

CO2 – Investigation & Analysis

6. What exploratory data analysis techniques did you apply?

7. How did you handle missing values or outliers?

8. What evaluation metrics did you use and why?

9. What were the key insights obtained from the analysis?

10. How did you validate your results?

CO3 – Teamwork & Communication

11. What role did you play in the project team?

12. How did you communicate your results to others?

13. What challenges did you face while working in a team?

14. How would you explain your project to a non-technical person?

CO4 – Ethics, Management & Learning

15. What ethical issues are involved in data analysis?

16. How did you manage your time during the internship?

17. What new tools or skills did you learn?

18. How does sustainability relate to AI projects?

19. How is industry problem solving different from academic problems?

20. How did this internship improve your confidence as an AI & DS student?

Internship-II (BT-307/BT-407) rubric. These are designed to align with the evaluation criteria and help assess the student's depth of understanding, application, and communication skills.

1. Tools & Technologies

1. Q: Which software tools and technologies did you primarily use during your internship? 

A: I primarily used [e.g., Python with Django framework, React.js for frontend, PostgreSQL database, and Docker for containerization]. These were chosen based on the project's requirements for scalability and rapid development.

2. Q: Why did you select these specific tools over others? 

A: I selected them because [e.g., Django provides built-in security features and admin panel, reducing development time; React offers component-based architecture for reusable UI]. Alternatives like Flask were lighter but lacked the structure needed for our team size.

3. Q: What are the key capabilities of one of the main tools you used? 

A: For example, Docker allows containerization, ensuring consistent environments across development, testing, and production, with features like image layering for efficient storage.

4. Q: What are some limitations of the tools you used? 

A: One limitation of [e.g., React] is its steep learning curve for state management; we mitigated this by using Redux. Docker can increase resource overhead on local machines.

5. Q: How did the tool's features help in solving the industry problem? 

A: The tool's [e.g., PostgreSQL's ACID compliance] ensured data integrity in our transaction-heavy application, critical for the client's financial module.

6. Q: Did you learn any new tool during the internship? How? 

A: Yes, I learned [e.g., Kubernetes] through official documentation, online courses, and hands-on practice in the company's cluster.

7. Q: Compare two similar tools you considered. 

A: [e.g., PostgreSQL vs MySQL]: PostgreSQL supports advanced data types and JSON better, making it suitable for our complex queries, while MySQL is faster for simple read-heavy operations.

8. Q: How does the tool support modern development practices? 

A: Tools like Git integrated with [e.g., GitHub Actions] enabled CI/CD pipelines, automating testing and deployment.

9. Q: Were there any compatibility issues with the tools? How resolved? 

A: Yes, version conflicts between Node.js packages; resolved using package-lock.json and npm audit.

10. Q: How would you justify the cost-effectiveness of these tools? 

A: Most were open-source (e.g., Python, PostgreSQL), reducing licensing costs while providing enterprise-grade features.

2. Methodology & Implementation 

1. Q: Describe the overall methodology you followed for the project. 

A: I followed Agile methodology with Scrum framework—daily stand-ups, 2-week sprints, backlog refinement, and retrospectives.

2. Q: What design considerations did you keep in mind? 

A: Considerations included modularity, scalability, security (e.g., OWASP guidelines), and user experience.

3. Q: Explain the key algorithms or code structure you implemented. 

A: I used [e.g., Dijkstra's algorithm for shortest path in a routing module], with a modular MVC architecture separating concerns.

4. Q: How did you ensure sustainability in your implementation? 

A: By optimizing code for lower computational resources, using energy-efficient cloud instances, and implementing serverless functions where possible.

5. Q: What societal impact did your project consider? 

A: The application [e.g., promotes financial inclusion by providing accessible banking to rural users], with features like multilingual support.

6. Q: Walk through your problem-solving approach for a major challenge. 

A: For [e.g., performance bottleneck], I profiled code, identified slow queries, added indexing, and implemented caching with Redis.

7. Q: How did you handle requirements changes during implementation? 

A: Through change request process in Agile—updated backlog, re-prioritized, and communicated impact to stakeholders.

8. Q: Describe your testing strategy in implementation. 

A: Unit testing with pytest, integration testing, and end-to-end with Selenium; achieved 85% code coverage.

9. Q: What architectural pattern did you use and why? 

A: Microservices architecture for independent scaling and deployment of different modules.

10. Q: How did you document your implementation? 

A: Using detailed comments, README files, API documentation with Swagger, and sequence diagrams.

3. Functionality & Correctness 

1. Q: Does your solution fully meet the specified requirements? Explain. 

A: Yes, all functional and non-functional requirements were met, verified through UAT with the client.

2. Q: Demonstrate one core functionality of your project. 

A: [Describe/demo]: The user authentication module uses JWT tokens for secure session management.

3. Q: How did you ensure the solution is bug-free?

A: Through rigorous testing cycles, code reviews, and bug tracking in Jira.

4. Q: What edge cases did you test?

A: Cases like invalid inputs, network failures, concurrent users, and extreme data volumes.

5. Q: Describe a major bug you encountered and how you fixed it.

A: A race condition in concurrent updates; fixed using database transactions and locks.

6. Q: How does your solution handle invalid inputs?

A: Client-side and server-side validation with meaningful error messages.

7. Q: Is the functionality robust under load?

A: Yes, load tested with JMeter simulating 1000 concurrent users with <2s response time.

8. Q: What requirements were prioritized and why? 

A: Core features first (MVP approach) to deliver value early.

9. Q: How did you verify correctness against requirements? 

A: Traceability matrix mapping requirements to test cases.

10. Q: Can your solution operate offline if needed? 

A: Partial offline support via service workers and local storage for critical features.

4. Technical Quality & Innovation 

1. Q: How would you rate the code quality of your work? 

A: High—followed PEP8 standards, used linters, and maintained DRY principles.

2. Q: What innovative approaches did you introduce? 

A: Implemented [e.g., machine learning-based recommendation engine] to personalize user experience.

3. Q: Describe an optimization you performed.

A: Reduced API response time from 5s to 800ms by query optimization and caching.

4. Q: How is your solution scalable? 

A: Horizontal scaling with Kubernetes, stateless design, and database sharding readiness.

5. Q: What makes your algorithm efficient? 

A: Time complexity reduced from O(n²) to O(n log n) using [e.g., merge sort variant].

6. Q: Did you use any design patterns? Which ones? 

A: Singleton for configuration management, Factory for object creation.

7. Q: How innovative is your solution compared to existing ones? 

A: Added [unique feature, e.g., real-time collaboration using WebSockets], not common in similar tools.

8. Q: What refactoring did you do for better quality? 

A: Extracted reusable components and improved modularity.

9. Q: How did you ensure code readability? 

A: Meaningful variable names, comprehensive docstrings, and consistent formatting.

10. Q: Mention one area where you could further optimize.

A: Migrate to asynchronous processing for long-running tasks using Celery.

5. Complexity & Scope

1. Q: How complex was the problem you addressed? 

A: High complexity—involved integration of multiple systems, real-time data processing, and security compliance.

2. Q: What was the overall scope of your internship work? 

A: Full-stack development of [module], from requirements to deployment, handling end-to-end responsibility.

3. Q: Which multiple technologies did you integrate? 

A: Frontend (React), backend (Node.js), database (MongoDB), cloud (AWS), and DevOps (Jenkins).

4. Q: Describe the most challenging technical aspect. 

A: Implementing secure real-time communication with end-to-end encryption.

5. Q: How many modules or features did you develop? 

A: Developed 6 core modules including authentication, dashboard, and reporting.

6. Q: Did your work involve big data or large-scale processing? 

A: Yes, processed daily datasets of over 1 million records efficiently.

7. Q: What interdisciplinary concepts were integrated? 

A: Software engineering with domain knowledge in [e.g., healthcare/finance] and UI/UX principles.

8. Q: How broad was the impact of your work within the organization? 

A: My module is used by 500+ internal users, improving process efficiency by 40%.

9. Q: Compare the complexity with your academic projects. 

A: Much higher—real-world data, legacy system integration, and production constraints.

10. Q: What would be a possible extension to increase scope? 

A: Adding AI-driven analytics or mobile app integration.

6. Presentation Quality 

1. Q: Why did you structure your presentation in this order? 

A: Logical flow: problem → approach → implementation → results → conclusion, to build understanding progressively.

2. Q: How did you make effective use of visual aids? 

A: Used diagrams (flowcharts, architecture), minimal text slides, and live demos for clarity.

3. Q: How did you manage time during the presentation? 

A: Allocated specific minutes per section, rehearsed, and kept buffer for questions.

4. Q: What makes your slides professional? 

A: Consistent theme, high-quality images, readable fonts, and company branding.

5. Q: How did you handle nervousness or delivery? 

A: Practiced multiple times, maintained eye contact, and used clear voice modulation.

(Questions 6–10 can focus on specific slide choices, transitions, color scheme, audience engagement techniques, etc.)

7. Technical Communication 

1. Q: Explain a complex concept from your project in simple terms. 

A: [e.g., Blockchain]: It's like a digital ledger shared across many computers—immutable and transparent.

2. Q: How would you explain your project to a non-technical stakeholder? 

A: Focus on business benefits: "This system reduces manual work by 70%, saving time and reducing errors."

3. Q: Use appropriate terminology while explaining [specific topic]. 

A: Detailed technical explanation with correct terms.

(Questions focus on clarity, terminology accuracy, and handling follow-up technical queries.)

8. Depth of Understanding

1. Q: What alternatives did you consider for your approach? 

A: Considered [alternative], but chose current due to [reasons].

2. Q: Critically analyze a decision you made. 

A: Pros and cons analysis showing depth.

3. Q: Why might your solution fail in certain scenarios? 

A: Honest discussion of limitations and mitigations.

(Questions probe conceptual depth, alternatives, and critical thinking.)

9. Technical Competence

(These are typically mentor-observed, but students can reflect.)

1. Q: How quickly did you learn new technologies? 

A: Learned [tool] in 2 weeks through self-study and application.

2. Q: Describe an initiative you took beyond assigned tasks. 

A: Proposed and implemented automated testing framework.

10. Professional Conduct & Ethics

1. Q: How did you maintain confidentiality? 

A: Never shared sensitive code/data outside, used secure channels.

2. Q: Describe adherence to organizational policies. 

A: Followed dress code, reporting structure, and data handling policies.

3. Q: How did you handle ethical dilemmas, if any? 

A: Reported a potential data privacy issue promptly.