Lumen Wiki — Company Overview & Onboarding Hub

Lumen is headquartered in Seoul, South Korea, and currently employs 26 people across engineering, product, design, and operations. Its core product is inventory-management software aimed at SMBs — businesses that need reliable stock tracking and supply-chain visibility without the overhead of enterprise tooling. The team is small enough that every individual contributor has direct impact, but large enough to have clear role specialisations: engineers work primarily in GitHub and Linear, product managers own the sprint backlog in Linear and collaborate with designers in Figma, and People Ops, IT, and Finance each run their own support channels on Slack. The Team / Who's Who page maps out these roles and explains where to reach each function. [Lumen Company Handbook & Onboarding.md]

The wiki is structured so that a new hire can move through it in a natural sequence, and so that any employee can jump directly to the policy or process they need. The Lumen Wiki — Home & Quick-Start page is the entry point — it hosts the quick-start kanban for new hires and links every section. From there, dedicated pages go deep on each subject:

• Starting out: Onboarding — Day 1 and first-week checklists, 30/60/90-day milestones.
• Getting set up: Tools & Access — every tool Lumen uses, who gets access, and how to request more.
• Staying secure: Security Policy — 2FA, password management, approved data stores, and lost-device protocol.
• Working together: Communication Guidelines — async-first norms, Slack channel conventions, and meeting hygiene.
• Scheduling and location: Hybrid Work & Working Hours — core hours, in-office days, and remote-work approval.
• Taking time away: Time Off Policy — annual leave, sick leave, and the Notion-based request flow.
• Spending money: Expenses & Company Card — thresholds, pre-approval flows, and the education budget.
• People and roles: Team / Who's Who — key roles and where to find them.

If something is missing or out of date, flag it to People Ops or post in #help-it. [Lumen Company Handbook & Onboarding.md]

The Onboarding page is the authoritative checklist for new hires, but the arc of the experience is worth understanding at a high level. On your first day, you arrive at the 3F lounge at 10:00 to collect your laptop and security key from People Ops. IT will have already provisioned Google Workspace, Slack, Notion, GitHub, and 1Password before you arrive — invites land in your company email. The very first tasks are security-oriented: save all passwords in 1Password, enable two-factor authentication on every account, and watch the security and data-protection training video, submitting the confirmation form before the day is out. Access to the staging and production environments is deliberately withheld until this training is complete and a team lead has approved the request — a gate that underscores how seriously Lumen takes data security. [Lumen Company Handbook & Onboarding.md]

