Skip to content

add new sre role to careers [SRE-4] #322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jun 15, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
add sre to open positions
  • Loading branch information
Matt Calhoun committed Jun 11, 2020
commit 6f64d6e8c3ddf372f01744fac67969b81617846b
106 changes: 96 additions & 10 deletions pages/careers/_open-positions.html
Original file line number Diff line number Diff line change
Expand Up @@ -88,22 +88,108 @@ <h4>Your Ideal Background</h4>

<hr />

<h3>Senior Software Engineer</h3>
<a target="site-reliability-engineer"></a>
<h3>Site Reliability Engineer (SRE)</h3>
<h4>
Be an SRE without being on call! Help Gruntwork develop SRE as a product
offering and enable our hundreds of customers to achieve best-practices
for operations and reliability, all while not being woken up at 3am!
</h4>
<h4>What You'll Work On</h4>
<ul>
<li>
<strong>Build an SRE product offering:</strong> Develop logging,
monitoring, and alerting strategies around availability, latency, and
overall systems health and develop solutions that can be deployed
internally and externally for our customers.
</li>
<li>
<strong>Toil/Engineering balance:</strong> Spend 50% of your time or
less on toil and the rest engineering solutions to reduce it for the
whole team.
</li>
<li>
<strong>Document tribal knowledge:</strong> Capture siloed knowledge to
create knowledgebase articles, runbooks, and other documentation for the
internal team as well as Gruntwork customers.
</li>
<li>
<strong>Gruntwork systems:</strong> Ownership of the systems and
infrastructure that power our web presence, internal tooling, and
upcoming Software as a Service platform.
</li>
<li>
<strong>World-class customer support:</strong> While participating in
business-hours only support rotations, triage customer requests, teach
Gruntwork and DevOps best-practices, help resolve problems, escalate to
internal SMEs, and automate and document the solutions so that problems
are mitigated for future users.
</li>
<li>
<strong>And a little bit of everything else.</strong> Gruntwork is a
<a
href="https://blog.gruntwork.io/how-we-built-a-distributed-self-funded-family-friendly-profitable-startup-93635feb5ace"
target="_blank"
>small, distributed, self-funded, profitable startup</a
>, so things are changing all the time, and we all wear many hats. You
should expect to write plenty of code, but, depending on your interests,
there will also be ample opportunity to write blog posts, give talks,
contribute to open source, go to conferences, talk with customers, do
sales calls, think through financial questions, interview candidates,
mentor new hires, design products, come up with marketing ideas, discuss
strategy, consider legal questions, and all the other tasks that are
part of working at a small company.
</li>
</ul>
<h4>Your Ideal Background</h4>
<ul>
<li>
You hate doing the same thing twice and would rather spend the time to
automate a problem away than do the same work again.
</li>
<li>
You have strong communication skills and are comfortable engaging with
external customers.
</li>
<li>You have experience running production software ("Ops").</li>
<li>
You have a strong background in software engineering (or are working
hard on it!).
</li>
<li>You have a passion for learning new technologies and languages</li>
<li>Bonus points for a sense of humor, empathy, and curiosity.</li>
<li>
Note that we're less concerned with prior experience than we are with
curiosity about all areas of the stack and demonstrated ability to learn
quickly and go deep when necessary.
</li>
</ul>
<p>
If the above describes you, email us at
<a href="mailto:careers@gruntwork.io">careers@gruntwork.io</a>.
</p>

<hr />

<h3>Senior Software Engineer<br />Senior Site Reliability Engineer</h3>
<p>
Just like our <a href="#software-engineer">Software Engineer</a> position,
but with the added expectation that you take more ownership, get (complex)
things done, and communicate even more effectively.
Just like our <a href="#software-engineer">Software Engineer</a> and
<a href="#site-reliability-engineer">Site Reliability Engineer</a>
positions, but with the added expectation that you take more ownership,
get (complex) things done, and communicate even more effectively.
</p>

<hr />

<h3>Principal Software Engineer</h3>
<h3>
Principal Software Engineer<br />Principal Site Reliability Engineer
</h3>
<p>
Just like our
<a href="#senior-software-engineer">Senior Software Engineer</a> position,
but with the added expectation that you can take full ownership of a
complex project, get (highly complex) things done, and communicate even
more effectively.
Just like our <a href="#software-engineer">Software Engineer</a> and
<a href="#site-reliability-engineer">Site Reliability Engineer</a>
positions, but with the added expectation that you can take full ownership
of a complex project, get (highly complex) things done, and communicate
even more effectively.
</p>
</div>
</div>