-
Notifications
You must be signed in to change notification settings - Fork 0
/
questions-that-senior-systems-engineers-want-answered.html
242 lines (227 loc) · 19.3 KB
/
questions-that-senior-systems-engineers-want-answered.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
<!DOCTYPE html>
<html dir="ltr" lang="en-US">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title>Questions that Senior Systems Engineers want answered</title>
<meta itemprop="name" content="Questions that Senior Systems Engineers want answered">
<meta property="og:title" content="Questions that Senior Systems Engineers want answered">
<link rel="icon" href="/favicon.png">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="twitter:creator" content="@ddtrejo">
<meta name="twitter:site" content="@ddtrejo">
<link rel="me" href="https://infosec.exchange/@dtrejo">
<link rel="canonical" href="https://dtrejo.com/questions-that-senior-systems-engineers-want-answered">
<meta property="og:url" content="https://dtrejo.com/questions-that-senior-systems-engineers-want-answered">
<meta property="og:image" content="https://dtrejo.com/images/social/questions-that-senior-systems-engineers-want-answered.jpg"/>
<meta name="image" content="https://dtrejo.com/images/social/questions-that-senior-systems-engineers-want-answered.jpg"/>
<meta itemprop="image" content="https://dtrejo.com/images/social/questions-that-senior-systems-engineers-want-answered.jpg"/>
<meta name="twitter:image:src" content="https://dtrejo.com/images/social/questions-that-senior-systems-engineers-want-answered.jpg">
<meta name="twitter:card" content="summary_large_image">
<meta property="og:type" content="article">
<link rel="stylesheet" href="/css/tachyons.min.css" />
<style>
* { margin-top: 0 }
* + * { margin-top: 1.5em }
li li { margin-top: 1.5em }
html { scroll-behavior: smooth }
body {
font-family: -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Oxygen, Ubuntu, Cantarell, Fira Sans, Droid Sans, Helvetica Neue, sans-serif;
font-size: 125%;
background-color: #013250;
color: #dcd9d6; /*rgb(220, 217, 214)*/
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale;
}
h1, h2, h3, h4, h5, h6 {
line-height: 1.25;
font-weight: 600;
}
a {
color: #f57a59;
font-weight: 500;
text-decoration: none;
}
a:focus, a:active, a:hover {
color: #ff6300;
}
.footer {
border-top: 1px solid rgb(25, 73, 110);
background-color: #021928;
}
.amp {
font-family: Baskerville, "Goudy Old Style", "Palatino", "Palatino Linotype", "Book Antiqua", serif;
font-style: italic;
font-weight: 400;
}
h1, h2, h3, h4, h5, h6, li, p, span, blockquote, pre, code {
text-rendering: optimizeLegibility;
}
hr {
border: none;
border-bottom: 1px solid rgba(0, 0, 0, .1);
border-top: 1px solid rgba(220, 217, 214, .1);
}
/* improve prism styles */
pre, pre[class*=language-] {
line-height: 1.4;
padding: 1.25rem 1.5rem;
margin: .85rem 0;
background-color: #282c34;
background-color: #191919;
border-radius: 6px;
overflow: auto;
}
blockquote {
margin-left: 0;
border-left: .5rem solid rgba(0, 0, 0, .5);
padding-left: 1.5em;
}
.customcolor { color: #013250 }
.b--customcolor { border-color: #013250 }
</style>
<meta name="cf-2fa-verify" content="27f0edaf36e9d24">
</head>
<body class="pt2 lh-copy">
<nav class="mw7 ph2 center flex flex-column flex-row-l"> <a class="fw5 link flex self-center self-start-l" href="/"> <img src="/images/dtrejo.jpg" class="w2 h2 br-100 mr3" alt="David Trejo"> dtrejo </a> <div class="flex self-center ml-auto-l mt0-l"> <a class="f5 fw5 link mt0 mr3 ttu" href="#footer">Articles</a> <a class="f5 fw5 link mt0 mr0 ttu" href="/books">Books</a> <!-- <a class="f5 fw5 link mt0 ttu" href="https://engineeroverflow.com" >Hire Engineers</a > --> </div></nav>
<article class="content mw7 ph2 center">
<h1 id="questions-that-senior-systems-engineers-want-answered">Questions that Senior Systems Engineers want answered</h1>
<p>You know that interviewing is a painful and expensive problem when your friends
send you pages worth of questions that they use to evaluate future employers.</p>
<p>These questions come from an experienced senior systems engineer friend of mine.
They gave me permission to publish, but asked to remain anonymous. This person
is currently interviewing.</p>
<p>If you're not looking to hire systems engineers, this article is less relevant
to you, but I think you'll still find it valuable.</p>
<p>– David</p>
<hr>
<p><em>Anonymous writes...</em></p>
<p>Things I want to know about a prospective employer. At the conclusion of this list, I will attempt to define questions that will elicit the answers to these questions. Note that the questions actually asked may not necessarily correspond to the questions that one wants to ask.</p>
<h2 id="what-i-really-want-to-know">What I Really Want to Know</h2>
<ul>
<li>Project prioritization<ul>
<li>What metrics are used to guide prioritization efforts?</li>
<li>What do project proposals look like? Are engineers forced to clearly define the problem or do they just propose various things they want to do?</li>
<li>Does someone maintain a backlog of potential projects and reassess things periodically?</li>
<li>Is there a centralized individual who selects what goes into a release from the top down, or are individual teams empowered to do their own prioritization?</li>
<li>How are projects staffed? In particular, how are projects that nobody <em>wants</em> to do staffed? It’s easy to find people to work on projects that will have high visibility or a technically rewarding environment, but the real test of culture is how gaps are identified and staffed.</li>
</ul>
</li>
<li>Software development lifecycle process<ul>
<li>What’s the code review process like?</li>
<li>How strictly are requirements enforced when it comes to getting reviews and performing automated testing?</li>
<li>Do developers write both code and tests, or is there an organizational split between development and QA?</li>
<li>How are conflicts mediated, both on the design level and the implementation level?</li>
<li>What’s the average time required to fix an “average sized” bug, from receiving the bug to closing it? Large times would reveal inefficiencies in the software development lifecycle. Over 8 hours saps motivation. Under 4 hours is a huge dopamine rush for highly productive developers. :)</li>
</ul>
</li>
<li>Approach to quality & technical debt<ul>
<li>Are people who introduce technical debt held accountable for removing it?</li>
<li>Is technical debt tracked at all?</li>
<li>When was the last time someone was promoted for their work on technical debt and other “hard to quantify” things (like developer productivity, internal infrastructure, build and test frameworks, etc.)</li>
<li>Are corporate and cultural incentives set up for adding or removing technical debt?</li>
<li>What is the ratio of short-term fixes to long-term fixes (and why)?</li>
</ul>
</li>
<li>Remote work and WFH policy</li>
<li>How do you grow engineers? How important is mentorship to company culture?</li>
<li>How do you give constructive feedback...<ul>
<li>...to managers?</li>
<li>...to other engineers?</li>
</ul>
</li>
<li>Are you hiring too fast or too slow?</li>
<li>What is your policy towards brilliant jerks?</li>
<li>What is your policy towards open source?</li>
</ul>
<h2 id="be-careful">Be careful:</h2>
<ul>
<li>Don’t come across as lazy when asking about WFH policies</li>
<li>Avoid using the phrase “technical debt” directly, as you don’t want to come across as an engineer who won’t provide high business value</li>
<li>Avoid the phrase “unfortunately”, as you want to come across as someone who builds things up rather than puts things down</li>
<li>Ask innocent, friendly, and natural questions</li>
</ul>
<h2 id="safer-phrasings-that-get-at-the-same-answers">Safer Phrasings That Get at the Same Answers</h2>
<p>The following practical questions might provide insights into the above theoretical questions:</p>
<ul>
<li>Re: build and continuous integration system, test frameworks, and technical debt:<ul>
<li>When was the last time someone made a meaningful contribution to software development lifecycle and developer productivity tooling? Tell me how they went about it (both organizationally and technically).</li>
<li>Do developers push code and tests at the same time (to the same repository), or is there a separate QA organization that writes tests asynchronously from features being pushed?</li>
</ul>
</li>
<li>Show me a “non trivial” code review (use this to asses quality standards, the review process, the no asshole rule, and testing requirements):<ul>
<li>Ask how things are handled when you ask someone to make a change and they don’t want to do it. Is the default policy to “file a bug” and do it later? Do those bugs just get closed out in two months, or is action ever taken? When the problematic code ends up causing production issues, does the issue come back to the person who wrote it?</li>
<li>How do you resolve arguments about code style? Do engineers waste colossal amounts of time arguing about style in reviews, or are there automated style checks and formatting tools that allow the discussion to shift toward matters of substance?</li>
<li>Note: you can’t ask a new hire this question, you need to ask a long-time employee who has been around the block and seen how things play out</li>
<li>Did the developer have to re-run tests due to flakiness? Is there a dashboard showing the state of the build? Are flaky tests tracked? Are there metrics regarding how often tests flake so that the most flaky areas can be addressed?</li>
</ul>
</li>
<li>What are the attributes that get people promoted?<ul>
<li>Be specific: Ask when the last time a close colleague was promoted and what they did to earn the promotion.</li>
</ul>
</li>
<li>Whose responsibility, if any, is developer productivity?<ul>
<li>“Everyone’s responsibility” is the worst possible answer to this question, as it means “nobody’s responsibility”</li>
<li>If answers are vague, follow up with: “What was the last thing you did personally?”<ul>
<li>Risk: This might embarrass the person if they did nothing.</li>
<li>This is a bit hardball, only go this far if you must.</li>
</ul>
</li>
</ul>
</li>
<li>How does the culture change near the end of the release?<ul>
<li>Does all hell break loose and people just push low quality code to get things out the door?</li>
<li>If so, how is the remaining work to “do it right” tracked?</li>
<li>What is the power relationship between engineers and managers? Do managers strongly imply you need to work late nights and long hours to ship a release?</li>
</ul>
</li>
<li>How do engineers interact with customers?<ul>
<li>A bit of a fluff question, but can reveal a fair amount about how the company works. Can engineers own a problem from customer interaction to solution, or are they just cogs in the wheel of a giant organization of salespeople and product managers?</li>
</ul>
</li>
<li>How much time have mentors spent with interns and/or new hires this year?<ul>
<li>Goal should be to find a company where mentorship is valued. Mentors shouldn’t blink at the idea of dropping whatever they’re doing for 2 hours to help a mentee (assuming the mentee is worth their time investment).</li>
</ul>
</li>
<li>What is the weirdest bug that you’ve worked on recently?<ul>
<li>Goal is to see how the organization responds to failure</li>
<li>How did you fix it in the short-term?</li>
<li>How did you fix it in the long-term?<ul>
<li>This is the most interesting part</li>
</ul>
</li>
<li>You ideally want to be at a company with good war stories, because then people are excited to do their job</li>
<li>Do people actually debug things, or just work around them and restart it?</li>
<li>Does the company have a culture of root causing issues on first failure, or do they just throw their hands in the air if they can’t reproduce the issue?</li>
</ul>
</li>
</ul>
<p>– Anonymous<br>
Senior systems engineer in the SF bay area</p>
<hr>
<p>David here. You may see the pattern: more senior people, even those who are
extremely technical, want high autonomy work, and want to be involved in
business decisions. They want to avoid teams and managers where they're just
another pair of hands, where no one tracks the impact of engineering work. They
want their engineering leaders to perceive the kinds of rot and dysfunction that
are difficult to explain to non-technical decision-makers.</p>
<p>You'll also notice that even someone who is more senior is cautious about asking
hard questions. Interestingly, I ask similar questions in my interviews for full
stack growth engineering positions, although they lean towards growth.</p>
<p>Yours,<br>
David<br>
david ått dtrejo.com</p>
<p>PS Want to impress all your engineering candidates with how great you and your company are? Email me, I can help.</p>
<p>PPS Tomorrow I'll be writing and sending my book review of Moneyball–you're going to like it because you'll get a better feel for how to measure & value engineering work.</p>
<p>In the mean time, I made this tool for you: <a href="http://engineerworth.com/">EngineerWorth.com</a>–it helps you calculate whether an engineering feature will pay back the time investment. You can drag the numbers to adjust them to your situation.</p>
</article>
<div class="mw7 ph2 center"> <img src="/images/dtrejo.jpg" title="David Trejo" class="br-100 fl ml2 mr2" height="80" /> <div class="overflow-hidden mr2"> <h4>David Trejo</h4> <p>Engineer at Chime <span class="amp">&</span> consultant. Past clients include Credit Karma, Aconex, Triplebyte, Neo, the Brown Computer Science Department, Voxer, Cloudera, and the Veteran's Benefits Administration.</p> </div></div>
<div id="footer" class="footer mt5 pt5 pb4"><div class="mw7 ph2 center"> <h3>Hiring Engineers? You'll like these articles</h3> <ol><li><a href="/engineer-interview-script">Growth & full stack engineering interview script</a></li><li><a href="/referrals">How to hustle on your referrals so they actually get hired</a></li><li><a href="/moneyball-book-review-and-measuring-revenue-per-engineer">Moneyball book review and measuring revenue per engineer</a></li><li><a href="/questions-that-senior-systems-engineers-want-answered">Questions that Senior Systems Engineers want answered</a></li><li><a href="/tools-for-hiring-engineers">Tools for hiring engineers that save time and increase conversion</a></li><li><a href="/how-to-reliably-get-your-team-to-write-articles-for-your-engineering-blog">How to reliably get your team to write articles for your engineering blog</a></li><li><a href="/why-share-salary">Why share salary ranges with candidates?</a></li><li><a href="/massive-list-of-engineering-recruiting-channels">Massive list of engineering recruiting channels</a></li><li><a href="/how-to-run-an-intern-program-like-cloudera-s">How to run an intern program like Cloudera's</a></li><li><a href="/how-to-replicate-the-warmth-of-referral-hires">How do you replicate the warmth and friendliness of a referral hire, even with a stranger engineer? By treating hiring like dating.</a></li><li><a href="/how-to-run-an-intern-meetup">How to run an intern meetup</a></li></ol>
<h3>Growth Engineering Articles</h3> <ol><li><a href="/engineer-interview-script">Growth & full stack engineering interview script</a></li><li><a href="/engineering-lead">Engineering lead checklists</a></li><li><a href="/days-as-a-growth-engineer">Everything you should do in the first 30 days of a new growth engineering job</a></li><li><a href="/how-do-you-transition-from-rails-lead-engineer-to-growth-engineer">How do you transition from Rails lead engineer to growth engineer?</a></li><li><a href="/chaos-in-your-product-prototyping">Chaos in your product prototyping</a></li></ol>
<h3>How to...</h3> <ol><li><a href="/tailoring-perfect-shirt-pants-jacket">Tailoring the perfect shirt, pants, and jacket</a></li><li><a href="/home-search">Home Searching Advice</a></li><li><a href="/publishing-vue-codesandbox-to-github-pages">How to publish a Vue CodeSandbox.io to Github Pages on a custom domain</a></li><li><a href="/how-to-get-your-business-to-pull-you-forward">How to get your business to pull you forward</a></li><li><a href="/overcome-cold-email-procrastination">Overcome cold-email procrastination</a></li><li><a href="/how-to-write-consistently-painlessly-and-without-writers-block">How to write consistently, painlessly, and without writer's block</a></li><li><a href="/how-to-email">How to email</a></li><li><a href="/how-to-buy-and-cook-steak">How to Buy and Cook Steak</a></li></ol>
<h3>Health</h3> <ol><li><a href="/why-go-carnivore-aka-zero-carb">Why go carnivore? (aka zero carb)</a></li><li><a href="/cancer">Cancer, fasting, carnivore, and chemotherapy side effects</a></li><li><a href="/lifting">Start weightlifting in just 720 days</a></li></ol>
<h3>Node.js</h3> <ol><li><a href="/my-javascript-tooling-wishlist">My Javascript tooling wishlist</a></li><li><a href="/metrics-and-operational-awareness-at-voxer">Metrics and operational awareness at Voxer</a></li><li><a href="/zero-effort-responsive-email-creation">Zero effort responsive email creation</a></li><li><a href="/node-single-point-of-failure">Node single point of failure</a></li></ol>
<h3>Git</h3> <ol><li><a href="/pull-requests">How Open Source People Do Pull Requests and What We Can Learn from Them</a></li><li><a href="/develop-on-a-cloud-machine">Develop on a cloud machine</a></li><li><a href="/faster-git-workflow">A faster Git workflow with Ampline</a></li><li><a href="/my-github-pull-request-workflow">My Github pull request workflow</a></li></ol>
<h3>Top Projects</h3> <ul> <li> <a href="https://duskk.com">Duskk.com</a> Want to unlock the power of your writing? Discover greatness inside yourself with <a href="https://duskk.com">Duskk, a journaling app</a>. </li> <li> <a href="https://EngineerWorth.com">EngineerWorth.com</a> Is that product feature worth coding? Run a quick ROI calculation and find out. </li> <li> <a href="/qlock/qlock.html">jQuery Qlock2</a> Tell time with this $800 clock, for free. </li> <li> <a href="/colorslice/">ColorSlice</a> Wish it were easier to steal and create color schemes? Colorslice helps front-end developers <span class="amp">&</span> designers with color. </li> <li> <a href="/colorpreview/">ColorPreview</a> Vet color combinations and pick only the ones with enough contrast, that your eye finds pleasing. </li> <li> <a href="/lazytemplating/">Lazy Templating</a> What if you could do HTML templating using a spreadsheet? Now you can. </li> <li> <a href="http://github.com/DTrejo/ampline">Ampline</a> Tired of copy-pasting or tab-completing long file paths? Accelerate yourself on the command-line. </li> </ul> <h4><a href="/archived">Archived</a></h4> <h3>Find me</h3> <ul> <li><a href="https://github.com/DTrejo">Github</a></li> <li><a rel="me" href="https://infosec.exchange/@dtrejo">Mastodon (infosec.exchange)</a></li> <li><a href="https://twitter.com/ddtrejo">Twitter</a></li> <li> <a href="#david åt dtrejo.com" title="david åt dtrejo.com" onclick="event.preventDefault(); this.href = 'mailto:' + (this.innerText = 'david' + '@dtrejo.com')"> Email me ✉️</a> </li> </ul> <div> Copyright © 2009-2024 David Trejo. Opinions mine. </div></div></div>
</body>
</html>