Land FAANG jobs - Group Cohort

Small group.
Full framework.

Each cohort runs with exactly 4 to 5 engineers — small enough for everyone to receive personalised attention, large enough to create the peer dynamic that accelerates preparation.

You will work through the same 12-week framework as my 1:1 clients — coding pattern mastery, system design fluency, behavioral story development, mock interview loops, and offer negotiation strategy. The difference is structure: group sessions replace individual sessions, and the cohort adds a dimension of peer accountability and collective problem-solving that private coaching cannot replicate.

Engineers preparing alongside peers who are at a similar level — facing the same challenges, targeting the same companies — consistently outperform those preparing in isolation. The accountability is built in. The competition is constructive.

What You’ll Get in 12 Weeks of Group Coaching

• 12 live group coaching sessions over 12 weeks

• Full diagnostic assessment in week one

• Resume and LinkedIn review with written feedback

• Behavioral story bank development — 8 STAR-P stories

• Coding pattern mastery across all 12 patterns

• System design sessions with group critique

• Two full mock interview loops per engineer

• Offer negotiation checklist

• Private cohort channel for async support

What's Included

Every pillar.
Every week.

01 · Live Group Sessions

One Session Per Week, Every Week

One 60-minute live coaching session each week covering the week's focus area. Every engineer participates — no passive watching. Rotating problem-solving and critique keeps every session active.

02 · Resume & LinkedIn

Profile Built for FAANG Screens

Written review of every cohort member's resume with specific, line-by-line feedback. LinkedIn headline, About section, and banner rewritten using the impact framework. All delivered in week two with a follow-up review in week four.

03 · Coding Mastery

All 12 Patterns, Practiced as a Group

Work through all 12 core coding patterns with group problem-solving sessions. Watch how peers approach and narrate problems — one of the most effective ways to improve your own communication under pressure.

04 · System Design

Group Critique, Real Trade-offs

Each engineer designs systems and presents to the group. Group critique surfaces blind spots faster than any solo practice. Defending your decisions to five sharp engineers is the closest simulation to a real onsite you can get.

05 · Mock Interviews

Two Full Loops Per Engineer

Each engineer completes two full mock interview loops — one in week eight, one in week ten. Cohort members also observe each other's mock sessions (with permission), compounding the learning for the entire group.

06 · Peer Accountability

The Advantage of Shared Pressure

A private cohort channel where engineers share progress, flag blockers, and hold each other accountable between sessions. Preparing alongside engineers at your level — facing the same challenges, targeting the same companies — accelerates everything.

The Curriculum

12 weeks.
Structured to deliver.

One live session per week throughout. The group moves together — one phase at a time.

Phase 1 · Weeks 1–3 · Foundation & Diagnosis

Week 1

Individual Diagnostics & Group Kickoff

Each engineer submits a resume, a written behavioral story, and completes an async coding assessment before the first session. Week one sessions cover diagnostic findings, preparation principles, and the group's collective target landscape — companies, levels, timelines.

Week 2

Resume & LinkedIn Workshop

Session one: group resume workshop — each engineer presents their current resume, group gives a structured critique using the impact formula. Session two: LinkedIn and personal brand — how to position yourself to attract FAANG recruiters rather than chasing them.

Week 3

Coding Patterns 1–6 & Thinking Out Loud

Sliding Window, Two Pointers, Fast & Slow Pointers, Merge Intervals, Cyclic Sort, and In-Place Linked List Reversal. One pattern per session segment. Engineers solve problems while narrating — the group provides feedback on both solution quality and communication clarity.

--

Phase 2 · Weeks 4–7 · Technical Depth

Week 4

Coding Patterns 7–12 & Pattern Recognition Drills

Tree BFS, Tree DFS, Two Heaps, Subsets/Backtracking, Modified Binary Search, and Top K Elements. Emphasis on pattern recognition speed — engineers identify the pattern from the problem statement before touching code. Group timed drills surface recognition gaps fast.

Week 5

System Design Fundamentals

