Job search
Tech Impact ITWorks: Check Age, Degree Eligibility, and the Five-Week Internship
Check local ITWorks eligibility and daytime attendance, plan all sixteen weeks, and compare certification and internship evidence with actual IT support requirements.
Check ITWorks as a specific local, daytime training commitment before treating its free tuition or internship as a route you can attend. Tech Impact publishes age, education and location conditions, and the program includes a five-week internship within its sixteen-week structure. Meeting the published description, being admitted, earning a credential and receiving an employer’s offer are separate outcomes.
LandOffer publishes this guide and offers recent job discovery. We checked Tech Impact’s current program page and public application landing page, plus a real entry-level support advertisement, on October 23, 2026. We did not register, apply, contact admissions or assess anyone’s individual eligibility. Ari and Jordan are fictional candidates whose completed planning records show what to verify before making a commitment.

Start with the published age and education conditions
The current ITWorks page lists ages 18–26, a high-school diploma or equivalent, no four-year college degree, being local to a program headquarters and interest in technology. It also requires availability Monday through Friday, 9 a.m.–3 p.m., for sixteen weeks. Compare your age, completed education, location and availability with the full list before choosing a cohort.
The degree condition is a limit on the intended entry route, not simply reassurance that a bachelor’s degree is unnecessary. Someone who already holds a four-year degree should not assume that being new to IT overrides the published requirement. Likewise, college attendance, an unfinished degree and a completed credential are different facts. State the credential you completed and ask admissions about any uncertainty; do not rename unfinished study as a degree.
If age timing matters, ask when the program evaluates it. The public description does not settle every question about turning 27 between an application, cohort start and completion. Do not invent an exception or change dates to make an application appear eligible. A clear question about the actual timeline is more useful than relying on an informal interpretation.
Tech Impact’s July 2023 program article also describes the young-adult, high-school-graduate, no-bachelor’s audience. Use it as background alongside the current eligibility page. Older descriptions of cities, salaries or partners should not override the current cohort’s requirements or establish a personal employment prospect.
Verify the city and intake before changing your schedule
The current page identifies Philadelphia, Wilmington in Delaware, Las Vegas and Nashville, with classes in their downtown areas. It says applications are being accepted for Winter and Spring cohorts, but that banner does not supply a year-specific start date, deadline or seat count for each city. Record it as a displayed application invitation, not a confirmed place in your preferred cohort.
The linked public application portal led to a sign-in page describing an in-person program. We stopped there without entering information or creating an account. We therefore did not inspect an applicant’s city selection, admissions questions, individual decision or private cohort schedule.
Ask about the next cohort for the location you can actually reach, the attendance expectations, any required selection steps and when an admitted learner receives final dates. A virtual information session is an opportunity to learn about the program; it is not evidence that the training itself can be completed remotely.
Keep historical launch announcements in their proper place. Tech Impact’s September 2024 Nashville announcement described plans for its initial local launch. That dated launch announcement does not confirm a current Nashville start date, open seat or internship pay rate. For a present decision, obtain the applicable cohort information rather than reusing a date from that announcement.
Reserve time for both study and the internship
ITWorks describes eleven weeks of technical learning followed by five weeks at a local corporation or nonprofit. The subjects include hardware, troubleshooting, networking and security. Treat the internship as part of the planned training route, not an optional extra to fit around another full-time daytime obligation.
The published 9 a.m.–3 p.m. commitment deserves a calendar check before you promise attendance. Add door-to-door travel, preparation and breaks around the class block before comparing it with work and care commitments. If you work shifts, provide the real schedule when asking about conflicts. An employer’s willingness to change your hours needs confirmation; an optimistic conversation is not a revised rota.
For the internship, ask about the host’s location, working hours, duties, supervision and arrangements for absences. Do not assume the host follows precisely the classroom schedule. An internship may also expose a commute or workplace requirement that differs from the training site, so keep the final five weeks visible when planning all sixteen.
The 2024 Nashville announcement described a paid internship. That dated statement does not establish a current pay rate, pay schedule or funding arrangement for every city and cohort. Confirm those details for the actual placement before using anticipated internship income to cover essential expenses.
Worked planning asset: Ari’s sixteen-week calendar
Fictional Ari is 24, lives in Wilmington, holds a high-school diploma and an associate’s degree, and has not completed a four-year degree. Ari works weekend retail shifts and wants to investigate daytime IT support training. These facts support a focused admissions question; they are not an admission or eligibility determination by Tech Impact.
Ari’s completed planning record is:
| Item | Ari’s recorded fact or calculation | Decision before committing |
|---|---|---|
| Age and education | Age 24; high-school diploma; associate’s degree; no completed four-year degree | Supply accurate education details and obtain the program’s review |
| Location | Wilmington resident; training-site journey estimated at 45 minutes each way | Verify the actual site and test the route at attendance times |
| Daytime availability | Can reserve Monday–Friday, 9 a.m.–3 p.m. if weekend work remains separate | Obtain the employer’s confirmed shift arrangement |
| First eleven weeks | Eleven weekly calendar blocks of 30 hours: 330 hours reserved | A planning reservation, not a statement of formal instructional hours |
| Final five weeks | Provisional reservation of another 150 hours | Rework this once the actual host schedule is known |
Across sixteen weeks, Ari reserves 480 daytime calendar hours. The assumed commute adds 7.5 hours a week, or 120 hours across sixteen weeks. A separate five-hour weekly preparation allowance adds 80 hours. The resulting planning total is 680 hours, averaging 42.5 hours weekly, before weekend employment and other personal commitments. These are Ari’s assumptions, not a published workload requirement or a verified transit timetable.
The calculation reveals which work shifts, journeys and placement details must be settled before Ari can rely on the plan. Free tuition would not make the weekday block available if retail shifts moved back into it. A longer internship journey could also break the plan even when the first eleven weeks work. Ari marks the employer rota, training address and host schedule as unresolved dependencies rather than declaring the calendar feasible.
Ari’s completed, unsent question is: “I live in Wilmington, am 24 and hold a high-school diploma and an associate’s degree, without a completed four-year degree. Which upcoming local cohort should I investigate, and what are its confirmed dates and attendance expectations? Before changing my work schedule, I also need to understand how internship hours, location and any financial support are confirmed.”
The recorded next step is to obtain those facts and revise the calendar. Ari has not applied, received a seat, resigned from a job or assumed an internship wage.
Treat certification preparation, credentials and work evidence separately
The program describes preparation for certification exams, including CompTIA A+ and Cisco IT Essentials; its current longer overview also names CompTIA AI Essentials. Ask the cohort which exams and related costs are included, when attempts occur and what happens if further preparation is needed. Preparing for an exam and earning the credential are different resume entries.
Tech Impact’s older program article describes hands-on hardware activities and professional-skills development. A useful learning record explains what you practiced, how you checked it and what you would escalate. A certificate title alone does not show how you communicated with a user or documented an unresolved issue.
Likewise, an internship can provide supervised experience without giving you ownership of the employer’s systems. Preserve your actual responsibilities, dates and level of supervision. Ask permission before using examples publicly, and substitute synthetic devices or data when explaining your method. Do not publish internal tickets, user details or access information to prove that you trained.
The relevant career direction here is entry-level IT support. If your goal is software development, compare the program’s support tasks with the coding work you intend to do. Do not assume a short support internship establishes application-development experience, independent systems administration or security-engineering responsibility.

