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
|
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang xml:lang>
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="franck@fcuny.net" />
<title>Franck Cuny</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
<style type="text/css">body {
font-family: sans-serif;
font-size: 1em;
line-height: 1.8em;
color: #0e0e0b;
margin: 1em auto;
padding: 0 0.55em;
max-width: 50rem;
}
h1 {
color: #0e0e0b;
font-size: 1.3rem;
}
h2, h3 {
border-bottom: 1px solid #eee;
font-style: italic;
}
h2 {
margin-top: 1.25em;
margin-bottom: 0.41em;
font-size: 1.2rem;
}
h3 {
margin-top: 1.5em;
margin-bottom: 0.5em;
font-size: 1rem;
}
hr{
color:#000111;
background-color:#000111;
border:none;
height:1px
}
a {
color:#047bc2;
transition:color .1s ease-in-out;
}
table {
width: 100%;
border-spacing: 0px;
outline: none;
}
td{
padding-right: 0.7em;
}
td:last-child {
text-align: right;
}
table, th, td {
font-family: monospace;
color: #000;
}
#title-block-header {
padding-right: 10px;
font-size: 1.4em;
display: flex;
font-family: monospace;
justify-content: space-between;
align-items: center;
padding-top: 0.5rem;
border-bottom: 1px;
}
#experience {
padding-top: 20px;
}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<header id="title-block-header">
<h1 class="title">Franck Cuny</h1>
<p class="author"><a href="mailto:franck@fcuny.net">franck@fcuny.net</a></p>
</header>
<p>I'm a seasoned Site Reliability Engineer with experience in large
scale distributed systems. I'm invested in mentoring junior and senior
engineers to help them increase their impact. I'm always looking to
learn from those around me.</p>
<p><strong>Specializations</strong>: distributed systems,
containerization, debugging, software development, reliability.</p>
<h1 id="experience">Experience</h1>
<h2 id="roblox-san-mateo">Roblox, San Mateo</h2>
<table>
<tbody>
<tr class="odd">
<td>Site Reliability Engineer</td>
<td>Principal (IC6)</td>
<td>SRE Group</td>
<td>Feb 2022 - to date</td>
</tr>
</tbody>
</table>
<p>I'm the Team Lead for the Site Reliability group that was started at
the end of 2021.</p>
<p>I'm defining the road-map and identify areas where SREs can partner
with different team to improve overall reliability of our services.</p>
<h2 id="twitter-san-francisco">Twitter, San Francisco</h2>
<h3 id="compute">Compute</h3>
<table>
<tbody>
<tr class="odd">
<td>Software Engineer</td>
<td>Senior Staff</td>
<td>Compute Info</td>
<td>Aug 2021 - Jan 2022</td>
</tr>
<tr class="even">
<td>Site Reliability Engineer</td>
<td>Senior Staff</td>
<td>Compute SREs</td>
<td>Jan 2018 - Aug 2021</td>
</tr>
</tbody>
</table>
<p>Initially the Tech Lead of a team of 6 SREs supporting the Compute
infrastructure. In August 2021 I changed to be a Software Engineer and
was leading one of the effort to adopt Kubernetes for our on-premise
infrastructure. As a Tech Lead I helped define number of internal
processes for the team, from on-call rotations to postmortem
processes.</p>
<p>Twitter's Compute is one of the largest Mesos cluster in the world
(XXX thousands of nodes across multiple data centers). The team defined
KPIs, improved automation to mange the large fleet of bare metal
machines, defined APIs for maintenance with partner teams.</p>
<p>In addition to supporting Aurora/Mesos, I also lead a number of
effort related to Kubernetes, both on-premise and in the cloud.</p>
<p>Finally, I've helped Twitter save XX of millions of dollar in
hardware by designing and implementing strategies to significantly
improve the hardware utilization of our bare metal infrastructure.</p>
<h3 id="storage">Storage</h3>
<table>
<tbody>
<tr class="odd">
<td>Site Reliability Engineer</td>
<td>Staff</td>
<td>Storage SREs</td>
<td>Aug 2014 - Jan 2018</td>
</tr>
</tbody>
</table>
<p>For 4 years I supported the Messaging and Manhattan teams. I moved
all the pub-sub systems from bare-metal deployment to Aurora/Mesos,
being the first storage team to adopt the Compute orchestration
platform. This helped reducing operations, time to deploy, and improve
overall reliability. I pushed for adopting 10Gb+ networking in our data
center to help our team to scale. I was the SRE Tech Lead for the
Manhattan team, helping with performance, operation and automation.</p>
<h2 id="senior-software-engineer---say-media-san-francisco">Senior
Software Engineer - Say Media, San Francisco</h2>
<table>
<tbody>
<tr class="odd">
<td>Software Engineer</td>
<td>Senior SWE</td>
<td>Infrastructure</td>
<td>Aug 2011 - Aug 2014</td>
</tr>
</tbody>
</table>
<p>During my time at Say Media, I worked on two different teams. I
started as a software engineer in the platform team building the various
APIs; I then transitioned to the operation team, to develop tooling to
increase the effectiveness of the engineering organization.</p>
<h2 id="senior-software-engineer---linkfluence-paris">Senior Software
Engineer - Linkfluence, Paris</h2>
<table>
<tbody>
<tr class="odd">
<td>Software Engineer</td>
<td>Senior SWE</td>
<td>Infrastructure</td>
<td>July 2007 - July 2011</td>
</tr>
</tbody>
</table>
<p>I was one of the early engineers joining Linkfluence in 2007. I led
the development of the company's crawler (web, feeds). I was responsible
for defining the early architecture of the company, and designed the
internal platforms (Service Oriented Architecture). I helped the company
to contribute to open source projects; contributed to open source
projects on behalf of the company; represented the company at numerous
open sources conferences in Europe.</p>
<h1 id="technical-skills">Technical Skills</h1>
<ul>
<li><strong>Languages</strong> Python, Go, Ruby, Perl</li>
<li><strong>Frameworks</strong> Kubernetes, Aurora, Mesos</li>
<li><strong>Databases</strong> RDBMS, NOSql</li>
<li><strong>Dev tools</strong> Git</li>
</ul>
</body>
</html>
|
