Coding interview coaches get paid for the one thing a real loop never hands back: a written account of where the signal dropped. A candidate sends a recorded mock, a solution stuck at 61 of 64 test cases or a design diagram, and you return timestamped notes, the complexity they should have stated and the patterns to drill. On Brillay the recording and diagram reviews are Custom Work, paid upfront, while one stuck problem pasted as text is a Paid Question.
If you're a senior or staff engineer who posts about interviews, you already know how this goes. A new grad sends a 40-minute screen recording of a mock and asks, "Be honest, would you hire me?" A mid-level engineer pastes a Python solution that exceeds the time limit on the largest inputs and asks what they're missing. Someone with a senior loop next week wants to know if their URL shortener design holds up when the interviewer asks about hot keys. None of that needs a live call. It needs your eyes, an hour of focus and a clear written verdict.
What are software engineers actually asking a coding interview coach for?
Most of the requests in your DMs come in a few repeat shapes, and each one maps to something you can sell:
- "Can you watch my mock?" A recorded practice round, from a peer mock or a timed solo attempt, where the candidate talks through a medium or hard problem. They want to know where they lost the interviewer: long silences, coding before clarifying constraints, no test cases at the end, no complexity stated.
- "Why is this wrong?" One problem, one solution, one bug or complexity question. Common ones: a dynamic programming state they can't define, a graph problem where they don't know whether to use BFS or DFS, an off-by-one in binary search, a heap solution they can't justify out loud.
- "How should I prep for this company?" A target company, a level, an interview date and a list of what they've done so far ("about 200 problems, half of a popular 150-problem list, never touched system design").
- "How would you scale this?" Senior candidates sending a diagram or write-up for a classic prompt: a rate limiter, a news feed, a chat system, a distributed cache.
- "Am I being down-leveled?" Questions about levels, team matching and what an offer one level lower really means. These usually go to people who worked inside big tech.
- "Can you refer me?" This is the one you don't sell. More on that below.
General interview coaching works with behavioral answers for any role. Your input is different: code, complexity analysis, whiteboard diagrams and back-of-envelope numbers. What candidates pay for is that you've sat on the interviewer's side of a software engineering loop and know what strong-hire signal looks like on a coding round.
Which offers should a coding interview coach set up first?
Start with two or three. A candidate should be able to read each scope in ten seconds, and the delivery time should fit a real interview calendar.
1. Written review of a recorded mock (Custom Work)
What it includes: you watch one recorded coding round, up to a length you state (45 minutes is a sensible cap), and write timestamped notes on the four areas most coding rubrics score: communication, problem solving, coding, and testing or verification. You add the time and space complexity they should have stated, a cleaner version of the key part of the solution, and the two or three problem patterns to drill next.
What the candidate sends: a link to the recording, the problem statement or a link to the public problem, the language they used, how long they gave themselves, their target level and interview date. Follower attachments are capped at 50 MB per file, so a long recording usually comes in as an unlisted video or a shared-drive link inside the brief.
Delivery: two to five days for a standard order. If you want to serve people with an onsite this week, publish a second listing with a 24-hour delivery time and a higher price.
2. One tricky problem explained in writing (Paid Question)
What it includes: one private question answered in writing, with up to two follow-ups. The candidate pastes the problem and their code into the question. You explain why it fails, which pattern it belongs to and how to say the approach out loud in an interview.
What to know: a Paid Question is plain text in both directions, so it suits pasted code and direct questions. Anything with a diagram, a recording or a résumé file belongs in Custom Work.
Delivery: you set the reply time, from 1–24 hours or 1–5 days. A lot of working engineers pick 24 hours so they can answer in the evening.
3. Target-company prep plan (Custom Work)
What it includes: a written plan for one company and level, running up to the interview date. It covers which problem patterns to prioritize, how to split time between coding and system design, which public practice sets to use, how to run timed mocks with a friend, and a day-by-day plan for the last week.
What the candidate sends: target company and level, interview date, current prep log, résumé, and which rounds are in the loop (phone screen, online assessment, coding onsite, system design, behavioral).
Delivery: three to five days.
Build the plan from public information and your own sense of what good looks like. It is not a list of the questions that company asks.
4. Feedback on a recorded behavioral answer (an add-on)
Big-tech loops still include a behavioral round, and candidates who grind problems often under-prepare "tell me about a time you disagreed with your manager." If you've run those rounds, a small Custom Work listing reviewing two or three recorded answers fits next to your coding offers.
You can read more about both offers on Custom Work and Paid Questions.
What should the candidate send you before you start?
A Custom Work listing tells the follower what you need, and the brief plus up to 5 files comes in with the payment. Because price, scope and delivery time are published before they order, you don't spend three DMs asking for the code. Write your "what I need" section like a checklist:
- The problem: a link to the public problem or the full statement, including constraints.
- Their code, in the language they'll actually interview in, with the complexity they claimed.
- For recordings: the link, plus the timestamps where they think they struggled.
- For design reviews: the diagram exported as an image or PDF, the requirements they assumed and their rough numbers (users, requests per second, storage).
- Context: company, level, round type and interview date.
- The one thing they most want to fix, such as "I always run out of time" or "I freeze when the interviewer adds a new constraint."
The last item matters more than it looks. It tells you which part of a 45-minute recording deserves the most of your hour.
How do you give mock interview feedback without getting on a call?
Write it the way you'd write interviewer notes, but aimed at the candidate and built to act on. A structure that works:
- A one-line read. Something like: "Problem solving was solid. Communication would be the concern: you went quiet for six minutes before writing code."
- Timestamped moments. "12:40 — you picked a hash map without saying why. Say the trade-off." "31:05 — you found the bug yourself; this is the strongest moment, keep doing it."
- The solution. What a strong answer looks like, its complexity, and the specific line or idea they missed.
- What to say out loud. Two or three sentences they can reuse: how to clarify inputs, how to state complexity, how to walk through a test case.
- What to drill next. Three named patterns, such as monotonic stack, interval merging or top-k with a heap, with public practice problems for each.
Your delivery can be a written note, up to 5 files (an annotated solution file, a marked-up screenshot) and links. If you think better on video, a screen-recorded walkthrough of 20 minutes or less can be part of the package. After you deliver Custom Work, the candidate can open a support conversation on the same order to ask about the delivery or report a broken link, and you reply there.
How long should delivery take when the onsite is next week?
You choose each offer's delivery time from 1–24 hours or 1–5 days, and five days is the maximum. There are no milestones and no built-in revision rounds. One order is one clearly scoped piece of work, finished and delivered.
That shapes how you sell longer coaching:
- A six-week prep program doesn't fit one order. Sell the first week's plan, or sell mock reviews one at a time. The candidate does the next mock and orders the next review.
- Rush orders are a separate listing. A "24-hour mock review" at a higher price serves the person whose onsite is in two days without turning your normal queue into a fire drill.
- Corrections need a written policy. You write a correction and revision policy that the follower sees before paying. State it plainly, for example: "If I misread your code or missed something in the brief, I'll fix it. A new solution or a second recording is a new order."
How much should you charge for a mock review or a single answer?
You set the price. Some common starting points for working engineers:
- One tricky problem explained (Paid Question): often $20–$40.
- Written review of a recorded coding mock: often $75–$150, depending on length and your level.
- Target-company prep plan: often $100–$200.
- System design diagram critique: often $120–$250 for senior and staff loops.
- Résumé review against big-tech hiring bars: often $60–$150.
Live paid mocks are usually priced as an hour of an engineer's time, because they take an hour of your calendar at a time that suits you both. A written review costs you about the same focus without the scheduling, so you can price a single-problem answer for the many candidates who would never book an hour. Rush delivery can reasonably cost more. What you earn depends on how many people already come to you. Nothing here is an income promise.
No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate.
The full breakdown is on pricing.
What can a coding interview coach never share or promise?
This trade has firmer lines than most coaching, and candidates will test them. Put them in your listing's "what's excluded" section so nobody pays expecting them.
- No guaranteed offers. Loops are noisy. Hiring committees, headcount, team match and the interviewer's day all play a part. You sell feedback and a better plan, not an outcome. Never write "land FAANG" or "pass guaranteed" in a listing.
- Never share confidential or leaked interview questions. If you've interviewed candidates at your company, its question bank, rubric details and any candidate's feedback are confidential. Teach the pattern with public problems instead.
- Respect interviewer NDAs. A buyer may ask "what did they ask you last month?" or "is this the question they use for phone screens?" The answer is no, every time. If a Paid Question asks for that, you can decline it.
- No help during a live interview or online assessment. You review practice. You never solve a timed assessment or sit on a call while someone interviews.
Candidates respect these lines more than you'd expect. Most of them want to pass because they're good, not because they saw the question in advance.
System design interview coaches: what changes for senior loops?
Your buyers are senior and staff candidates, and the input changes from code to a design: a diagram exported from a whiteboarding tool, a photo of a real whiteboard, a written design doc, or a recorded 45-minute answer.
What you critique is the shape of the answer:
- Did they scope requirements and ask about read/write ratio before drawing boxes?
- Are the capacity estimates (requests per second, storage per year) in the right order of magnitude?
- Do the API and data model match the access patterns?
- Are the trade-offs named: SQL or a key-value store, cache-aside or write-through, strong or eventual consistency?
- Where does it break? A sharding key that creates hot partitions, a single queue with no backpressure, a cache with no invalidation story.
Two offers fit well:
- Critique of a system design diagram and write-up (Custom Work). The candidate sends the diagram, the write-up and their assumed numbers as files, up to 5. You return a marked-up diagram, a written critique of the trade-offs and the three probing questions a strong interviewer would raise next. Three to five days.
- Answer to one "how would you scale X" question (Paid Question). Text only, which suits a focused question such as "my notification service uses one queue; how should I handle a 10x spike on New Year's Eve?" They get up to two follow-ups for "what if we also need ordering per user?"
The same rules apply: no guaranteed offers, and never confirm which design prompts a specific company uses.
Ex-FAANG interview mentors: how do you charge for advice without selling referrals?
If your headline says you used to work at a big tech company, people message you because of the logo. They want to know how leveling works, how team matching happens after the offer at some companies, what a hiring committee reads in a packet, and whether their résumé clears the bar.
Offers that fit:
- Résumé review against big-tech hiring bars (Custom Work). They send the résumé, target level and two job postings. You return line edits on impact bullets (scope, scale, measurable result), notes on which bullets read as the level they want and which read one level down, and a short summary. There's more on structuring this in selling a résumé review from your bio.
- Written answer on leveling and team matching (Paid Question). For example: "I have an offer one level below what I asked for; what usually decides that, and what can I ask the recruiter?"
The care rules are stricter here:
- Never sell referrals. A referral puts your name and your employer's process behind someone. It isn't yours to put a price on, and most referral programs forbid it. Say so in your listing.
- No confidential interview questions, including anything you saw as an interviewer or on an internal hiring tool.
- If you still work there, check your current employer's outside-work policy before selling anything on the side. Many companies require you to disclose outside work, and some restrict work related to hiring.
Followers see the public name you choose for your page, not your legal name. That's useful if you post under a handle, but it never replaces following your employer's policy.
What about tips, goals and personalized videos?
These are smaller, but they fit some coaches:
- Tips: the candidate who got the offer often wants to say thanks. A tip is a one-time thank-you with nothing for you to deliver.
- Goals: if you run a free monthly mock night for new grads or keep a free system design notes site online, a Goal with a progress bar lets people chip in. Every contribution is yours whether or not the goal is reached, and there's nothing to ship.
- Personalized Videos: a two-minute pep talk the night before an onsite, at a price and delivery time you set.
If interview-prep tools or course companies ask you about partnerships, the Brand Collaboration Inquiries form collects their budget, timeline and deliverables in a separate brand inbox, away from candidate orders.
How do you start when the DMs are already coming in?
- Create your page and choose the public name candidates will see.
- Publish two offers: one Custom Work mock review and one Paid Question for single problems.
- Write the scope, what you need from the candidate, what's excluded (referrals, company question lists, live assessment help) and your correction policy.
- Put the link where the asks happen: LinkedIn Featured, your X bio, your GitHub profile README, the Discord where you answer prep questions.
- Answer the next DM with the link: "Happy to look at it. Send the recording through here and I'll have notes back by Friday."
There's no follower minimum, so it works with the first junior who asks. Creators in 41 countries can get paid, and followers pay by card from anywhere, which matters when half your DMs come from candidates in other countries. For the step-by-step flow, see how it works. If people also ask you for code reviews outside interviews, the developers page covers that, and selling async technical interview feedback goes deeper on review formats. When you're ready, create your free Brillay page.
Frequently asked questions
Can I sell interview prep while I work at a big tech company?
It depends on your employer. Read your current outside-work policy before you sell anything, and disclose the work if the policy asks you to. Whatever it says, never use internal questions, rubrics or candidate data, and never offer referrals.
Do I need to run live mock interviews at all?
No. Everything here is asynchronous (no live call): the candidate records the mock or pastes the code, and you reply in writing within the delivery time you set. If someone specifically needs live practice, they can do a peer mock with a friend and send you the recording.
What does it cost to use Brillay?
There's no monthly fee and no paid tier. The platform fee only applies to orders that were actually paid, at the rates in the price section above, and card processing is separate.
What if the candidate still doesn't get the offer?
That can happen with excellent prep. No guaranteed offers is part of your listing from the start: you sell a review, a plan or an answer, and you deliver exactly that. A candidate who didn't pass usually comes back for a review of their next mock.
Can a candidate send me the exact question they were asked in a real interview?
Don't build your work on that. The candidate may have agreed not to share it, and passing it on helps no one. Teach the underlying pattern with a public problem instead, and decline any request for company question lists.
How do follow-ups work on a Paid Question?
The candidate asks one question and you answer in writing within your reply time. They can then send up to two follow-ups, such as "what if the input is a stream?" or "how would I explain that in 30 seconds?", and you answer each one in the same private thread.
Explore more