What should an engineering intake cover, and what is engineering pay made of?

What should an engineering intake cover, and what is engineering pay made of?

An engineering intake has to produce five facts: the systems the new hire touches in week one, the level defined as scope, the technologies that are load-bearing, the shape of the interview loop, and the pay band. Everything else in this module builds toward that list. Decoding the hiring manager's phrases turns their words into the first fact. Seniority as scope covers the second. The week-one test sorts the third. The loop audit covers the fourth. This lesson closes the set with the fifth: what engineering pay is made of, and which non-cash facts move the people the req is for.

What is an intake meeting for?

An intake meeting is the conversation where a recruiter and a hiring manager agree what a req actually needs before sourcing starts. The meeting itself is old ground for anyone who has carried reqs for a decade. What changes on an engineering req is the raw material. A sales intake produces facts the recruiter can already evaluate: quota history, deal size, territory. An engineering intake produces facts about systems, and the manager describing them assumes a shared vocabulary the way a lawyer assumes you know what a deposition is.

The earlier lessons in this module exist so that assumption holds. A manager who says the team is breaking up the monolith has named the actual work. A manager who wants "a strong senior" has named a scope of ownership that means something specific at their company and something different everywhere else. The intake is where those translations happen live, with the one person who can confirm them.

Which facts does the meeting have to produce?

Five, and each maps to a lesson in this module.

The week-one systems. What does this person touch in their first weeks, and what happens to the team if that work stalls. This is the fact that separates a must-have from a nice-to-have: a technology is load-bearing when the week-one work fails without it, and decoration when it appears on the job description out of habit.

The level as scope. A title is a label; scope is a fact. Does this person own a feature, a system, or a direction shared across teams. One company's senior is another company's mid, so the useful output is the scope sentence, never the title.

The load-bearing technologies. The two or three items on the stack that the week-one test keeps, and the longer list it demotes. A req that survives this cut stops describing three people stapled together.

The loop. Which stages, what each one measures, how long the whole thing runs. Covered next.

The band. The approved pay range for the level, plus the equity structure behind it. Covered in the second half of this lesson.

A req that leaves the meeting with all five facts written down can be sourced against directly. A req missing any of them produces the familiar failure: a search that technically matches the posting and misses the job.

How does the level get pinned down?

By trading titles for scope sentences. The manager says "senior;" the useful follow-up territory is what the person owns. A senior who owns one service alone, handles its on-call, and makes its design calls without review is one shape. A senior who leads two other engineers and answers for a whole product area is another. Both are real seniors at their companies. They are different hires, at different prices, findable in different places.

The years-of-experience shortcut fails here for the reason the JD rewrite lesson covers: years measure calendar time, and scope measures growth, and the two drift apart fast. Pinning the level to a scope sentence in the intake gives the search a target that titles and year counts cannot give it. It also sets the band, since companies price levels, and the level is the scope.

How does the loop get settled in the same meeting?

The intake is the one moment the loop is cheap to change, so the audit from the loop lesson belongs inside it. The facts to capture: which stages the loop has, what each stage measures, who runs each one, and total elapsed time from first call to offer.

Two loop facts matter most at intake. First, whether each stage measures something the week-one work needs. A loop that tests algorithm puzzles for a role that is integration work on an existing system filters for the wrong strength, and the intake is where that mismatch gets caught. Second, the clock. Strong engineers run parallel processes and take the offer that arrives while the slow loop is still scheduling round four. A manager who hears the elapsed-time number out loud in the intake often shortens the loop on the spot.

What is engineering pay made of?

Total compensation is base salary plus equity, plus a bonus at some companies. Engineers, hiring managers, and offer letters all reason in total compensation, so the intake band has to be stated in it too.

Base salary works like base salary everywhere.

Equity is ownership in the company, and at technology companies it is a large share of the total, often a third or more at the big public ones. It comes in two main forms. RSUs, restricted stock units, are shares granted to the employee that become theirs over time. A typical grant vests across four years: the employee earns a quarter of it per year, frequently with a one-year cliff, meaning nothing vests until the first anniversary and then it flows monthly or quarterly. RSUs are the standard at public companies, where the shares can be sold as they vest, which makes them close to cash. Stock options are the startup form: the right to buy shares later at a fixed price. Options can be worth a great deal or nothing, and engineers who have been through a failed startup price them skeptically.

Bonus is an annual cash payment, common at large companies and finance, rare at startups.

One more piece completes the picture: the refresh, an additional equity grant given to an existing employee, usually annually. Refreshes are why a strong engineer at a big company gets more expensive to recruit every year they stay: their old grants are still vesting while new ones stack on top. The comp a candidate walks away from includes those unvested layers, and why engineers change jobs anyway is its own lesson.

What is a band, and why is it the band?

A band is the pay range the company has approved for one level in one location. It exists to keep pay consistent across everyone at that level, which is why a manager cannot stretch it for one candidate without touching the pay of the whole team.

This is the fact that makes the intake's level conversation double as its money conversation. The band attaches to the level, and the level is the scope. A req scoped as "owns one service" prices at one band; the same posting rescoped as "sets direction across teams" moves to another. When the market for the skills exceeds the band, the fix runs through the level or through the req itself, and making that case upward is a later station on this path.

Which non-cash levers actually carry weight?

Five, and the intake should capture each one, because they decide most offers that are close on pay.

The stack. Engineers treat their tools as part of the job itself. Modern tooling and room to modernize old tooling both count; the intake should establish which one this req honestly offers.

The scope. The same fact that set the level also sells the role. Ownership of a real system, or a genuine step up in scope, moves candidates that a matching salary alone leaves flat.

The on-call load. How often this person carries the pager, and how often it fires overnight. Engineers trade meaningful salary against this number, in both directions.

The remote arrangement. Stated precisely: fully remote, hybrid with named days, or in-office. Engineers had remote work early and widely, and vague language here reads as a policy about to tighten.

The say. How much input engineers have in what gets built, from how work gets chosen and planned to whether their technical objections change decisions. This one is hard to fake and travels by reputation.

A runsheet that leaves the intake carrying the five facts and the five levers is the finished version of everything this module built. The job description becomes the easy part: it is the runsheet, written for the candidate.