resume

Log | Files | Refs | README

CEI_ITDirector_Meeting_Prep.md (5805B)

      1 # CEI Engineering Associates — IT Director Meeting Prep
      2 
      3 **Role:** Help Desk Technician  
      4 **Stage:** In-person with IT Director  
      5 **Date:** 2026-06-29
      6 
      7 ---
      8 
      9 ## What This Meeting Is About
     10 
     11 The phone screen confirmed your qualifications. The IT director is now evaluating:
     12 
     13 1. **Fit** — Will you work well with the team and the company culture?
     14 2. **Attitude** — Are you someone they want to invest in?
     15 3. **Judgment** — Do you think like a technician or like someone who just wants to close tickets?
     16 
     17 Come in as a professional, not a candidate begging for a job. You have real experience, real certs, and real infrastructure you built yourself.
     18 
     19 ---
     20 
     21 ## Likely Questions and How to Answer Them
     22 
     23 ---
     24 
     25 **"Tell me about yourself."**
     26 
     27 Keep it under 90 seconds. Hit three beats:
     28 1. Where you're coming from (QA at Leggett & Platt, mechanical testing before that)
     29 2. What ties it together (troubleshooting, documentation, clear communication across teams)
     30 3. Why now (you hold your A+ and Linux+, you've been building toward a dedicated support role, this is the right move)
     31 
     32 Do not recite your resume. Give them the narrative.
     33 
     34 ---
     35 
     36 **"Why CEI?"**
     37 
     38 CEI is a real company with a 50-year track record, distributed offices, and professionals who depend on their tools to do serious work. That's an environment where good support actually matters. You're not interested in retail IT or a chaotic startup -- you want to support people who have demanding, technical jobs of their own.
     39 
     40 ---
     41 
     42 **"Where do you want to be in a few years?"**
     43 
     44 You want to build depth. You're already pursuing additional certs beyond A+ and Linux+. You want hands-on experience with enterprise tools, ticketing systems, and the kind of infrastructure a company like CEI runs. You're not here to punch a time card -- you want to grow into a well-rounded support professional.
     45 
     46 Don't say "IT director." Don't oversell ambition. Be honest.
     47 
     48 ---
     49 
     50 **"You've been in QA -- why the switch to help desk?"**
     51 
     52 You've been troubleshooting, documenting, and communicating technical issues your whole career. Help desk isn't a pivot -- it's applying those same skills in a user-facing role. QA taught you to think methodically, communicate clearly with non-technical stakeholders, and close the loop on problems. That's exactly what good help desk looks like.
     53 
     54 ---
     55 
     56 **"Do you have direct help desk experience?"**
     57 
     58 No, not professionally -- and say so directly. But you've been managing real infrastructure at home, you've been the de facto tech support for people around you, and your QA work uses the same core loop: identify, document, resolve, follow up. You also already hold the cert they listed as preferred. You're not starting from zero.
     59 
     60 ---
     61 
     62 **"What do you do when you're stuck on a problem?"**
     63 
     64 You start with what you know and work outward: reproduce the issue, check the obvious first, consult documentation and vendor KB articles. If you're genuinely stuck, you escalate -- you don't guess in ways that could make things worse, and you always set expectations with the user so they're not left in the dark. You also document what you tried so the next person has a starting point.
     65 
     66 ---
     67 
     68 **"How do you handle a frustrated user?"**
     69 
     70 You listen first. Let them explain the problem fully -- people calm down when they feel heard. You stay even-keeled, don't take it personally, and focus on moving toward a resolution. You've done this in QA: reporting defects to developers who pushed back, explaining technical findings to managers who didn't want to hear them. Staying professional under pressure is part of the job.
     71 
     72 ---
     73 
     74 **"Tell me about your home lab."**
     75 
     76 Keep it punchy -- don't go down a rabbit hole. You built servers from the ground up, run Proxmox for virtualization, manage Linux and FreeBSD hosts, and maintain a backup pipeline across local and cloud storage. You use Ansible to keep deployments repeatable. You built it because you like having things that actually work, and maintaining it keeps your skills current.
     77 
     78 If they're interested, they'll ask more. If they're not, you've planted the seed.
     79 
     80 ---
     81 
     82 ## Questions to Ask the IT Director
     83 
     84 Have at least three ready. These signal genuine interest and give you real information.
     85 
     86 - "How is the IT team structured right now, and where does this role fit in?"
     87 - "What's the biggest challenge the team is working through at the moment?"
     88 - "What does success look like in the first 90 days for someone in this role?"
     89 - "How do you prefer technicians handle situations where they're stuck -- come to you, escalate to a vendor, or work through it independently first?"
     90 - "What does the on-call or after-hours support picture look like?"
     91 
     92 ---
     93 
     94 ## Your Strongest Cards
     95 
     96 | What They Need | What You Bring |
     97 |---|---|
     98 | Methodical troubleshooting | QA + home lab -- you build things and fix them systematically |
     99 | Documentation discipline | Both QA and mechanical testing -- it's habit, not an afterthought |
    100 | Clear communication | 12 years of cross-department technical reporting |
    101 | Cross-platform coverage | Windows, Linux, macOS, iOS, Android -- all real, not just coursework |
    102 | A+ certification | Active, verified -- their named preference |
    103 | Calm under pressure | QA: delivering bad news diplomatically is the job |
    104 
    105 ---
    106 
    107 ## Day-of
    108 
    109 - Bring printed copies of your resume
    110 - Dress professionally -- civil engineering firm, not a tech startup
    111 - Arrive early -- Bentonville traffic
    112 - Driver's license: you have one, confirm if asked
    113 - Overnight travel: say you're open to it
    114 
    115 ---
    116 
    117 ## One Thing to Leave Them With
    118 
    119 You are not someone who just studied for a cert and applied. You built real infrastructure, you maintain it, and you approach problems the same way whether it's a home server or a coworker's laptop: methodically, with documentation, and with follow-through.