Add Software Engineer (Contractor) (#651)

Marina · web-flow · commit 353ba40b2d05 · 2021-10-22T17:07:12.000+02:00
* Remove SRE + add SWE Contractor

* Update description of contractor

* Update headers for contractor role

* Update list of requirements

* Fix titles + add requirement

* Update list of requirements

* Minor text edit

* Update job description

* Update requirements for contractor

* Smaller tweaks + workable url

* remove section from swe
diff --git a/pages/careers/_open-positions.html b/pages/careers/_open-positions.html
@@ -11,7 +11,7 @@ <h2 class="bold">Open Positions</h2>
 
     <ul>
       <li><a href="#software-engineering">Software Engineering</a></li>
-      <li><a href="#site-reliability-engineering-sre">Site Reliability Engineering (SRE)</a></li>
+      <li><a href="#software-engineering-contract">Software Engineering (Contract)</a></li>
       <li><a href="#sales">Sales</a></li>
     </ul>
 
@@ -96,60 +96,47 @@ <h4>Your Ideal Background</h4>
 
     <hr />
 
-    <h2>Site Reliability Engineering (SRE)</h2>
+    <h2>Software Engineering (Contract)</h2>
 
-    <h3 style="margin-top: 5px; margin-bottom: 5px;">Site Reliability Engineer (SRE)</h3>
-    <h3 style="margin-top: 5px; margin-bottom: 5px;">Senior Site Reliability Engineer (SRE)</h3>
-    <h3 style="margin-top: 5px;">Principal Site Reliability Engineer (SRE)</h3>
+    <h3 style="margin-top: 5px; margin-bottom: 5px;">Senior Software Engineer (Contract)</h3>
+    <h3 style="margin-top: 5px; margin-bottom: 5px;">Principal Software Engineer (Contract)</h3>
+
+    <p>At Gruntwork, we have created a library of production-grade infrastructure code that is used by thousands of developers around the world. We are getting more support & maintenance requests for the library than our small team can currently handle, so we are hiring contractors to help us scale the team up and down in response to inquiry volume. Although you would start as a contractor, focused on support & maintenance, this is a job with a view to full-time employment!</p>
+    <p>This is a contractor position, paid based on an hourly rate. We expect an average of 10 hours of work per week though it'll fluctuate up and down, with more hours on some weeks (e.g., 30 hours) and fewer hours on other weeks (e.g., 0 hours).</p>
+    <p></p>
 
-    <p>
-      Be an SRE without being on call! Help Gruntwork develop its internal SRE
-      practices as well as offer SRE as a product to enable our hundreds of
-      customers to achieve world-class operations and reliability, all while not
-      being woken up at 3am!
-    </p>
     <h4>What You'll Work On</h4>
     <ul>
       <li>
-        <strong>Build an SRE product offering:</strong> Create a new product
-        offering for Gruntwork customers that includes Production Readiness
-        Reviews, training and implementation strategies for SLIs/SLOs/SLAs,
-        error budgets, chaos engineering strategies, blame-free post-mortems,
-        logging, monitoring, and alerting strategies around availability,
-        latency, and overall systems health. This solution will be deployed both
-        internally for Gruntwork and externally for our customers.
-      </li>
-      <li>
-        <strong>Spend Max 50% of Your Time On Toil:</strong> We are adamant
-        about having our SREs spend 50% of their time or less on
-        <a
-          href="https://landing.google.com/sre/sre-book/chapters/eliminating-toil/"
-          target="_blank"
-          >toil</a
-        >
-        and the rest on engineering solutions to reduce it for the whole team.
-        We enforce this by using a rotational schedule that ensures at least 50%
-        of your time is free for engineering work.
-      </li>
-      <li>
-        <strong>No On-Call:</strong> A key goal at Gruntwork is that no one
-        should have to be woken up in the middle of the night or on New Year's
-        Day due to an outage. We do not have an on-call rotation now and we’re
-        building out an SRE team to help us keep it that way. How do we design
-        products where outages don’t require paging someone? How do we design
-        infrastructure where these outages are rare? What sorts of SLIs, SLOs,
-        and SLAs should we promise customers? and the rest engineering solutions
-        to reduce it for the whole team.
+        <strong
+        ><a href="/infrastructure-as-code-library/"
+        >Infrastructure as Code Library</a
+        ></strong
+        >: create and maintain reusable infrastructure modules for a variety of
+        infrastructure (e.g., EKS, ECS, RDS, VPC, Lambda, EC2, S3, ElastiCache,
+        etc.), using a variety of tools (e.g., Terraform, Go, Python, Bash,
+        Docker, Packer, etc.), atop AWS.
       </li>
       <li>
         <strong>Document team knowledge:</strong> Capture siloed knowledge and
         create knowledgebase articles, runbooks, and other documentation for the
         internal team as well as Gruntwork customers.
       </li>
       <li>
-        <strong>Gruntwork systems:</strong> Own the systems and infrastructure
-        that power our web presence, internal tooling, and upcoming Software as
-        a Service platform.
+        <strong>Open Source:</strong> contribute to our open source projects,
+        including
+        <a href="https://github.com/gruntwork-io/terragrunt" target="_blank"
+        >Terragrunt</a
+        >,
+        <a href="https://github.com/gruntwork-io/terratest" target="_blank"
+        >Terratest</a
+        >,
+        <a href="https://github.com/gruntwork-io/cloud-nuke" target="_blank"
+        >cloud-nuke</a
+        >,
+        <a href="https://github.com/gruntwork-io/bash-commons" target="_blank"
+        >bash-commons</a
+        >, and more.
       </li>
       <li>
         <strong>World-class customer support:</strong> While participating in
@@ -158,48 +145,29 @@ <h4>What You'll Work On</h4>
         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 have a strong background in software engineering, with 5+ years of experience.</li>
+      <li>You know how to write Infrastructure as Code using Terraform. </li>
+      <li>You know have deep experience with AWS.</li>
       <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
+        You have strong communication skills in English and are comfortable engaging with
         external customers.
       </li>
-      <li>You know how to write code across the stack (“Dev”).</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>
+      <li>You have a passion for learning new technologies and languages.</li>
+      <li>Ability to write Golang and Bash is a nice to have!</li>
+      <li>You live within our time zone bounds (GMT-7 to GMT+2).</li>
+      <li>You're interested in working an average of 10 hours/week.</li>
+      <li>You can respond to support & maintenance requests within a 2 business day SLA.</li>
     </ul>
+
     <p>If the above describes you:<br>
-      <a href="https://apply.workable.com/gruntwork-io/j/21BC80A6E4/apply/" class="btn btn-primary-hollow btn-sm d-inline-block btn-dpa" style="margin-top:10px;" role="button">Apply Now</a>
+      <a href="https://apply.workable.com/j/80BC6CFBCD" class="btn btn-primary-hollow btn-sm d-inline-block btn-dpa" style="margin-top:10px;" role="button">Apply Now</a>
     </p>
 
     <hr />
@@ -211,12 +179,12 @@ <h3 style="margin-top: 5px; margin-bottom: 5px;">Sales Engineer</h3>
     <p>We've grown to millions of dollars in annual revenue with zero outside investment/debt, near-zero marketing budget, and a small number of software engineers who handle all sales calls in addition to their core work. Now we're ready to take our sales to the next level!</p>
     <p>Our product is used and purchased by software and DevOps engineers, so we are looking for a sales professional with proven experience selling products that enable software engineers. As the first sales hire, you'll report directly to the founders and have considerable impact on the overall growth of the company. Your growth path in this role could be as either a star individual contributor or team lead (at Gruntwork, we value IC and management roles equally).</p>
     <p></p>
-  
+
     <h4>What You'll Work On</h4>
     <ul>
       <li><strong>Manage deals.</strong> Own the deal from inquiry through contract signature. Engage with both large enterprises and startups.</li>
       <li><strong>Showcase the product.</strong> Show customers how the Gruntwork product works. Answer both their high-level strategic questions and common technical questions. When necessary, collaborate with our engineering team to answer a detailed question or build your knowledge.</li>
-      <li><strong>Make customer-driven tweaks where needed.</strong> Does the customer want to see an integration out of the box we don't yet support? You can add it directly, following the patterns we've laid down with other integrations.</li>    
+      <li><strong>Make customer-driven tweaks where needed.</strong> Does the customer want to see an integration out of the box we don't yet support? You can add it directly, following the patterns we've laid down with other integrations.</li>
       <li><strong>Develop new markets.</strong> Our product works well for customers building greenfield in AWS or doing migrations. What kinds of customers might find themselves in that situation? Identify those opportunities, figure out what the customer wants, and write content/guides to help showcase our solution.</li>
     </ul>
     <h4>Your Ideal Background</h4>
