How do you like to be managed, sample interview answers, manager questions to ask, and a worksheet for engineering teams. According to iSilta's 2026 survey of 146 organizations, respondents estimate 44% of current people managers had no formal leadership training before managing anyone. Use this guide to move from generic advice to week by week manager habits on engineering teams.
What does “how do you like to be managed” really mean?
What does “how do you like to be managed” really mean is a manager practice that turns how do you like to be managed into predictable team behavior, not a poster on the wall.
Engineering managers win when how do you like to be managed is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, respondents estimate 44% of current people managers had no formal leadership training before managing anyone. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, how do you like to be managed interview question and sample answer intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how do you like to be managed easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how do you like to be managed shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How should candidates answer in interviews?
How should candidates answer in interviews is a manager practice that turns how do you like to be managed into predictable team behavior, not a poster on the wall.
Engineering managers win when how do you like to be managed is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, respondents estimate 44% of current people managers had no formal leadership training before managing anyone. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, how do you like to be managed interview question and sample answer intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how do you like to be managed easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how do you like to be managed shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
What questions should managers ask instead of guessing?
What questions should managers ask instead of guessing is a manager practice that turns how do you like to be managed into predictable team behavior, not a poster on the wall.
Engineering managers win when how do you like to be managed is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, respondents estimate 44% of current people managers had no formal leadership training before managing anyone. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, how do you like to be managed interview question and sample answer intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how do you like to be managed easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how do you like to be managed shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do preferences differ for senior engineers vs new grads?
How do preferences differ for senior engineers vs new grads is a manager practice that turns how do you like to be managed into predictable team behavior, not a poster on the wall.
Engineering managers win when how do you like to be managed is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, respondents estimate 44% of current people managers had no formal leadership training before managing anyone. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, how do you like to be managed interview question and sample answer intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how do you like to be managed easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how do you like to be managed shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do you document answers without bureaucracy?
How do you document answers without bureaucracy is a manager practice that turns how do you like to be managed into predictable team behavior, not a poster on the wall.
Engineering managers win when how do you like to be managed is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, respondents estimate 44% of current people managers had no formal leadership training before managing anyone. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, how do you like to be managed interview question and sample answer intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how do you like to be managed easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how do you like to be managed shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
What follow up keeps the conversation alive?
What follow up keeps the conversation alive is a manager practice that turns how do you like to be managed into predictable team behavior, not a poster on the wall.
Engineering managers win when how do you like to be managed is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, respondents estimate 44% of current people managers had no formal leadership training before managing anyone. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, how do you like to be managed interview question and sample answer intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how do you like to be managed easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how do you like to be managed shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do how do you like to be managed practices compare?
| Approach | Strength | Risk |
|---|---|---|
| Ad hoc conversations | Fast to start | Inconsistent across reports; hard to scale |
| Shared written profiles | Reduces guessing; helps hybrid teams | Stale if never revisited in 1 on 1s |
| Pulse and 1 on 1 loop | Connects listening to action | Fails if leaders skip follow through |
Implementation steps
- Ask the question in the first 1 on 1, not as a form, as a conversation starter.
- Capture three themes: communication, autonomy, and feedback style.
- Share your own manager readme so the exchange is mutual.
- Translate themes into calendar norms (deep work, response times).
- Revisit after promotions, reorgs, or return from leave.
Frequently asked questions
Why do interviewers ask how you like to be managed?
They are testing self awareness and fit, not fishing for flattery. Strong answers connect preferences to outcomes and show you can partner with different styles.
What is a good sample answer?
Name 2 to 3 preferences tied to results: clarity on priorities, candid feedback with examples, and autonomy with checkpoints, then ask how the team’s managers typically operate.
Should managers ask this question too?
Yes. Ask every direct report in week one and revisit quarterly. Preferences change with role seniority and life context.
Is this the same as a personality test?
No. It describes working agreements, not fixed types. Avoid DISC/MBTI labels unless the person finds them useful.
Related: working style assessment questions, manager readme examples template, first time manager specialist to leadership.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.