Lumos Assessment Center Tracks https://lumostech.org/
This repository has been archived on 2026-10-26. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
  • Python 72.2%
  • JavaScript 18.3%
  • HTML 9.5%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Rubem Passos Oliveira 659da1caec Changed link
2026-10-24 17:10:03 +02:00
1-zenith Welcome to Lumos AC! 2026-10-24 11:59:01 +02:00
2-omnimart Welcome to Lumos AC! 2026-10-24 11:59:01 +02:00
3-crm Welcome to Lumos AC! 2026-10-24 11:59:01 +02:00
README.md Changed link 2026-10-24 17:10:03 +02:00

Lumos Assessment Center — 26W

How It Works

  1. Choose one track (1–3) below and work on it following the time schedule.
  2. Each track is self-contained: its brief and all materials live in the corresponding folder (/1-zenith, /2-omnimart, /3-crm).
  3. Submit your results according to the schedule.

The Tracks

# Track Working time Presentation Folder Brief
1 Zenith Active Solutions: External Strategy Audit — a consulting-style case: process a raw data room, identify the structural leaks destroying a D2C brand's margins, and present a data-backed turnaround strategy. Covers 4 sub-tracks (data engineering, business intelligence & strategy, marketing & brand, UX/UI) — your team should cover at least 2 of them. 12:30–14:45 & 15:45–17:00 (3h15m total) 17:00–18:00 (10–12 slides) /1-zenith 1-zenith.md
2 The OmniMart Crisis — a cross-functional task force challenge: pick one of three operational crisis areas (food waste, logistics bleed, eco-friendly slump) at a supermarket network and design + prototype a full-stack digital product that solves it, with a business case and a final pitch. 12:30–14:45 & 15:45–17:00 (3h15m total) 17:00–18:00 (5–7 min + 3–5 min Q&A) /2-omnimart 2-omnimart.md
3 Customer Relationship Management — a real problem at Lumos: design a CRM system to track partner interactions and long-term deliverables, balancing effectiveness against maintenance friction. Includes an anonymized sample of real Lumos interaction notes, a baseline deliverable set, and an MVP + presentation. 12:30–14:45 & 15:45–17:00 (3h15m total) 17:00–18:00 (5–7 min) /3-crm 3-crm.md

Tip: Read the brief in your chosen track carefully — each one lists its own deliverables, expectations, and (where applicable) suggested tools.

Time Schedule

Start End Day plan
11:00 11:30 Applicants arrive
11:30 12:15 Lumos & tracks introductions
12:15 12:30 Break + time buffer
12:30 14:45 First working session + interviews
14:45 15:30 Lunch
15:30 15:45 Time buffer
15:45 17:00 Second working session + final interviews
17:00 18:00 Presentations & Q&A
18:00 18:30 Closing words

Per track: working time is 12:30–14:45 and 15:45–17:00 (3h15m total, excluding breaks); presentations take place 17:00–18:00.

Questions

If you have questions about a track, reach out to the Lumos organizing team (see the track briefs for track-specific guidance).

Submission

https://tally.so/r/6D8l5P