Core vocabulary: load balancers, caching, sharding, message queues, CDNs, and rate limiting. The clarify-first framework. Engineers design a URL shortener — each person presents their design, the group critiques the trade-offs. Instant feedback from 5 different engineering perspectives.

Week 6

System Design — Scale & Complexity

Twitter feed, distributed storage, and notification service designs. Rotating presentations — each week, a different engineer presents first. The group learns to defend under real questioning. This session replicates the adversarial dynamic of a senior staff interviewer more accurately than any solo practice.

Week 7

Behavioral Story Workshop

Each engineer presents two STAR-P stories to the group. Group identifies vague language, missing metrics, and team-speak in real time — the most efficient way to sharpen behavioral answers. Engineers leave with 8 refined stories mapped to their target company's values.

--

Phase 3 · Weeks 8–10 · Mock Interview Loops

Week 8

First Mock Interview Loop — All Engineers

Each engineer completes a full mock loop: coding, system design, and behavioral. Sessions run across both week eight sessions. Observers watch with structured feedback forms — learning from every session, not just their own. Full debrief in session two.

Week 9

Targeted Remediation — Group Focus Areas

Based on the week eight mock performance, the group identifies collective and individual gaps. Shared weaknesses receive group session focus. Individual gaps receive targeted async coaching in the cohort channel. Advanced coding and system design problems for engineers ahead of baseline.

Week 10

Second Mock Interview Loop — All Engineers

Second complete loop with harder problems and stricter evaluation criteria. Comparative performance review against week eight baseline — engineers see their trajectory clearly. By this point, the cohort dynamic creates constructive competitive pressure that individual prep cannot replicate.

--

Phase 4 · Weeks 11–12 · Offer Strategy & Launch

Week 11

Application Strategy & Interview Day Protocol

Targeting strategy — which companies, which teams, which roles. Referral outreach templates and warm connection strategy. Pre-interview protocol and mental preparation. Engineers go live with applications this week. Group accountability check-ins ensure everyone executes.

Week 12

Offer Negotiation & Cohort Graduation

Full negotiation basic — base, RSU, signing bonus, refresher.

Direct referral to top tech companies for all cohort graduates. Program debrief. Ongoing cohort support channel stays active until every engineer receives and accepts their offer.

Is This For You?

Right fit.
Wrong fit.

Group coaching is for you if...

• You have 3+ years of professional software engineering experience

• You are targeting L4, L5, or L6 at a FAANG or top-tier tech company

• You learn well in a structured group and value peer accountability

• You want full FAANG preparation at a more accessible price point

• You can commit 15–20 hours per week for 12 weeks

• You can attend live sessions on a consistent weekly schedule

Choose 1:1 coaching instead if...

• You want every session built entirely around your specific situation

• Your schedule cannot accommodate fixed group session times

• You prefer complete privacy throughout your preparation

• You want maximum flexibility in session timing and content

• You are targeting a very specific niche role or company

• You want direct 1:1 access to Emran for every session

To Join the Cohort

Four requirements.
Non-negotiable.

3+ Years Professional Engineering Experience

The cohort is designed for experienced engineers, not new graduates. Every member needs to bring substantive engineering experience — real systems, real scale, real impact — to make the peer critique and group sessions genuinely valuable for everyone.

Independent Problem-Solving Baseline

You can solve Easy LeetCode problems within 15 minutes without external help. The cohort starts from this baseline — we build from here, not toward it. Engineers below this baseline are not ready for group coaching and will struggle to keep pace with the cohort.

15–20 Hours Per Week Available for 12 Weeks

Group sessions run twice per week. Between-session preparation, problem practice, and story development require additional time. The cohort moves together — consistent participation is a requirement, not a suggestion. Missing sessions affects the group, not just yourself.

Able to Receive and Give Direct Feedback

Group coaching requires engineers who can receive honest critiques of their work and give constructive, specific feedback to peers. If you cannot comfortably present your resume, code, or system design to a group and hear direct feedback on it, the 1:1 program is the better fit.