The rest of Day 1 is social: lunch with your onboarding buddy (assigned by your manager before your start date) and a 13:30 introduction at the team standup. In the first week, you set up a recurring weekly 1:1 with your manager (Tuesdays at 16:00), read the Product Overview in Notion, begin codebase onboarding by working through the README and local setup, open your first pull request, and join the core Slack channels (#general, #eng, #product, #random, #help-it). [Lumen Company Handbook & Onboarding.md]

The 30/60/90-day framework gives new hires and managers a shared language for progress. By Day 30 you should have shipped your first feature-sized task independently. By Day 60 you should be comfortable with the on-call and deploy process. By Day 90 you should own one quarterly OKR. These goals are agreed with your manager and recorded in Notion. For the full checklist and goal table, see Onboarding. [Lumen Company Handbook & Onboarding.md]

Lumen's toolstack is intentionally focused. The Tools & Access page documents every system in one place, but the logic is simple: Day 1 tools are provisioned automatically by IT; anything touching live data requires an extra approval step. [Lumen Company Handbook & Onboarding.md]

Day 1 (automatic): Google Workspace (email, calendar, Drive), Slack, Notion, GitHub, and 1Password are all set up before you arrive. Role-gated: Figma edit access goes to Design and Product; everyone else gets viewer. Linear is available to engineers and PMs. Approval-gated: Staging and production environment access requires completion of the security training video, submission of the confirmation form, and explicit team-lead approval — only then does IT grant access.

If a tool or account is missing after Day 1, post in #help-it. [Lumen Company Handbook & Onboarding.md]

Security at Lumen is non-negotiable and starts on Day 1. The Security Policy page states the full requirements; the essentials are: every company account must have 2FA enabled, all passwords live in 1Password (no exceptions), and company data may only be stored in the three approved platforms — Google Workspace, Notion, and GitHub. Uploading company data to personal drives or unapproved cloud services is explicitly prohibited. Confidential data — customer records, revenue figures — must be shared only in private Slack channels. [Lumen Company Handbook & Onboarding.md]

If a device is lost or stolen, the required action is immediate: report it to #help-it so IT can trigger a remote lock. Security training is not a one-time onboarding formality; it is the gate that controls access to the environments where real data lives, making it structurally tied to every new hire's first day.

Lumen runs on an async-first communication culture, described in full on the Communication Guidelines page. The default for most questions, updates, and decisions is Slack or Notion — not a call, not a DM. Calls and direct messages are reserved for genuinely urgent matters. Every meeting must have a prepared agenda before it begins, and every decision made in a meeting must be recorded in Notion afterward, so the organisation's working memory lives in writing rather than in people's heads. [Lumen Company Handbook & Onboarding.md]

Slack channels are organised by function. #general is for company-wide announcements. #eng and #product are team-specific. #random is for casual conversation. #help-it handles equipment, accounts, and lost devices. #help-people handles HR, leave, and People Ops questions. Same-day sick leave is the one exception to the channel convention — notify your manager directly by Slack DM. [Lumen Company Handbook & Onboarding.md]

Lumen's work model is hybrid, with structure provided by core hours and a recommended in-office cadence. The Hybrid Work & Working Hours page has the full details. Core hours are 11:00–16:00 every working day — during this window all employees are expected to be online and reachable. Outside of those hours, schedules are flexible. [Lumen Company Handbook & Onboarding.md]

The office expectation is a minimum of two days per week, with Tuesday and Thursday recommended. If those days don't suit your role or circumstances, you can agree on alternative in-office days with your manager. Fully remote work for an entire quarter is possible but requires explicit manager approval and is not the default — it must be discussed and agreed in advance.

New hires should confirm their preferred in-office days with their manager during the first week, as noted on the Onboarding page. [Lumen Company Handbook & Onboarding.md]

The Time Off Policy covers all Lumen employees. Annual leave starts at 15 days per year, with one additional day accrued for each year of tenure, capped at a maximum of 25 days. Sick leave is 5 days per year; no documentation is needed for the first five days, but a doctor's note is required beyond that. [Lumen Company Handbook & Onboarding.md]

The request process runs through Notion: fill in the leave form, await manager approval, and receive People Ops confirmation. The one critical timing rule is that requests for three or more consecutive days must be submitted at least two weeks in advance. For same-day sick leave, DM your manager directly rather than going through the Notion form. Questions about leave go to the #help-people Slack channel. [Lumen Company Handbook & Onboarding.md]

The Expenses & Company Card page governs all spending on behalf of Lumen. The key threshold is 50,000 KRW: expenses below this amount can be spent and then reconciled in the monthly statement (cutoff: the 25th of each month) with a receipt attached. Expenses at or above 50,000 KRW require pre-approval — submit a Notion expense request, get manager sign-off, then Finance approval — before spending the money. [Lumen Company Handbook & Onboarding.md]

There is one self-serve exception: books and educational materials up to 200,000 KRW per person per quarter can be purchased without pre-approval. Keep the receipt and reconcile it in the monthly statement.

Company card holders must write a purpose note on every line of their monthly statement. Any undocumented line is attributed as a personal charge — Finance does not chase explanations, it simply reallocates the cost. [Lumen Company Handbook & Onboarding.md]

The Team / Who's Who page documents roles rather than named individuals (the handbook does not list employees by name), but the functional map is clear. People Ops handles onboarding, HR, and leave confirmation — reach them at #help-people. IT provisions accounts and manages environment access — reach them at #help-it. Your manager assigns your onboarding buddy, runs your weekly 1:1, and is the first approver for leave and remote-work requests. Your onboarding buddy is a peer contact assigned before your start date to help you settle in. Finance sits downstream of the expense approval flow in Notion. Team leads gate access to staging and production. [Lumen Company Handbook & Onboarding.md]