The work
This is a real, supervised technical role with small assignments and visible results. You will work only in approved public pages, demonstrations, and disposable practice environments. Training, meetings, feedback, and required corrections are paid work.
Test technology carefully
- Follow a checklist to test assigned pages on a computer and phone-sized screen.
- Try the expected path, then a few safe “what if?” cases such as missing information or a broken connection.
- Capture screenshots and write the exact steps that produced a problem.
- Retest the same behavior after a correction and report whether it changed.
Practice in a sandbox
- Follow a provided setup guide in an isolated practice environment.
- Run only approved commands or make small supervised HTML, CSS, or script changes.
- Compare the instructions with what actually happened and improve simple documentation.
- Stop and ask before installing software, changing permissions, or using an unfamiliar account.
Report what you learned
- Submit one short weekly report: assignment, result, evidence, blocker, and next question.
- Keep screenshots and notes in the assigned folder with useful names.
- Explain one technical idea in plain language without pretending to know what has not been proven.
What good work looks like
- First 30 days: complete guided checklists, produce reproducible notes, and follow every access stop-line.
- By 60 days: independently complete one bounded test-and-retest cycle and improve one checklist or setup guide.
- Communicate before a deadline when blocked, accept specific feedback, and correct the work during paid time.
Qualifications
- Curiosity about computers, websites, games, devices, or how software works.
- Ability to follow steps in order and notice when the result differs from the instructions.
- Willingness to write down evidence instead of saying only “it is broken.”
- Good judgment about stopping when access, privacy, or safety is unclear.
- No coding experience required; the role can grow as demonstrated skills grow.
Access and safety boundaries
At hire, this role has no customer or production access, no real customer data, no credentials or secrets, no deployments, no account administration, no external messages, and no unsupervised software installation. Work happens in approved public, demo, or disposable sandbox environments.
Eligibility
This youth-focused role is available only when CTM verifies privately that the candidate’s employment is permitted under applicable federal and Georgia law, including any required parent or legal-guardian ownership or corporate-officer relationship. CTM does not ask for age, birth date, school records, or identity documents in the public application.
Hiring process
- Written application and short fictional troubleshooting sample.
- Structured interview, including a small coachability exercise.
- Private eligibility review before any offer.
- If selected, written pay, schedule, supervision, and onboarding terms.
Youth-employment wording is based on current guidance from the Georgia Department of Labor, its FLSA employer FAQ, and U.S. Department of Labor Fact Sheet #43. The stricter applicable rule controls.