Switching to IT
How to conduct effective informational interviews to learn about day to day responsibilities in IT roles.
A practical guide to using informational interviews for uncovering real duties, boundaries, and skills across IT roles, with strategies to prepare, ask insightful questions, and interpret insights for career planning.
Published by
Matthew Stone
July 26, 2025 - 3 min Read
Informational interviews are a powerful, practical way to gain nuanced insight into what daily work feels like in IT roles, beyond job postings and generic descriptions. Start by identifying people whose paths align with your learning goals, whether in software development, cybersecurity, data engineering, or IT operations. Approach them with respect for their time, offering a concise rationale and a clear ask. Before you speak with them, map out your own goals: what information would genuinely help you decide if this path suits you, and what skills you still need to build? A thoughtful prework step sets a productive tone and increases the odds of useful, concrete guidance.
In your outreach, emphasize curiosity over ambition, and signal that you want practical, day-to-day realities rather than lofty forecasts. Prepare prompts that invite storytelling: “What does a typical day look like for you?” “What tasks take the most time, and which skills are indispensable?” “How do you collaborate with others and manage competing priorities?” Avoid generic questions about salary or hype around technologies; instead, seek examples, tradeoffs, and constraints that reveal the rhythm of the job. A well-framed inquiry earns trust and yields richer, more actionable replies.
Translate insights into a clear, actionable learning plan and milestones.
During the interview, listen for patterns that recur across roles and teams, such as problem-solving approaches, collaboration styles, and the pace of change. Take notes that capture concrete responsibilities rather than vague impressions. For instance, you might record how much time is spent debugging, writing documentation, or coordinating with cross-functional teams. Note the tools mentioned, the workflows described, and the level of autonomy expected in decision-making. These specifics help you map a realistic skill set to future roles and prioritize learning efforts that will move you closer to your target.
After the conversation, synthesize what you learned into a practical picture of day-to-day life. Compare the interviewee’s experiences with your current strengths and gaps, then translate that into a concrete learning plan. Identify two or three core competencies to develop first, such as scripting for automation, basic system administration, or interpreting data visualizations. Set measurable milestones, like completing a hands-on project or earning a relevant credential within a defined timeframe. Finally, reflect on whether the role aligns with your temperament, preferred pace, and long-term career goals.
Be purposeful about structuring conversations to surface practical truths.
When you reach out to multiple professionals, track contact details and the scope of each conversation. Keep a simple matrix that notes the role, organization, date, main takeaways, and any follow-up you promised. This record helps you identify patterns across companies and specialties, which strengthens your ability to evaluate fit. It also makes future outreach more efficient because you can tailor requests to address a shared theme. If possible, ask for permission to reconnect after you’ve made progress in your learning plan; many interviewees appreciate updates and may offer additional guidance or referrals.
To maximize value from each exchange, bring a clear, concise agenda to the call. Share your learning goals at the outset and ask targeted questions that align with those aims. Examples include inquiries about the most essential day-to-day tasks, how much time is spent on collaboration versus independent work, and which problems frequently require escalation. Be explicit about what you want to achieve in the short term, whether it’s mastering a tool, understanding a workflow, or learning about the team’s culture. Respect boundaries around confidentiality and avoid pressing for insider information.
Pair conversations with hands-on projects to demonstrate progress.
In parallel with interviews, leverage portfolio projects to validate and deepen what you learn. Build small experiments that simulate real tasks the interviewee described, such as automating a routine process, writing a script to parse logs, or deploying a simple monitoring setup. Document your results and challenges, then compare them with the interview insights. This hands-on practice not only reinforces knowledge but also demonstrates initiative to future employers. By pairing conversation with practical, shareable work, you transform abstract advice into tangible capabilities that you can showcase in interviews.
Additionally, cultivate a habit of continuous learning as part of your IT journey. Subscribe to technical newsletters, participate in online communities, and dedicate regular time to practice. When you discuss progress with mentors or interview partners, you can frame your growth in terms of concrete outcomes rather than just intentions. Emphasize how you’ve translated feedback into improved performance, such as faster troubleshooting, cleaner code, or more resilient automation. A mindset oriented toward incremental improvements signals readiness for real-world responsibilities.
Build a living reference of tasks, tools, and priorities.
When you speak with seasoned IT professionals, you may hear about tradeoffs between speed and quality, or between innovation and stability. These conversations reveal the nuanced realities behind claims of cutting-edge technology. Listen for how teams balance risk, security, and user needs, and note the constraints that guide decisions. You’ll often find that soft skills—communication, prioritization, and stakeholder management—are as important as technical know-how. By collecting examples of how these elements intertwine in daily practice, you gain a more accurate map of what to develop to succeed in your target environment.
As you accumulate interviews, organize the insights by theme: daily tasks, collaboration patterns, decision-making, tooling, and learning paths. This thematic catalog becomes a reference you can consult when planning your path forward. It helps you validate your interests, refine your skill gaps, and choose relevant certifications or projects. When you revisit insights, look for shifts over time—what new challenges are emerging, what tools are changing, and where teams are investing their energy. This dynamic approach keeps your plan aligned with evolving industry realities.
A well-executed informational interview strategy also enhances your networking posture. By showing genuine curiosity, you build rapport with professionals who might later become mentors or referrals. Treat each conversation as a learning partnership rather than a transaction. Follow up with a brief note summarizing key takeaways and expressing appreciation for the time and guidance shared. If appropriate, offer a quick recap of how you applied what you learned and sent an update on your progress. This thoughtful reciprocity strengthens relationships and keeps doors open for future collaboration or opportunities.
Finally, translate the cumulative wisdom into a credible narrative for resumes and interviews. Craft concise, outcome-focused bullets that reflect actual tasks and competencies you observed or practiced. Emphasize your exposure to core IT workflows, collaboration dynamics, and problem-solving approaches rather than listing every tool you encountered. When you present yourself to potential employers, frame your learning journey as a proven strategy for quickly contributing to their team. A well-supported story grounded in real examples makes your candidacy memorable and credible.
