resume

Log | Files | Refs | README

CEI_HelpDesk_interview_prep.md (8141B)

      1 # CEI Engineering Associates — Help Desk Technician Interview Prep
      2 
      3 **Role:** Help Desk Technician, Bentonville AR  
      4 **Company:** Civil engineering, land surveying, landscape architecture. Est. 1973. ~180 staff, coast to coast.
      5 
      6 ---
      7 
      8 ## What CEI Is Looking For
      9 
     10 The job description emphasizes three things above all else:
     11 
     12 1. **Customer service attitude** — "professional and helpful demeanor," coaching users, not just fixing
     13 2. **Troubleshooting process** — identify the problem, determine best resolution, coach through it
     14 3. **Documentation** — track issues, spot patterns, look for improvements
     15 
     16 Your A+ cert is a named preference. Lead with it.
     17 
     18 ---
     19 
     20 ## About CEI — Know Before You Go
     21 
     22 - Engineering firm, not a tech company. Their staff are engineers, surveyors, architects — smart people who need their tools to work so they can focus on their actual work
     23 - "Coast to coast" offices means remote/distributed support is likely part of the job
     24 - The role mentions "occasional overnight travel" — be prepared to say you're open to it
     25 - ESOP (Employee Stock Ownership Plan) means employees own a stake — they care about who they hire
     26 
     27 **Why CEI specifically?** Have an answer ready. Something honest: stable company, established reputation, you want to support a team of professionals who depend on reliable tooling.
     28 
     29 ---
     30 
     31 ## Likely Question Categories
     32 
     33 ### 1. Behavioral ("Tell me about a time...")
     34 
     35 These follow the **STAR format**: Situation, Task, Action, Result.
     36 
     37 ---
     38 
     39 **"Tell me about a time you helped someone who was frustrated with a technical problem."**
     40 
     41 Draw from: Your QA role. When you find and report a defect, developers sometimes push back or are skeptical. You had to stay professional, explain the issue clearly, and work toward resolution together.
     42 
     43 Or: Home lab context — helping someone remotely (family, friend) troubleshoot a tech issue over the phone.
     44 
     45 Key points to land: You stayed calm, listened first, didn't make them feel bad for not knowing.
     46 
     47 ---
     48 
     49 **"Tell me about a time you had to explain something technical to a non-technical person."**
     50 
     51 Draw from: QA role — you write defect reports for developers, but also explain issues to product owners or managers who aren't technical. Or from your Consumer Testing Labs days — communicating testing results across departments.
     52 
     53 Key points: You adjust your language to your audience. You check for understanding rather than assuming they got it.
     54 
     55 ---
     56 
     57 **"Tell me about a time you had to handle multiple requests at once."**
     58 
     59 Draw from: QA — managing an active test cycle where multiple bugs come in at once, and you have to triage by severity and impact.
     60 
     61 Key points: You assess priority (what's blocking work vs. what's inconvenient), communicate realistic timelines, don't let things fall through the cracks.
     62 
     63 ---
     64 
     65 **"Tell me about a time you identified a recurring problem and did something about it."**
     66 
     67 Draw from: QA directly — "Identify, document, and track defects to surface patterns and drive resolution" is literally on your resume. Give a concrete example if you have one.
     68 
     69 Or: Home lab — noticed a recurring failure in a backup job, investigated the root cause, fixed it systematically.
     70 
     71 Key points: You don't just solve one-offs. You look at what the pattern tells you and address the source.
     72 
     73 ---
     74 
     75 ### 2. Technical / Scenario
     76 
     77 **"Walk me through how you'd troubleshoot a user's computer that can't connect to the network."**
     78 
     79 Suggested approach to talk through:
     80 1. Ask the user — is it all sites or one? Wired or Wi-Fi? Did anything change recently?
     81 2. Check the obvious first: cable, Wi-Fi toggle, airplane mode
     82 3. `ipconfig` — do they have an IP? DHCP issue vs. connectivity issue
     83 4. Ping the gateway, then 8.8.8.8, then a domain name — isolates where it breaks
     84 5. If Wi-Fi: forget and re-add the network, check adapter driver
     85 6. Escalate if it's infrastructure (switch port, DHCP server, etc.)
     86 
     87 Key points: You work methodically, you ask questions before assuming, you know when to escalate.
     88 
     89 ---
     90 
     91 **"A user says Outlook isn't receiving email. What do you do?"**
     92 
     93 1. Ask clarifying questions: is it just not receiving, or also can't send? Is it one account or all? When did it start?
     94 2. Check if they can log into webmail (OWA) — isolates client vs. server issue
     95 3. If client issue: check account settings, try removing/re-adding the account, check Outlook profile
     96 4. If server-side: check with another user, escalate to whoever manages Exchange/M365
     97 5. While waiting on escalation: document and set expectations with the user
     98 
     99 ---
    100 
    101 **"How do you handle a situation where you don't know the answer?"**
    102 
    103 Be honest: say you don't know, but you'll find out. You know how to research (documentation, Microsoft support, vendor KB articles). You escalate when appropriate and don't guess in ways that could make things worse. You follow up with the user — you don't leave them hanging.
    104 
    105 ---
    106 
    107 **"What's your process when you close a support ticket?"**
    108 
    109 Document what the problem was, what steps you took, what resolved it, and any follow-up needed. This serves two purposes: the next tech who sees the same issue has a reference, and patterns across tickets point to systemic problems worth fixing.
    110 
    111 ---
    112 
    113 ### 3. Role / Background Questions
    114 
    115 **"Tell me about your CompTIA A+ certification."**
    116 
    117 You hold an active A+ cert. It covers hardware, OS troubleshooting, networking basics, mobile devices, printers, security fundamentals — directly applicable to this role. You're also currently pursuing additional certs (Linux+, and beyond).
    118 
    119 ---
    120 
    121 **"Do you have ITIL experience?"**
    122 
    123 Honest answer: You don't have the ITIL Foundations certification, but you're familiar with the concepts — structured ticketing, incident vs. problem management, escalation paths, service-level thinking. It's on your list. (If you want to get ahead of this, the ITIL 4 Foundation exam is straightforward and affordable.)
    124 
    125 ---
    126 
    127 **"You've been in QA and mechanical testing — why help desk?"**
    128 
    129 Your whole career has involved troubleshooting, documentation, and communicating technical findings to people who need clear answers. Help desk is a direct application of that. QA and help desk both require methodical thinking, user empathy, and closing the loop on issues. You're not pivoting away from something — you're applying your existing strengths in a support-focused role.
    130 
    131 ---
    132 
    133 **"Do you have direct help desk experience?"**
    134 
    135 Be honest: not professionally. But you've been the de facto tech support for people around you, you manage your own infrastructure (home lab), and your QA work involves the same core skills — identify, document, resolve, communicate. You also already have the cert they list as preferred.
    136 
    137 ---
    138 
    139 ### 4. Questions to Ask Them
    140 
    141 Have 3-4 ready. These signal genuine interest and help you evaluate the role.
    142 
    143 - "What does the ticketing system look like — do you use something like ServiceNow, Jira, or a different platform?"
    144 - "What are the most common issues you see day to day?"
    145 - "How is the IT team structured — is this a one-person help desk, or are there tiers?"
    146 - "What does the first 90 days look like for someone in this role?"
    147 - "You mentioned occasional overnight travel — can you give me a sense of how often that comes up?"
    148 
    149 ---
    150 
    151 ## Your Strongest Talking Points
    152 
    153 | Their Need | Your Evidence |
    154 |---|---|
    155 | Troubleshooting methodology | QA role + home lab (you build and fix things systematically) |
    156 | Documentation and pattern recognition | Both QA and mechanical testing — it's in your DNA |
    157 | Cross-platform familiarity | Windows, Linux, macOS, iOS, Android — all on your resume |
    158 | A+ certification | Active, verified cert — their named preference |
    159 | Professional communication | 12 years of cross-department technical reporting |
    160 | Staying calm under pressure | QA: reporting bad news diplomatically is the job |
    161 
    162 ---
    163 
    164 ## Day-of Reminders
    165 
    166 - Bring printed copies of your resume
    167 - Dress professionally — civil engineering firm, not a startup
    168 - Be ready to discuss the driver's license requirement (you have one)
    169 - Arrive early — Bentonville traffic can be unpredictable