Skip to content

Commit e4bc70f

Browse files
authored
Merge pull request #692 from gruntwork-io/remove-sales-engineer-posting
Remove sales engineer from job openings
2 parents 869911a + 9ac3978 commit e4bc70f

File tree

1 file changed

+0
-103
lines changed

1 file changed

+0
-103
lines changed

pages/careers/_open-positions.html

Lines changed: 0 additions & 103 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ <h2 class="bold">Open Positions</h2>
1212
<ul>
1313
<li><a href="#software-engineering">Software Engineering</a></li>
1414
<li><a href="#front-end-software-engineer">Software Engineering - Front End</a></li>
15-
<li><a href="#sales">Sales</a></li>
1615
</ul>
1716

1817
<hr />
@@ -168,107 +167,5 @@ <h4>Your Ideal Background</h4>
168167
>
169168
</p>
170169

171-
<hr />
172-
173-
<h2>Sales</h2>
174-
175-
<h3 style="margin-top: 5px; margin-bottom: 5px">DevOps Sales Engineer</h3>
176-
177-
<p>As a Gruntwork DevOps Sales Engineer, you'll work directly with customers ranging from startups
178-
to scale-ups to enterprises to help them evaluate Gruntwork on a technical level. You'll also work
179-
on improving the evaluation process itself by coming up with new ways to demo the Gruntwork
180-
product and creating small enhancements to the product that open up new markets like migrating users
181-
from Heroku or CloudFormation. Ideally, you can blog about what you learn, or publish your tooling as
182-
open source.
183-
</p>
184-
<p>Gruntwork is a different type of company with a different type of sales ethos. We serve two key stakeholders:
185-
(1) our customers and (2) Gruntwork itself. For customers, our mission is to help them make the
186-
best possible decision for setting up their AWS and Terraform infrastructure, whether that includes Gruntwork
187-
solutions or not. For Gruntwork, our mission is to help customers understand how the Gruntwork product
188-
meets our customers' needs. When we achieve both our missions, our sales performance takes care of itself.
189-
</p>
190-
<p>
191-
As the second DevOps sales engineer, your success will make a significant impact on the
192-
overall growth of the company. You'll work closely with our principal sales engineer, other Gruntwork
193-
software engineers, and one of the founders. Your growth path in this role could be as either a star individual
194-
contributor or team lead (at Gruntwork, we value IC and management roles equally), either on the sales
195-
engineer track, or an adjacent one such as software engineer or developer evangelist.
196-
</p>
197-
<p></p>
198-
199-
<h4>What You'll Work On</h4>
200-
<ul>
201-
<li>
202-
<strong>Understand customer requirements.</strong> The first rule of working with customers is
203-
to understand their needs. You'll work with customers to identify their requirements and in some
204-
cases help to define them.
205-
</li>
206-
<li>
207-
<strong>Showcase the product.</strong> Show customers how the Gruntwork
208-
product works. Answer both their high-level strategic questions and
209-
low-level technical questions. When necessary, collaborate with the
210-
engineering team to answer a question or build your knowledge.
211-
</li>
212-
<li>
213-
<strong>Develop proofs of concept.</strong> When we find a new customer opportunity
214-
or market segment, a little tooling and docs could go a long way. You'll study the new
215-
opportunity, propose a lightweight deliverable and implement it.
216-
</li>
217-
<li>
218-
<strong>Write blog posts.</strong> Share recent insights as a post on the Gruntwork blog,
219-
which has received millions of views.
220-
</li>
221-
<li>
222-
<strong>Work with a stellar team.</strong>You'll work with two teams. You'll collaborate
223-
with a team of industry-leading software and DevOps engineers that have written the open source tools
224-
and battle-tested, production-grade infrastructure-as-code for which Gruntwork is famous. In addition,
225-
you'll be part of the (someday famous) Gruntwork sales team.
226-
</li>
227-
</ul>
228-
<h4>Your Ideal Background</h4>
229-
<ul>
230-
<li>
231-
<strong>Significant experience with Terraform and AWS.</strong> You have used
232-
Terraform in depth and you know both its charm and its challenges. You've deployed
233-
many resources to AWS and run services in prod. There is a special authority that
234-
comes from having been in the trenches, so this is the one hard requirement
235-
for this role.
236-
</li>
237-
<li>
238-
<strong>Interest in helping others.</strong>You enjoy engaging with and presenting
239-
to others. You've experienced situations where you worked directly with stakeholders
240-
and it suited you.
241-
</li>
242-
<li>
243-
<strong>Interest in hacking.</strong>You like coding, tinkering, putting together quick demos,
244-
and showcasing proofs of concept. If there is a need to implement a narrowly-scoped deliverable
245-
for a customer, you see this as a fun opportunity.
246-
</li>
247-
<li>
248-
<strong>Moral grounding.</strong> You feel comfortable saying no when necessary
249-
or acknowledging the limits of our product so that we can all sleep better
250-
at night. In general, you do the right thing for customers, for Gruntwork, and for yourself.
251-
</li>
252-
</ul>
253-
<h4>What time zones do we work in?</h4>
254-
<p>
255-
While Gruntwork <a href="/careers/#sane-working-hours">generally</a> hires
256-
anywhere between San Francisco and Berlin, candidates for this role must
257-
be within the GMT-8 to GMT-3 time zones, with a preference for being
258-
located in the USA or Canada. We expect you'll work primarily with
259-
customers and fellow Grunts in those time zones, with limited engagement
260-
with customers worldwide and Grunts in Europe. Working during reasonable
261-
hours is a priority for us.
262-
</p>
263-
<p>
264-
If the above describes you:<br />
265-
<a
266-
href="https://apply.workable.com/gruntwork/j/8FC9042E48/apply/"
267-
class="btn btn-primary-hollow btn-sm d-inline-block btn-dpa"
268-
style="margin-top: 10px"
269-
role="button"
270-
>Apply Now</a
271-
>
272-
</p>
273170
</div>
274171
</div>

0 commit comments

Comments
 (0)