Worked readiness asset: Jordan compares training with a real support role
Fictional Jordan is 19, lives in Las Vegas and is exploring ITWorks. Jordan has completed a personal lab exercise but has not enrolled, earned the program’s credentials or started an internship. The comparison uses Grand Sierra Resort’s IT Support Specialist I advertisement, requisition 26468, read on its employer-hosted careers page.
That job is in Reno, not Las Vegas. It describes first-line support, ticket documentation, user communication and following access-control procedures. Its conditions include age 21 or older, flexible shifts, a high-school diploma, relevant experience or an acceptable combination of training and experience, and the ability to obtain an appropriate gaming license. It is a role-reading example, not an ITWorks referral or a promise of a continuing vacancy.
| Readiness question | Jordan’s completed evidence comparison | Remaining boundary |
|---|---|---|
| Troubleshooting | Personal lab: checked a synthetic printer connection and recorded the observed symptoms | Lab practice is not employment or proof of this employer’s system knowledge |
| User communication | Wrote a plain-language explanation of the checks and next action | Still needs feedback on interacting with real users under supervision |
| Ticket documentation | Prepared a sample note separating symptoms, checks, result and escalation | Must not claim access to a real employer ticket system |
| Internship learning | Would ask a supervisor to review an appropriately sanitized support example | No actual internship assignment or competency sign-off exists |
| Job conditions | Age 19 and Las Vegas location differ from this Reno role’s requirements | Do not treat training eligibility as employer eligibility |
Jordan’s completed lab note reads: “Synthetic user reports a printer unavailable. Confirmed the intended device and connection, checked its status, and recorded the error shown. The test did not resolve the fault; next action is to escalate with the checks already completed.” It avoids claiming a repair that did not happen and does not teach bypassing access controls.
The comparison’s result is a preparation plan, not an application recommendation. Jordan can work on accurate troubleshooting notes and user explanations while investigating suitable training. The reviewed employer conditions remain separate; finishing a course would not erase the age or location difference. Future job searches require fresh postings and requirements rather than this example’s continued availability.
Clarify the support you would receive without assuming an outcome
ITWorks advertises mentoring, employer connections and job-placement assistance. Ask how those services work in the cohort you are considering: who provides feedback, how internship matching is handled and what support continues after graduation. An employer connection is a chance to learn about work; it is not automatically an interview or hiring decision.
The program page also lists travel stipends, laptops and other assistance. Confirm what is available to your cohort, when it is provided and whether any conditions apply. Do not assume it covers housing, every journey or all lost earnings. Confirm the assistance and the attendance plan separately before relying on either.
Keep a record of the actual next stage: information gathered, application submitted, decision received, enrollment confirmed, training completed, credential earned and employer offer received. Only change a stage when its own evidence exists. National program statistics and graduate stories describe reported past experiences, not your admission, certification or employment result.
Choose the program by the work and schedule you can support
ITWorks is a route to investigate when the published young-adult, education, location and daytime conditions fit the training question you need to answer. The decision should rest on a real cohort and a sustainable sixteen-week plan, including its internship, rather than on the appeal of a free credential alone.
Use recent roles on LandOffer alongside original employer pages to compare support duties, shifts, location and required evidence. Use that role comparison to prepare cohort questions and identify support tasks you still need to practice; keep the work record accurate. Admission, exam success, internship arrangements and a subsequent employer offer each need their own confirmation.
Sources and Further Reading
- Tech Impact ITWorks, current published eligibility, format, locations and intake wording; checked October 23, 2026.
- Public application landing page, in-person description and sign-in destination only; no applicant account inspected.
- How to Access Free IT Training, July 27, 2023 background article; older salary and partner claims not adopted as current outcomes.
- Nashville expansion announcement, September 5, 2024 historical launch description; not a current cohort calendar or pay promise.
- Grand Sierra Resort IT Support Specialist I, requisition 26468, employer duties and conditions read in full; Reno example, no program relationship or application tested.


