What this is, and what it is not
Some of these answers are not the ones you were hoping for. They are the ones that survive an interview. Nothing on this page claims something the product does not do.
Is this a real job?
No. Wavelength does not exist, and neither does the second company you move to after day twenty — we are not printing its name yet. There is no employer, no wage, no contract, and every colleague you meet at either of them is a model. We are not a staffing agency, and no job is promised at the end of it.
What is real sits on the other side of it: the repository is a real repository in your own GitHub account, the code is code you wrote, the pull requests are real pull requests, and the reviews are written against the diff you actually pushed. The company is the simulated half. The work is not.
Do I need to be able to code already?
Some, yes. Day one has a short screening question, and if you have not written JavaScript before you are told so on day one, plainly, with somewhere to go and learn it (javascript.info) and an open door back afterwards.
This is not a course that teaches programming from zero, and we will not pretend it is one. It assumes you can write a small program and get stuck in the ordinary ways. What it adds is the part nobody can give themselves: a ticket you did not choose, a deadline you did not set, and somebody senior reading your diff line by line.
What do I need?
A phone for the office — the standups, the reviews, the meetings, the people. Your own computer for the work: the code is written in your own editor and pushed from your own machine, and that part never waits on us. And a GitHub account, because the repository is created inside it.
Whose repository is it?
Yours. When you connect GitHub we generate a repository from a starter template in your own account, under your own username. You then install our GitHub App on that one repository — the link we hand you is scoped to it, and you can uninstall it whenever you like.
The App files the issues, opens one pull request, and posts the review comments. It never sees your GitHub password, and the token from the sign-in is used to create the repository and is not stored anywhere. The repository is yours whether you finish, stop, or never come back. You can delete it yourself, and we could not stop you.
Is my code public?
Yes. The repository is created public, so anyone with the link can read it and search engines can index it. That is deliberate: a record nobody is allowed to read is not evidence of anything.
It is your repository, so its visibility is yours to change in GitHub's own settings. Know what it costs you, though — the deployed page, the links in your Work Story and the whole point of having a record all assume a repository a stranger can open.
Is the AI going to write my code for me?
No. Nothing we run writes code into your repository, with exactly one deliberate exception: on day seven a colleague opens a pull request containing a page of notes with two mistakes planted in it, because that day the job is to review somebody else's work instead of your own. Otherwise the App only files issues and posts review comments. Everything in the code is yours, minus the starter template the repository begins from.
Whether you use AI tools while you work is your business, and we assume you do — that is how the job works now. It changes nothing about the review: what gets read is the diff, and the questions come from the lines that are in it.
Can I put this on my CV?
Not as a job. Everybody wants a yes here, so here is the whole answer rather than a comfortable half of it.
Erfara is not employment. Wavelength is not a company that existed, we were never your employer, and there is nobody to phone for a reference. A line in your work history reading "Engineer, Wavelength" is a false statement about your career. It reads as one, it collapses at the first follow-up question, and it costs you the interview it was meant to win. We will never suggest it, and we will say so plainly to anyone who asks us to confirm it.
What you can do is show the work, and that is not the consolation prize. Most junior applicants have a claim. You have a public repository with merged pull requests and line-anchored reviews in it, which any technical reader can check in about a minute.
- The repository, linked from anywhere you like. It is your code.
- Your Work Story page, described as what it is.
- The pull requests and the review threads — the actual evidence.
- A projects, training or personal-work section, however you name the part of your CV that is not employment.
- In a cover letter or an interview, in your own words: what you built, what the review caught, what you did about it.
- Not under employment, work history, or experience at a company.
- Not with Wavelength as an employer, and not with dates that look like a contract.
- Not "worked in a team of engineers". Your colleagues were models. Saying so out loud is not a weakness — it is the only version that survives the next question.
- Not as a reference, and not as a referee. There is nobody to call.
- Not as a certificate or a qualification. We do not issue one.
- Not with any title from the ladder — not Engineer II, not Senior Engineer. Those are levels inside a simulation, not a seniority anybody conferred on you.
- Not with a second employer's name. There is one, it is fictional, and it does not belong on your CV.
Say "I did a simulated first year at an AI company — here is the repository, here are the reviews" and a technical reader clicks the link. That link is what the line on your CV is for.
What do I actually have at the end?
after day twenty — the Wavelength year
- The repository. Commits, branches, merged pull requests and review threads, public, in your account.
- What you built, on the web. The repository is set up to publish through GitHub Pages, and the design review in week four reads the page you actually deployed.
- A performance review, written against your record: the commits, the pull requests, the reviews. Not against a feeling about you.
- A reference letter from Nadia, the engineer who reviewed your code all year.
- A Work Story — a page built from your GitHub record, which you publish or do not.
About the letter, since it is the part people over-read: Nadia is a character, the letter is written by a model in her voice, and it cites your record rather than praising you. It is not a reference from anyone who employed you, and nobody can call her. Read it for what it says about the work. Do not hand it to an employer as a reference.
days twenty-one to forty
- No letter, no badge, no certificate, no title. Nothing is minted at the second company, and that is deliberate.
- More real repository history, and more entries on your Record — including the pages that were read out to you and the words you wrote yourself.
That is a selling point rather than an apology: it is the proof the product does not inflate. If a second twenty days produced a second certificate, the first one would be worth less.
Who sees my Work Story?
Nobody, until you press publish. From day six it sits in your Record as a draft — a draft is rendered for you and stored nowhere.
When you publish it, it becomes a public web page at a hard-to-guess address. It carries your real name, the product name, counts read from your repository, a link to the repository — which means your GitHub username — and any highlights you wrote, in your own words. There is no password on it, and nothing on the page currently asks search engines to stay away. Treat it as public, because it is.
Recruiters with an invite code can search published Work Stories and ask for an introduction. That request is written down and a person routes it to you; nothing is sent automatically, and we do not sell contact details. The review comments in your repository are posted by our GitHub App, so GitHub shows the App as their author rather than Nadia — the Work Story says so on the page rather than letting you discover it later.
There is no unpublish button yet. Write to hello@erfara.ai and a person takes the page down.
How long does it take?
Forty office days: twenty at Wavelength, then twenty more at a second company on two higher levels. An office day is a sitting — the meetings, the reviews, the decisions — plus the code you write in between at your own desk, which takes as long as it takes. The Wavelength year is a complete ending on its own; the twenty after it are optional and hand over no documents.
The office opens six hours after you finish a day. So the Wavelength year cannot be compressed below roughly five days of wall clock however keen you are, and the full forty below roughly ten. Most people spread them across weeks. That is the point: a year that takes an evening is not a year.
What does it cost?
Nobody has been charged anything. The build in front of the first cohort cannot take a payment at all, and the card where the price would be says so out loud.
What we intend to charge is $149 for the whole ladder — all forty office days — or $19 a month, with day one free before any of it. If that number changes you will see the new one before you are asked for it. Everything you build stays yours either way.
What happens if I stop?
Nothing. There is no streak to lose, nothing expires, and we delete nothing because you went quiet. The year waits where you left it.
One warning, because it is the true one: the year lives on your device. This build has no accounts, so if you delete the app or lose the phone, the year is gone and we cannot restore it. Your repository is not affected — that is on GitHub, in your account, and it stays there.
How do I get in?
The waitlist. Cohorts are small because a person reads what comes out of them, and we would rather run a small one properly than a large one badly. One email when your cohort opens.
Something here not answered, or answered wrongly? Write to us — a sentence on this site that is not true is the most useful mail we get.
Join the waitlist