Start with Iris's own skills and experience, then find internships that fit. Don't reshape everything around one company.
Python — make this the default coding/interview language when allowed.
JavaScript and C experience broaden the software foundation.
Existing SWE experience is important. Be ready to explain exactly what she built and solved.
UW Informatics gives access to software, UX/HCI, data and broader technology roles.
Current gap is not a problem: she hasn't learned databases/SQL yet. For now, target internships that value programming/software fundamentals. Learn basic SQL gradually rather than turning the search into a data-only path.
A simple positioning is: UW Informatics student with prior software-development experience, strongest in Python, also experienced with JavaScript/C, building stronger DS&A fundamentals and looking for hands-on software/application engineering experience.
That story should drive the résumé, role search, elevator pitch and interview preparation.
Handshake, company career pages, UW/iSchool events, LinkedIn and referrals.
Read required skills. Apply where her current foundation overlaps with the real work.
Tailor the top of the résumé and projects to the role. Apply early.
DS&A + project depth + role-specific basics + behavioral stories.
Primary target. Search SWE, software developer, application developer, backend, full-stack and general engineering internships.
PythonDS&AJSGitAPIsStrong target when Python/JS/web development or general application work is central.
Worth considering because Informatics can bridge engineering and user/product thinking, especially if the role still contains meaningful coding.
Apply selectively when requirements emphasize general programming and problem solving rather than deep systems experience.
Worth checking when the job is software engineering around AI products rather than requiring advanced ML research.
Secondary for now. Revisit more broadly after SQL/database coursework. A posting that mainly needs Python and is willing to teach the data stack can still be reasonable.
Apply only when the role matches actual interest/experience; don't target it simply because it is technical.
Tech summer recruiting can begin in autumn. UW notes that tech is one of the fields where summer recruiting may happen in fall, so don't wait for winter to start.
LeetCode approach: fewer problems with deeper understanding is better than rushing through many. Ask: what is familiar, what building blocks are being combined, why does this approach work, and what changes would break it?
Python, fundamentals, Easy/Medium DS&A, tests, edge cases and O().
Problem → architecture → her work → hard decision/bug → result → improvement.
Expect questions about anything listed on the résumé: Python, JS, C, frameworks, APIs, tools.
Prepare examples for teamwork, disagreement, failure, ownership, learning and ambiguity.
UW's online job/internship database. The iSchool also uses it for Career Services appointments, workshops and events.
Current students can get résumé, cover-letter, LinkedIn and elevator-pitch review and schedule 1:1 advising through Handshake.
Includes job documents, interview prep, professional development, recruiting policy, recruitment checklist and career-search timeline.
Use both UW-wide and iSchool-specific events. Research employers beforehand, bring a polished résumé and prepare a short introduction.
Oct. 7, 2026: UW Fall Job & Internship Fair, 11:00 a.m.–2:30 p.m. Check Handshake for participating employers and openings.
The iSchool's dedicated career fair is also especially relevant: employers historically recruit for software development, data/analytics, UX, cybersecurity, IT consulting and related roles.
Keep the main plan general. Add a company page only when an opportunity is worth targeting; that page can hold its roles, pay, dates, UW connections and reported interview questions.