Participant handbook

The operating guide for the FlyRank AI Internship.

What to trust, where to look, what counts as proof, and what FlyRank will not overpromise.

At a glance

The stable version.

This page turns the kickoff, FAQs, and support policies into one participant-facing operating guide.

Cost
Free

No fees, certificate paywall, or required paid tools.

Format
Remote

Self-paced cohort work with recorded sessions when possible.

Typical pace
6-10 weeks

Most tracks fit focused 5-10 hour weekly work blocks.

Completion proof
Credential

Unlocked by required work and an accepted capstone.

How to stay informed

The portal is the source of truth for your cohort. Email, Google Group messages, calendars, and community posts help surface updates, but portal announcements are where official program updates live.

  • Read announcements before asking support; missed emails are repeated in the portal when possible.
  • Published events and calendar entries may change as mentors, staff, and guest speakers confirm availability.
  • Use support when your application, account, assignment, document, credential, or event access looks wrong.

Onboarding

Start by completing your profile, contact details, and onboarding tasks. CV upload and social links help career tools and future opportunity matching, but they do not replace program completion requirements.

  • Use the LinkedIn account tied to your application; sign-in issues usually come from account or email mismatches.
  • Upload a CV even if it is rough, so future CV audit and career-readiness tools can give better feedback.
  • LinkedIn, social sharing, and support-us tasks are encouraged but optional; never present acceptance as completion.

Program rhythm

The internship is remote, global, mostly asynchronous, and self-paced during your cohort. Live sessions, Q&As, office hours, and mentor events are scheduled when available.

  • You do not need to match a US timezone; recordings are shared when possible so time zones are not a blocker.
  • Core resources are in English, and non-native English speakers are welcome to use recordings and extra review time.
  • Governed Documents cover acceptance and confirmation letters, custom university forms, progress records, and completion proof.

Work and capstones

You have one current specialization, with General AI Fluency available alongside it. Each track qualifies independently: complete at least five assignments and an accepted capstone in a track to earn that track's certificate.

  • Assignments ask for reviewable evidence, usually GitHub, hosted pages, Google Docs, or track-specific links.
  • Capstones are your main proof of work and are reviewed for ownership, useful evidence, safe AI use, and explanation.
  • Program work is practical learning evidence, not paid client delivery or a promise that FlyRank will use your work.

Documents and university proof

Approved interns can generate governed documents from the portal. Your university decides whether the internship counts for credit.

  • Arijana Ibrović, Director of Internship Program, is the supervisor of record, and the verification contact is verify@internship.flyrank.ai.
  • D7 is the weekly progress report, D13 is the weekly log book, D2 covers uploaded university forms, and D5 covers MOU/MOA review before official PDFs are issued.
  • Send exact university requirements through support early, and confirm your school will accept FlyRank documentation.

Credentials and verification

Certificates, credentials, and letters depend on identity, track, cohort, assignment, capstone, and completion records being ready. They are never paywalled.

  • Complete at least five assignments and an accepted capstone in a track to earn that track's certificate. AI Fluency and specialization tracks qualify independently; required onboarding remains part of the internship but does not block certificate eligibility.
  • Recommendation letters are eligibility-bound and governed by completion quality and program policy.
  • Public credential verification confirms completion status without exposing private PDFs or support records.

Community, mentorship, and support

Community access, Discord, guest mentor sessions, office hours, and peer support are capacity-bound program benefits. They are announced in the portal when available.

  • Peer support matters, but staff and mentors are not a 24/7 help desk and may redirect repeat questions to public channels.
  • Respect other participants, staff, mentors, cultural backgrounds, private issues, and unpublished work.
  • Harassment, impersonation, spam, scams, or abuse can affect community and program access.

Boundaries

FlyRank AI Internship is an unpaid educational program, not employment, contract work, or a guarantee of future paid work. The program is built so participants can complete it without paid AI tools.

  • No wages, stipend, employee benefits, employment offer, work authorization, interview, or job placement is promised.
  • FlyRank does not issue default work email addresses for employment or LinkedIn workplace verification.
  • Partner-course or forwarding email access is for program access only, not company-employment verification.
Reference links

Fast paths for common questions.

These links keep participants and verifiers away from stale screenshots or informal answers.

Policy history

What changed.

2026-07-02

Kickoff and KB alignment

Handbook updated after the July 1 kickoff and live-session transcript review. The support KB remains the source of truth for document boundaries, university proof, community availability, recordings, optional tasks, and credential eligibility.

2026-05-16

Handbook published

Initial public handbook covering program format, reviews, credentials, community expectations, support routing, and accessibility paths.

2026-05-16

Legal pages refreshed

Terms and privacy pages remain the source of truth for legal obligations and data handling.

Accessibility and participation needs.

You can request help with access needs, device or bandwidth constraints, event materials, alternate formats, or site barriers. Include the affected page, event, assignment, resource, or deadline so support can route the issue.