Name: Krishna Mihir Tatavarthi
Pronouns: He/Him
Semester of Internship: Spring 2026
Major: Computer science
Current Class Level: Master's Student
This semester I completed a(n)...: Internship
Internship, Co-op, or Research Site (Company/Organization Name): VelocitiPM
Location of the Organization (City, State): Pheonix, Arizona
Title of position: Full Stack Engineer Intern
Tell us about your internship, co-op, or research opportunity, including your day-to-day responsibilities:
As a Full Stack Engineer Intern at VelocitiPM, I work on VelocitiPM, a product management SaaS. My responsibilities include building and shipping features across the frontend (React/TypeScript) and backend (Supabase edge functions, Python), writing and testing APIs, managing local dev environments with Docker, and collaborating with senior engineers through code reviews and ticket-based workflows.
Describe the process of obtaining your position. When did you hear of the position and submit your application?
I found the position through LinkedIn and submitted my application in January 2026. After a technical interview focused on full stack development, I received and accepted an offer to join VelocitiPM as a Full Stack Engineer Intern.
What resources did you use to find your current experience?
LinkedIn or other social media
What have you enjoyed the most about your position and organization?
I've enjoyed working on a real product that's actively used shipping features end-to-end across the full stack has been genuinely rewarding. The team trusts interns with meaningful work, and getting feedback directly from a senior engineer has accelerated my growth a lot.
How do you believe you have made an impact through your work?
I've built and shipped features that directly improve the user experience on VelocitiPM, including automating parts of the product strategy workflow using AI. My contributions have gone into production, which means real users benefit from the work I do.
What advice would you give to another student who is seeking an internship or similar experience?
Get comfortable being uncomfortable you won't know everything on day one, and that's fine. Focus on understanding the codebase before writing code, ask questions early, and treat every ticket as a chance to learn the full system, not just fix one thing.