Blue Lake

Candidate Data Room

Packet I for the Blue Lake Revenue Operator Academy. Read this as a business operator, not as a resume applicant.

The Business

Blue Lake is the B2B side of the operating system. HomeEasy is the B2C renter-demand surface. The operator role exists because AI collapses the old separation between sales, operations, software, and analysis.

This cohort is academy-style and entry-level. Blue Lake is not taking experienced or lateral hires for this role at this time because operators are trained into a specific method of working from the ground up.

Submit Response Technical Screen
Demand Renter intent enters through consumer channels and must be qualified, followed up, and matched.
Supply Buildings, owners, managers, policies, availability, commissions, and counterparties determine what can actually close.
Revenue The business makes money when qualified demand converts into payable transactions and the commission path is not lost.
AI layer Agents carry volume, retrieve context, decompose work, alert humans, and make missed next actions hard to ignore.

What To Study

Founder pattern

Look for the operating style: direct ownership, rapid iteration, sales plus systems, and willingness to touch the messy edge of the work.

Academy path

This is a build-from-the-pipeline role. Senior experience can be impressive and still be outside the current cohort.

Unit economics

Work out where a renter lead becomes valuable, where it dies, and where collections or follow-up can leak revenue.

Agentic leverage

Think about the continuous captain model: context, decomposition, sub-agent work, observability, and escalation.

The Assessment Path

This public room is Packet I. Later packets are released only after the candidate has earned them. That keeps the burden on the candidate while protecting internal scoring guides, answer keys, and production context.

The path is not a shortcut for experienced hires. Candidates advance by completing each packet exactly, not by substituting a resume or portfolio for the assigned screen.

1
Public

Packet I: business read

Study Blue Lake/HomeEasy, submit a point of view, technical evidence, revenue thesis, first fix, CT overlap, and start timing.

2
Email release

Packet II: build screen

Build a small Revenue Captain service from messy candidate/source/event records with tests, idempotency, reason codes, and a walkthrough.

3
Live, no AI

Technical fundamentals

Reason through data structures, databases, concurrency, debugging, and system design without a model writing the answer.

4
Judgment

Commercial simulation

Triage candidate, source, renter, building, and revenue evidence; decide the next action and explain what information is missing.

5
Paid

Sandbox trial

Complete a small audited work product against sanitized operating data before touching any real production workflow.

6
Decision

Offer, park, or recycle

Finalists move to role alignment. Promising candidates who are not ready are remembered for future cohorts.

Files In This Room

These are the public Packet I files. They are candidate-safe and intentionally sanitized. Real applicant history, employee files, WhatsApp exports, answer keys, and internal scoring guides are not public.

Open Manifest Download Packet ZIP
01 Business BriefBlue Lake / HomeEasy model 02 Assessment Pathsix stages 03 Packet I Questionsapplication prompts 04 AI And Integrity Policyallowed use and live test 05 Packet II Build Previewtechnical screen shape applications.jsonfictional sample records events.jsonfictional event ledger school_routes.jsonfictional source routes

Packet I Submission

Your submission is not judged by polish. It is judged by whether it shows independent technical and commercial thought.

Answer these in your own words

  1. What is Blue Lake / HomeEasy, and what does the operator actually own?
  2. Where does the business make money?
  3. What would you build, instrument, or fix first?
  4. What technical evidence proves you can own systems rather than only describe them?
  5. What would you need to inspect before trusting any funnel metric?

AI Policy

Use AI for authorized building work. Do not use it to replace studying, to summarize material you did not understand, or to manufacture correspondence with us.

How this is tested

  • Live no-AI technical fundamentals screen.
  • Follow-up questions about your own submission.
  • Code and architecture review under changing constraints.
  • Production-style debugging from raw records before metrics.