Public Event Guide
A three-day attendee field guide built for networking-first conference use: when to prioritize sponsor-floor passes, when a session is actually worth stepping into, and how to leave Athens with cleaner follow-up notes instead of loose impressions.
Choose a mode
These modes are intentionally simple: they tell you whether to spend your next block in the hallway, at a booth, or inside a room.
Networking first
Use breakfast, coffee, lunch, and after-hours spillover as the real product. Rooms are fallback unless a talk is clearly stronger than the hallway.
Focus: Hallway density, sponsor overlap, recruiter routing, follow-up paths
Best fit: Best on Thursday, still useful at Friday lunch and Saturday breakfast
Booth and hiring first
Prioritize companies that combine visible sponsor presence with public hiring signal or strong architecture relevance, then use talks to reset between loops.
Focus: Sponsor logos, jobs-wall overlap, role-family signal, team routing
Best fit: Strongest on Thursday morning, still worthwhile on Friday breaks
Talks first
If you mainly care about AI, architecture, and career signal, Friday and Saturday carry the cleanest talk density without giving up every useful networking window.
Focus: AI coding agents, event-driven systems, architecture, career signal
Best fit: Friday all day and a lighter, more selective Saturday
First timer or short visit
Use the day cards below to choose one anchor window, one sponsor loop, and one fallback session rather than trying to consume everything.
Focus: Fast decisions, low overhead, easy mobile scanning
Best fit: Thursday lunch, Friday coffee plus one talk, or Saturday wrap-up
Day Plans
Official site positioning checked on 2026-04-23: 3 days, 60+ sessions, 1200+ attendees, and tracks spanning Architecture, Data and AI, Security, People and Culture, Programming Languages, Build and Deploy, and UI and UX
2026-04-23
The highest-density sponsor-floor and hallway day. Treat talks as fallback and use the afterparty if you still have unfinished conversations.
Strategy: Networking first, booth conversations second, talks last
2026-04-24
More balanced than Thursday. Keep the major networking windows, but this is the day where the right AI or architecture session can genuinely beat the hallway.
Strategy: Balanced networking plus stronger talk value
2026-04-25
Lower-volume, more intentional finish. Choose a few strong sessions, revisit the companies that still matter, and turn loose impressions into concrete notes before leaving.
Strategy: Selective talks, quieter follow-ups, cleaner wrap-up
Company Lens
The point is not to talk to every logo. It is to pick the conversation lane that actually matches the kind of work you want to learn about.
Use this lane if you want architecture authority, enterprise delivery scale, and cross-client transformation exposure rather than a single product track.
Good for governance, modernization, platform ownership, and architecture-led change inside regulated environments.
Best if you want product-scale engineering, platform depth, and hiring signal closer to operating teams than to transformation programs.
Useful when you want sharper signal around developer tooling, AI platforms, or security-heavy product environments.
Reality Checks
The official site shows sponsor logos but does not publish booth numbers or a floor plan, so booth-targeting logic still needs onsite validation.
Company weighting here uses a jobs-wall snapshot captured on 2026-04-22. Treat it as a dated hiring signal, not a stable live inventory.
Some presence calls are inferred from official sponsor-logo visibility rather than a text sponsor roster with booth metadata.
The live Thursday schedule checked on 2026-04-23 shows an afterparty from 18:30 to 20:30 on Thursday, while the FAQ still says Friday evening. Use the day schedule when those pages disagree.
Official links
The live schedule is the final source of truth for session timing. The guide adds routing logic and dated caveats so you can act quickly on the day.