Before you start, one shared vocabulary reminder so no symbol is unearned:
The two pictures below anchor the two worlds this bank tests — glance at them before you dive in.
The left idea is linear: the prediction line has a fixed slope βj, so one step right always adds the same amount up (additive). The right idea is logistic: the probability follows an S-curve, so the same one-unit push moves probability a lot in the middle and barely at all near 0 or 1 — that is why we report the multiplicative eβj on odds, not a fixed probability change.
This second figure shows the scaling trap: two features with the same real effect but different units get wildly different raw coefficients; only after dividing by σj (standardizing) do their bars become comparable.
Every answer is a full sentence of reasoning, not a bare verdict.
TF1. In linear regression, doubling a feature's coefficient means that feature is now twice as important.
False — importance also depends on the feature's scale and spread; a coefficient is dollars-per-unit, so a huge coefficient on a feature that barely varies (small σj) moves y^ very little. Compare βjσj (effect per standard deviation) instead. See Feature Scaling & Standardization.
TF2. In logistic regression, βj=0.8 raises the probability of "yes" by 0.8.
False — βj acts on log-odds, so it multiplies the odds by e0.8≈2.23; the probability change depends on where you start and is bounded by 0 and 1, so it can never rise by 0.8 across the board.
TF3. A logistic coefficient of 0 means the feature has no effect on the odds.
True — e0=1, and multiplying the odds by 1 leaves them unchanged, so the feature is inert (at least in this fitted model).
TF4. If βj<0 in logistic regression, the feature makes the outcome less likely.
True in direction — βj<0 gives eβj<1, an odds multiplier below 1, so the odds (and hence probability) fall as xj rises, other features fixed.
TF5. Two identical datasets fit with linear vs logistic regression will give the same coefficient interpretation.
False — linear βadds units of y; logistic β becomes eβ and multiplies odds. "Linear adds, logistic multiplies" — the same number means completely different things.
TF6. Ranking features by their raw coefficient magnitudes gives the same importance order as ranking by standardized coefficients.
False — raw magnitudes reflect the features' units (dollars vs years), so a feature can look big only because its unit is small; standardized coefficients (βjσj, effect per one standard deviation) put every feature on the same footing and can reorder the ranking entirely.
TF7. A statistically significant coefficient proves the feature causes the outcome.
False — regression measures association; an unmeasured confounder can drive both feature and outcome. Causal claims need a causal design, not just significance. See Correlation vs Causation.
TF8. Adding a strongly correlated copy of an existing feature won't affect the original feature's coefficient.
False — with two nearly-identical features (multicollinearity), the model can't decide how to split the credit, so both coefficients get huge variance and can even flip sign. See Multicollinearity & VIF.
TF9. The intercept β0 always has a sensible real-world meaning.
False — β0 is the prediction when every feature equals 0, which is often impossible (a house with 0 sqft). Centering features makes β0 the prediction at the average instead.
False — regularization deliberately shrinks coefficients toward 0 to stabilize them, so a regularized βj is biased and no longer the plain "per-unit effect"; it trades interpretability for stability. See Regularization (Ridge & Lasso).
Each prompt contains a flawed statement; the reveal names the flaw and repairs it.
SE1. "Price =50000+300⋅sqft, so βsqft=300 means adding a bedroom is worth $300."
The error swaps features — 300 is the effect of one extra square foot, holding bedrooms fixed, not the effect of a bedroom. Each coefficient describes its own feature only.
SE2. "The smoker coefficient is 0.8, so smokers have an 80% higher chance of disease."
The error reads log-odds as probability. 0.8 gives odds ratio e0.8≈2.23, a 123% increase in the odds (not probability). Probability change must be computed at a specific x via p=σ(log-odds).
SE3. "Income's coefficient is 0.00002 and age's is 500, so age matters far more."
The error compares across unmatched scales. Income spans tens of thousands, so its tiny coefficient can dominate; standardize (use βjσj) before ranking.
SE4. "We held all other features fixed mathematically, so in reality we can raise this feature alone."
The error confuses a math idealization with reality. Ceteris paribus is a thought experiment; if features are correlated, no real intervention moves one alone, so the isolated effect may be unobservable.
SE5. "eβ≈1+β always, so I'll skip the exponential."
The approximation only holds for smallβ. For β=2, 1+β=3 but e2≈7.39 — a huge error. Use eβ exactly unless β is near 0.
SE6. "The coefficient flipped sign after I added a feature, so my first model was buggy."
Not necessarily a bug — sign flips are the classic signature of multicollinearity. The new correlated feature stole shared explanatory power, redistributing credit. Check VIF before concluding anything is broken.
SE7. "βsqft=300 means every house gains exactly $300 per sqft, guaranteed."
The error treats an estimate as certainty. β is an estimated average slope with a confidence interval and assumes linearity holds across the range; it is not a per-house law.
WQ1. Why do we insist on the phrase "holding all other features fixed" for every coefficient?
Because βj is a partial derivative ∂y^/∂xj — it describes moving one axis while freezing the rest. Drop the phrase and you smuggle in the effects of correlated features that actually move together.
WQ2. Why does logistic regression use eβ instead of just β for interpretation?
Because the model is linear in log-odds, and undoing the log (log→exp) turns an additive change in log-odds into a multiplicative change in odds — the odds ratio eβ is the natural, scale-free way to report the effect.
WQ3. Why is comparing raw coefficient magnitudes for "importance" a trap?
Because a coefficient carries the feature's units: it's "y per one unit of xj". A feature measured in tiny units gets a big coefficient purely from unit choice, not from real influence. Only per-SD (standardized) effects are comparable.
WQ4. Why does βjstd=βjσj make features comparable?
Standardizing rescales so one "step" in each feature is one standard deviation (σj) of that feature. Since a σj-step in xj produces a βjσj change in y, every feature's effect is now measured in the same "one typical spread" unit.
WQ5. Why can correlated features give unstable, high-variance coefficients?
When features move together, many different coefficient combinations fit the data almost equally well. The fitting procedure has no unique way to split the shared effect, so small data changes swing the estimates wildly. See Multicollinearity & VIF.
WQ6. Why does regularization help when coefficients are unstable?
Ridge/Lasso add a penalty on coefficient size, forcing the model to prefer smaller, smoother solutions among the near-tied fits. This shrinks the wild swings from multicollinearity at the cost of a bit of bias — a trade for reliability.
WQ7. Why is a significant coefficient not enough to claim causation?
Significance only says the association is unlikely to be pure noise. It says nothing about direction of cause or hidden confounders that create the association without any causal link. See Correlation vs Causation.
EC1. What does a linear coefficient mean for a binary 0/1 feature (e.g. has_garage)?
"1 unit" is the whole jump from 0 to 1 (no garage → garage), so βj is the predicted y-difference between the two groups, other features fixed — there's no "half a garage".
EC2. In logistic regression, if βj is very large positive, what happens to the odds and to the probability?
The odds multiply by an enormous eβj, but the probability saturates toward 1 and cannot exceed it — so huge log-odds gains buy almost no probability change once you're already near certain.
EC3. What is the odds ratio when βj is exactlyln2≈0.693?
eln2=2, so a one-unit increase in xjdoubles the odds of the outcome — a clean benchmark for "this feature doubles the odds".
EC4. A feature has σj=0 (constant column). What happens to its standardized coefficient and why?
Standardization divides by σj, which is 0 — undefined. A constant feature carries no information and cannot have a meaningful per-SD effect; it should be dropped.
EC5. Two features are perfectly collinear (x2=2x1). What can you say about their individual coefficients?
They are not uniquely identifiable — infinitely many (β1,β2) pairs give the same predictions, so no single "the coefficient" exists for either until you remove the redundancy or regularize.
EC6. In logistic regression the two classes are perfectly separable by a feature (all y=1 above some threshold, all y=0 below). What happens to that feature's coefficient?
The likelihood keeps improving as the coefficient grows, so βjdiverges toward ±∞ and never settles — the fit fails to converge. The cure is regularization (a penalty bounds it) or recognizing the feature perfectly predicts the label.
EC7. All features are already standardized and one βj is still tiny. Does that reliably mean the feature is unimportant?
Mostly, but not if that feature is entangled with a correlated partner that absorbed its effect — collinearity can hide a real influence in a near-zero coefficient. Check correlations before declaring it useless.
EC8. The intercept comes out negative in a house-price model. Is the model wrong?
Not necessarily — β0 is the prediction at all-features-zero, which is out of range and physically meaningless, so its sign carries no real-world verdict. Center the features if you want an interpretable intercept.
EC9. In logistic regression a feature's coefficient is 0 but the feature is clearly related to the outcome in a plot. What's going on?
The relationship is likely captured by a correlated feature already in the model, or it's non-linear (logistic assumes linearity in log-odds). A raw scatter relationship can vanish once other features are held fixed.