More
    CultureTop 10 Up-and-Coming AI Culture Events You’ll Actually Want to Attend

    Top 10 Up-and-Coming AI Culture Events You’ll Actually Want to Attend

    AI is no longer a niche curiosity—it’s a social, creative, and commercial force reshaping how we make art, tell stories, launch startups, and build communities. If you’re looking to plug into this energy, the fastest hack is to immerse yourself in the right events. This guide spotlights ten up-and-coming gatherings where AI culture is being made in real time. You’ll learn what each event is, who it’s for, how to prepare, what to bring, and how to measure your return so you don’t just attend—you actually level up.

    Key takeaways

    • AI culture is happening live at emerging festivals, conferences, and community summits—these are your best entry points from zero to hero.
    • Preparation beats proximity: define goals, map sessions, and pre-schedule a handful of conversations before you arrive.
    • Measure what matters: track a small set of KPIs (conversations, demos booked, content shipped, collaborations started) to convert hype into results.
    • Respect the craft: follow codes of conduct, credit collaborators, and be transparent about AI use in art and demos.
    • Start small, ship often: pick one event, do it well, then scale the playbook across the rest of the calendar.

    1) Runway AI Film Festival (AIFF)

    What it is & why it matters
    A young but influential film festival showcasing short-form storytelling that blends traditional craft with generative tools. It’s become a proving ground for directors, animators, and multidisciplinary creators experimenting with new pipelines. Expect screenings, awards, and showcases across major cultural capitals.

    Core benefits

    • Exposure to the newest AI-driven film techniques and pipelines.
    • Networking with directors, producers, and tool-makers.
    • A clear bar for quality via juried selections and finalist showcases.

    Requirements & low-cost alternatives

    • Prereqs: a short film or work-in-progress helps, but curious creators and producers benefit as attendees.
    • Equipment: laptop/tablet for notes and reels; portable SSD with portfolio; headphones for on-site review.
    • Budget: festival pass + travel (look for student/early-bird tiers).
    • Low-cost alt: watch finalist screenings online, study public case studies, and join remote meetups.

    How to do it (beginner steps)

    1. Define the “one scene” goal: identify a single shot or sequence in your film you’ll refine using techniques you learn.
    2. Scout sessions: shortlist 3 talks on workflow, 1 on ethics, and 1 on distribution.
    3. Book 5 micro-meetings: DM filmmakers in advance (15-minute coffee windows).
    4. Bring a 60–90 second reel and a one-page breakdown of your pipeline and credits.
    5. Post-fest: publish a reflective thread or behind-the-scenes micro-case study within 72 hours.

    Beginner modifications & progressions

    • Simplify: attend virtually and build a “festival-at-home” plan (replays + local watch party).
    • Scale up: submit to the next cycle; collaborate with a composer or VFX artist you met; aim for a city screening.

    Frequency, duration & metrics

    • Frequency: once per year (plus one smaller local showcase).
    • KPIs: 10 quality conversations, 2 collaboration leads, 1 revised scene shipped within 30 days.

    Safety, caveats & common mistakes

    • Respect IP: credit your team and data sources; keep your dataset notes tidy.
    • Avoid hype-overload: pick a single tool to trial deeply post-event.

    Mini-plan (2–3 steps)

    • Week 0: cut a clean 90-second reel.
    • Event week: attend 5 target sessions, record takeaways with timestamps.
    • +72 hours: ship a revised scene and tag collaborators.

    2) AI on the Lot

    What it is & why it matters
    A community-driven conference that connects filmmakers, studio execs, engineers, and startups focused on AI for production, post, and distribution. The vibe: practical demos, workflows, and real talk about rights, credits, and jobs.

    Core benefits

    • Direct access to studio perspectives and real use cases.
    • Hands-on demos for pre-viz, editing, localization, and synthetic production.
    • A bridge between indie creators and industry decision-makers.

    Requirements & low-cost alternatives

    • Prereqs: none; having a prototype or reel helps.
    • Equipment: business cards (physical + QR), a one-page workflow sheet, and NDAs ready if needed.
    • Budget: pass + two nights lodging; split Airbnb with peers.
    • Low-cost alt: watch community recaps and recorded sessions; join regional spin-offs.

    How to do it (beginner steps)

    1. Pick one workflow to stress-test (e.g., dialogue cleanup, storyboard-to-shot).
    2. Create a “demo storyboard”: a 6-panel PDF framing your use case.
    3. Target 3 booths for deep dives; ask for workflow checklists.
    4. Book 2 meetings with studio or platform reps; come with rights & credits questions.
    5. Follow-up pack: 1-pager + 2-minute Loom demo.

    Beginner modifications & progressions

    • Simplify: focus on community sessions; skip big keynotes.
    • Scale up: propose a lightning talk; submit your short to a related screening series.

    Frequency, duration & metrics

    • Frequency: annual, with optional regional visits.
    • KPIs: 1 pilot test secured, 3 serious follow-ups, 1 workflow change adopted.

    Safety, caveats & common mistakes

    • Don’t oversell: be transparent about tool limits.
    • Credit protocol: agree on attribution and rights before sharing drafts.

    Mini-plan

    • Before: draft a two-page deck for your use case.
    • During: attend 3 technical sessions, 1 ethics panel.
    • After: send a “pilot proposal” template to qualified leads.

    3) AI Fringe

    What it is & why it matters
    A public-facing, multi-venue “fringe” festival that rides alongside major policy and industry moments. It mixes talks, workshops, and community-led sessions, prioritizing accessibility and exchange between researchers, builders, artists, and the public.

    Core benefits

    • Easy on-ramps for newcomers; strong conversation quality.
    • Cross-disciplinary formats (policy, art, startups, civic tech).
    • Timely programming aligned with global AI milestones.

    Requirements & low-cost alternatives

    • Prereqs: none.
    • Equipment: notebook, laptop, and a clear personal “learning brief.”
    • Budget: many sessions are lower cost or free; travel is the big variable.
    • Low-cost alt: attend remote streams and local spin-offs.

    How to do it (beginner steps)

    1. Pick a theme (e.g., AI & education, public art, health).
    2. Curate 4 sessions around that theme; draft 3 questions for each.
    3. Join an open mic or lightning slot to share your project or ask for collaborators.

    Beginner modifications & progressions

    • Simplify: attend one day, two sessions, one meetup.
    • Scale up: host your own fringe session with a partner venue.

    Frequency, duration & metrics

    • Frequency: once a year plus occasional pop-ups.
    • KPIs: 2 collaborators found, 1 public artifact shipped (blog, demo, deck).

    Safety, caveats & common mistakes

    • Civility first: fringe events draw diverse views—listen before you pitch.
    • Don’t overscope your talk: shorter, concrete demos win.

    Mini-plan

    • Plan: one-page “learning brief” (theme, questions, desired outcomes).
    • Attend: 4 sessions + 1 meetup.
    • Publish: a public recap and a small prototype.

    4) AI Fashion Week

    What it is & why it matters
    A platform and runway showcase for AI-assisted fashion design. Designers submit collections, experiment with creative direction and brand storytelling, and present work that sits at the intersection of style, synthetic imagery, and physical craft.

    Core benefits

    • A credible stage for AI-native designers and digital fashion houses.
    • Feedback from judges and peers; visibility to brands and retailers.
    • Bridges to photography, music, and motion graphics collaborations.

    Requirements & low-cost alternatives

    • Prereqs: a concept collection and a visual pipeline (image-to-look or 3D + AI).
    • Equipment: design suite (from open-source to pro tools), prompt logs, and mood boards.
    • Budget: submission fees, production for lookbooks or show pieces.
    • Low-cost alt: submit digital-only lookbooks; collaborate with photographers for TFP (trade-for-portfolio).

    How to do it (beginner steps)

    1. Write your brand brief: 150 words on ethos, silhouette, and references.
    2. Build a 12-look capsule: start with 3 cornerstone looks and iterate variants.
    3. Create a submission folder: images, a 30-second video, prompt/process notes.
    4. Work with a stylist or 3D artist to stress-test realism and cohesion.
    5. Prepare a “production plan” if your concept moves to physical prototyping.

    Beginner modifications & progressions

    • Simplify: build a 6-look digital capsule; share as an interactive lookbook.
    • Scale up: prototype a hero garment; pitch pop-up collabs.

    Frequency, duration & metrics

    • Frequency: yearly; add one digital fashion challenge per quarter.
    • KPIs: 1 shortlist/feature, 3 editor meetings, 1 collaboration MOU.

    Safety, caveats & common mistakes

    • Model and brand rights: never imply endorsement; be explicit on how imagery is made.
    • Fabric feasibility: test materials early if you plan to produce garments.

    Mini-plan

    • Week -2: mood board + three silhouettes.
    • Event week: publish a cohesive lookbook; network with two buyers.
    • +30 days: ship one physical prototype or photoreal 3D render.

    5) TEDAI San Francisco

    What it is & why it matters
    A curated conference under the TED banner devoted entirely to AI—its promise, perils, and practical applications. Expect polished talks, provocative panels, and a high concentration of builders, researchers, and policy voices.

    Core benefits

    • Big-picture insights with pragmatic takeaways.
    • A concentrated network across science, design, business, and culture.
    • High-quality stage content you can reference and share.

    Requirements & low-cost alternatives

    • Prereqs: application or ticket purchase; business casual is fine.
    • Equipment: smart notebook; one-pager on what you do and what you’re seeking.
    • Budget: premium conference pricing; consider employer sponsorship.
    • Low-cost alt: watch published talks afterward; host a local viewing club.

    How to do it (beginner steps)

    1. Pre-write “3 asks”: a deal ask, a learn ask, and a collab ask.
    2. Map sessions that directly inform those asks.
    3. Book 4 coffees with attendees whose work intersects yours.
    4. Document quotable insights (with speaker names, timestamps, and links for later).
    5. Publish your “3 applications” write-up within a week.

    Beginner modifications & progressions

    • Simplify: take a note-taker approach; write a public summary for your team.
    • Scale up: pitch a lightning talk, salon, or lab next year.

    Frequency, duration & metrics

    • Frequency: annual.
    • KPIs: 2 strategic intros, 1 co-project scoping call, 1 process improvement adopted.

    Safety, caveats & common mistakes

    • Don’t be a wallflower: many attendees are there to meet; introduce yourself.
    • Avoid vague notes: capture exact framing and links for future reference.

    Mini-plan

    • Before: DM three attendees to pre-align on meeting windows.
    • During: attend 5 sessions; take structured notes.
    • After: host a 30-minute debrief for your team.

    6) Enterprise GenAI Summit (IEEE Computer Society)

    What it is & why it matters
    A practitioner-first summit focused on how enterprises can safely deploy generative AI—architecture, governance, security, and value creation. It’s deliberately not academic or purely vendor-driven; it’s for teams shipping real systems.

    Core benefits

    • Clear patterns for building, evaluating, and securing GenAI solutions.
    • Case studies across industries (finance, healthcare, retail, manufacturing).
    • A talent pipeline for enterprise AI roles.

    Requirements & low-cost alternatives

    • Prereqs: none; product managers, engineers, security leads all benefit.
    • Equipment: laptop; architecture diagrams; a backlog of candidate use cases.
    • Budget: pass + travel; ask your employer to sponsor learning.
    • Low-cost alt: watch recap talks or join community working groups.

    How to do it (beginner steps)

    1. Pick one enterprise use case (e.g., claims triage) with a baseline metric.
    2. Attend sessions on retrieval, evaluation, and safety.
    3. Score tools against your guardrails (latency, cost, privacy).
    4. Book a clinic with a speaker for quick design feedback.
    5. Return with a 2-page RFC for a pilot and a 6-week plan.

    Beginner modifications & progressions

    • Simplify: focus on governance and evaluation first.
    • Scale up: run a cross-functional tabletop exercise for red-teaming.

    Frequency, duration & metrics

    • Frequency: annual + regional spins.
    • KPIs: one pilot greenlit, risk register drafted, evaluation dashboard live.

    Safety, caveats & common mistakes

    • Privacy & provenance: ensure your data flows and attribution policies are explicit.
    • Avoid tool sprawl: standardize early to reduce hidden costs.

    Mini-plan

    • Pre-event: choose one use case and baseline.
    • At event: attend evaluation + safety tracks.
    • Post: write an RFC and book stakeholder buy-in.

    7) Open-Source AI Summit (Abu Dhabi)

    What it is & why it matters
    A summit convening open-source AI communities, researchers, and policymakers to debate licensing, safety, and collaboration. It’s timely for teams betting on open models and community tooling.

    Core benefits

    • Perspectives across governance and open licensing.
    • Networking with maintainers, research labs, and startups building on open stacks.
    • A read on the future of “open vs. closed” dynamics.

    Requirements & low-cost alternatives

    • Prereqs: interest in open models or tooling.
    • Equipment: laptop; short README of your project; questions on compliance.
    • Budget: travel + pass.
    • Low-cost alt: follow livestreams and public write-ups; contribute to repos.

    How to do it (beginner steps)

    1. Identify a target repo to contribute to (docs count!).
    2. Attend sessions on licensing and safety; take notes on obligations.
    3. Join a birds-of-a-feather for maintainers to find mentorship.
    4. Make one contribution within a week (issues, docs, or tests).

    Beginner modifications & progressions

    • Simplify: start with documentation or tutorials.
    • Scale up: propose a governance doc improvement or evaluation harness.

    Frequency, duration & metrics

    • Frequency: annual.
    • KPIs: 1 merged PR, 1 maintainer relationship, 1 compliance checklist draft.

    Safety, caveats & common mistakes

    • License literacy: misunderstandings here can be risky—double-check before shipping.
    • Attribution: be precise on model cards and dataset sources.

    Mini-plan

    • Before: pick a repo and open an issue.
    • During: attend licensing + safety panels.
    • After: merge one contribution and share learnings.

    8) Paris Open Source AI Summit

    What it is & why it matters
    A European gathering focused on open-source AI and the broader policy moment around AI action at the highest levels. An excellent vantage for those building products in or for the EU and for anyone navigating evolving AI governance.

    Core benefits

    • Insight into open-source policy trends and public-private collaboration.
    • Connections to European startups and research groups.
    • A pulse on responsible deployment and standards.

    Requirements & low-cost alternatives

    • Prereqs: none; founders and engineers with EU exposure get extra value.
    • Equipment: compliance questions; product one-pager.
    • Budget: pass + travel.
    • Low-cost alt: track agendas, watch replays, and join EU open-source forums.

    How to do it (beginner steps)

    1. List your product’s EU touchpoints (data, users, partners).
    2. Book three conversations with legal/standards experts on obligations.
    3. Draft a lightweight conformity checklist post-event.

    Beginner modifications & progressions

    • Simplify: map only your top two regulatory exposures.
    • Scale up: join or launch a working group on evaluations or logging.

    Frequency, duration & metrics

    • Frequency: annual.
    • KPIs: 1 compliance checklist, 1 standards contact, 1 design change implemented.

    Safety, caveats & common mistakes

    • Don’t copy-paste policies: tailor compliance to your architecture and data flows.
    • Avoid jargon fatigue: focus on what’s enforceable now vs. aspirational.

    Mini-plan

    • Plan: product touchpoints doc.
    • Attend: policy + OSS tracks.
    • Ship: public model card update within 30 days.

    9) Generative AI Summit (AI Accelerator Institute – city series)

    What it is & why it matters
    A series of practitioner summits (New York, Boston, Berlin, Los Angeles, and more) with strong engineering and product focus—agentic systems, LLMOps, and applied patterns for deployment.

    Core benefits

    • Regional access if you can’t travel far.
    • Practical content by builders for builders.
    • Good density of startup and enterprise product folks.

    Requirements & low-cost alternatives

    • Prereqs: none; helpful to have a live or sandbox project.
    • Equipment: laptop; repo link; a short demo script.
    • Budget: day-pass plus local transit.
    • Low-cost alt: watch posted talks and join local meetups.

    How to do it (beginner steps)

    1. Pick one system pattern (e.g., agent + toolformer + memory).
    2. Attend sessions that align; ask about failure modes and evals.
    3. Run a post-event spike implementing one idea; document latency/cost.

    Beginner modifications & progressions

    • Simplify: implement a single new eval method (hallucination or safety).
    • Scale up: present a lightning talk on your spike results at the next city stop.

    Frequency, duration & metrics

    • Frequency: quarterly cadence across regions; pick one nearby.
    • KPIs: 1 spike shipped, 1 performance improvement, 1 new monitoring metric.

    Safety, caveats & common mistakes

    • Beware of demo bias: ask for failure cases and tradeoffs.
    • Keep costs visible: track tokens and context lengths.

    Mini-plan

    • Before: prep a 3-minute demo flow.
    • During: attend 2 architecture talks + 1 office hours.
    • After: write a spike report and open a lightweight design doc.

    10) Prompt Engineering Conference (London)

    What it is & why it matters
    A focused conference dedicated to the craft of prompt and system design, safety patterns, and evaluation. If you’re a creative, researcher, educator, or builder who cares about prompt reproducibility and reliability, this is your jam.

    Core benefits

    • Dedicated space for techniques, patterns, and anti-patterns.
    • Cross-pollination between creatives, data folks, and application engineers.
    • A place to compare notes on prompting frameworks, test harnesses, and style guides.

    Requirements & low-cost alternatives

    • Prereqs: none; bring a use case or creative brief.
    • Equipment: laptop; a prompt logbook; baseline eval script or rubric.
    • Budget: day-pass; split lodging with peers.
    • Low-cost alt: join online prompt-focused conferences or community salons.

    How to do it (beginner steps)

    1. Pick a prompt class (retrieval, creative writing, code generation).
    2. Define a measurable rubric (accuracy, readability, latency, cost).
    3. Collect 20 test cases and run A/B prompts before the event.
    4. At the conference, compare your framework with others; gather 3 ideas.
    5. Post-event, publish a mini-benchmark with your findings.

    Beginner modifications & progressions

    • Simplify: test 5 cases with a simple rubric.
    • Scale up: open-source your rubric or a reusable prompt pack.

    Frequency, duration & metrics

    • Frequency: annual (pilot year); supplement with monthly practice.
    • KPIs: 10% quality gain on your task, reduced cost or latency, reproducible runs.

    Safety, caveats & common mistakes

    • Leak prevention: don’t paste secrets into prompts.
    • Attribution: keep a changelog for creative prompts used in public work.

    Mini-plan

    • Before: build a five-prompt suite with tests.
    • During: attend safety + eval sessions.
    • After: write up results and share a gist.

    Quick-Start Checklist (attendee version)

    • Define your one-line outcome: e.g., “Leave with two collaborators and a refined workflow for X.”
    • Pick your “one big, one small” pair: one major conference + one community event.
    • Pre-book 5 micro-meetings: 15 minutes each; confirm time and place.
    • Pack a slim demo kit: 90-second reel or live demo, QR to portfolio, short bio.
    • Draft 3 questions per session: make participation intentional.
    • Set KPIs: conversations, pilots, content shipped, intros made.
    • Block post-event time: 72-hour follow-up window (calendar holds + templates).

    Troubleshooting & Common Pitfalls

    • “I attended everything and learned nothing.”
      You over-consumed. Pre-select 20% of the program and double down on hallway time.
    • “I met people but nothing came of it.”
      Your follow-ups were late or vague. Send a same-day summary with one clear next step.
    • “I got overwhelmed by tools.”
      Pick one technique to trial for 14 days. Compare against a baseline, not vibes.
    • “I don’t know how to talk about AI ethics credibly.”
      Be transparent about data sources, consent, and model limits. Share what you won’t do.
    • “I’m nervous about sharing unfinished work.”
      Bring a sandbox demo; mark it clearly as WIP. Ask for specific feedback (e.g., temporal consistency, typography, latency).
    • “Travel is too expensive.”
      Prioritize local/regional stops, use replays, and host a mini viewing group to keep momentum.

    How to Measure Progress (Turn Attendance into Outcomes)

    Core KPIs (pick 3–5):

    • Conversations logged: target 10–20 with names, roles, and next steps.
    • Qualified follow-ups: 3–5 with a concrete calendar invite sent.
    • Artifacts shipped: 1 new scene, feature, or prompt pack within 30 days.
    • Opportunity pipeline: pilots, mentorships, paid work tracked in a simple CRM.
    • Signal quality: inbound messages, invites to speak, newsletter signups.
    • Capability delta: measurable improvement vs. baseline (accuracy, cost, time).

    Simple scorecard template:

    • Sessions attended (was each aligned to your goal?)
    • People met (quality over quantity; did they match your ICP or craft goals?)
    • What you changed (tool, technique, process)
    • What you shipped (artifact + link)
    • One big lesson; one big decision

    A Simple 4-Week Starter Plan

    Week 1 – Choose & Prime

    • Pick one event from the list that fits your craft or role.
    • Define a single, testable outcome (e.g., “Prototype a localization pipeline”).
    • Build a one-pager with project context and your ask (collab, feedback, pilot).
    • DM 10 people; book 5 quick meetings.

    Week 2 – Prep & Practice

    • Assemble a 90-second demo or reel.
    • Draft 3 sharp questions for each target session.
    • Write two email templates (thank-you + pilot follow-up).
    • Set up a lightweight tracking sheet for conversations and tasks.

    Week 3 – Attend & Act

    • Stick to your pre-selected sessions.
    • Take timestamped notes; snap photos of slides (if allowed).
    • Honor your 5 micro-meetings; ask for one warm intro each.
    • Post a daily micro-recap to your network.

    Week 4 – Ship & Share

    • Publish a small artifact (scene, prompt pack, benchmark).
    • Send your thank-you notes and pilot proposals.
    • Update your scorecard; decide what to double down on next month.
    • Book the next event or community meetup immediately.

    FAQs

    1) How do I pick the “right” event if I’m brand-new to AI?
    Choose by craft first (film, fashion, product, policy), then by format (festival vs. practitioner summit). If you’re unsure, start with a fringe/community event or a city-series summit—lower cost, high signal.

    2) I can’t travel. Can I still get value?
    Yes. Many of these events post talks or host replays. Pair replays with a local viewing party and a 30-day “implementation sprint” so you translate ideas into output.

    3) What should I bring besides a laptop?
    A 90-second reel or demo, a one-page overview of your work, and a QR code to your portfolio. If you’re technical, include a short architecture diagram; if you’re creative, include mood boards and credits.

    4) How do I avoid “hype fatigue”?
    Pick one technique to trial, define a baseline metric, and run a two-week A/B comparison. Treat everything like an experiment with a hypothesis.

    5) I’m worried about ethics and credit in AI-assisted work.
    Be explicit: credit collaborators, document datasets, and state your tools. If you use models trained on public data, clarify what’s yours vs. what’s generated.

    6) How soon should I follow up with people I met?
    Same day if possible, within 72 hours at most. Include a specific next step (share a doc, schedule a call, swap assets).

    7) What if I’m an educator or student? Which event fits best?
    Fringe festivals and prompt engineering gatherings are excellent for teaching and curriculum development. Apply for student discounts and volunteer roles.

    8) Are there ways to participate without a finished project?
    Yes—volunteer, join open mics, enter 48-hour challenges, or present a WIP. Bring a clear ask for feedback or a call for collaborators.

    9) How do I justify the cost to my boss or client?
    Bring a short business case: sessions you’ll attend, people you’ll meet, and the artifact you’ll ship afterward. Promise a post-event debrief with actionable recommendations.

    10) I want to speak next year—how do I get on stage?
    Publish your learnings now. Propose a talk with data (before/after metrics), an open repo or prompt pack, and a clear narrative about impact and limits.

    11) Can I attend multiple events back-to-back?
    You can, but don’t dilute your outcomes. It’s better to nail one event with a shipped artifact than to sample three without follow-through.

    12) What’s the one thing most first-timers overlook?
    Blocking time after the event. Success lives in the 72-hour follow-up window when momentum is highest.


    Conclusion

    The AI culture scene is moving fast—but not so fast that you can’t catch up. Pick one event that maps to your craft and run the playbook: define a narrow goal, pre-book a handful of conversations, stay intentional during sessions, and ship something small within a week. Do that, and you’ll turn a single trip into a career inflection point.

    Copy-ready CTA: Pick one event, book two coffees, ship one artifact—start your zero-to-hero run today.


    References

    Claire Mitchell
    Claire Mitchell
    Claire Mitchell holds two degrees from the University of Edinburgh: Digital Media and Software Engineering. Her skills got much better when she passed cybersecurity certification from Stanford University. Having spent more than nine years in the technology industry, Claire has become rather informed in software development, cybersecurity, and new technology trends. Beginning her career for a multinational financial company as a cybersecurity analyst, her focus was on protecting digital resources against evolving cyberattacks. Later Claire entered tech journalism and consulting, helping companies communicate their technological vision and market impact.Claire is well-known for her direct, concise approach that introduces to a sizable audience advanced cybersecurity concerns and technological innovations. She supports tech magazines and often sponsors webinars on data privacy and security best practices. Driven to let consumers stay safe in the digital sphere, Claire also mentors young people thinking about working in cybersecurity. Apart from technology, she is a classical pianist who enjoys touring Scotland's ancient castles and landscape.

    Categories

    Latest articles

    Related articles

    Leave a reply

    Please enter your comment!
    Please enter your name here

    Table of Contents