Artillery
8KSign in
Company news

Artillery is hiring full-stack product engineers

Hassy VeldstraHassy Veldstra

Artillery is a performance testing platform for DevOps and SRE. We make it easy to run planet-scale load tests from your own AWS infrastructure. Developers love Artillery because it’s modern and comes with batteries included. SRE & Platform teams love Artillery because they can provide a self-service load testing platform to developer teams. Security teams love Artillery because it runs on prem (or rather cloud-prem).

While we love, love, love load testing, and have a lot (like, A LOT) of new ideas to shake up the space, the Big Vision is much bigger than load testing. The state of testing tools for today’s complex production systems is abysmal. We’d like you to join us to help us build a better future.

Anyways, we’re hiring full-stack product engineers.

Full-stack product engineers?

As a product engineer you will be working on our products - Artillery, Artillery Pro, and yet-unannounced-but-we-think-its-cool stuff. We treat our website and our docs as products too. You will own features end-to-end from dev to prod, and spend most of your time writing code.

Our users interact with Artillery primarily through its CLI today, but we’re building an ambitious UI and UX for all things performance testing.

Our code is mostly JS and TypeScript, but there is some Go too. When building a UI we reach for React + Next.js + Tailwind. Build and test pipelines run mostly on Circle. To host stuff we use either AWS (serverless whenever possible) or Vercel. Our collaboration stack is Slack, Notion, Linear, and GSuite. We will never use Jira or Confluence. Design is done in Figma + prototypes in actual code.

We’re a small team and we wear a lot of hats. Here are some of the hats you may find yourself wearing (never worn some of those hats before? that’s OK):

  • Writing code. This week you may be adding a new feature to Artillery’s extension APIs and doing user research to figure out which existing plugins may be affected; next week you may be working on improving one of the monitoring/observability integrations we support, and the week after you may be building a new UI + API endpoints to support it.
  • Building end to end: you’ll go from a user story/PRD, to working with our designer to refine what the UI/UX is going to look like, to writing code, tests, build & release scripts, infra automation scripts, and documentation. You may find yourself writing a launch announcement for the new feature on our blog too, and dipping into our template library in Figma to make a nice header image for the blog + Twitter. You will think about ways to measure if & how the new feature is used, and how to get feedback from users to improve it.
  • Helping our community on Github, responding to and helping triage Issues, and answering questions in Discussions.
  • Helping improve the docs and examples, and spend time thinking about improving onboarding experience and DX of our products
  • Helping our customers in shared Slack channels
  • Building an internal tool to make us more productive, such as adding an integration to our Slack bot

You will have plenty of opportunities to move between projects, and will likely end up contributing to several of them, but we’d expect you to settle and focus on mostly one or two areas after a couple of months on the job.

Who is this role right for?

You’re a good fit if you like the idea of:

  • Building tools for other developers to help them be more productive and get their jobs done faster and better
  • Talking to people who use the software you build every day
  • Working on open source, and helping grow our open source community
  • Working across the stack - from frontend, to backend, to infrastructure. We don’t expect a unicorn who can do everything (none of us are), but you should be very comfortable in one area, and know enough to be dangerous elsewhere + be curious and willing to get involved with everything
  • Spending time thinking about UX, building intuition and deep empathy about the problems our users face, and how we can solve them
  • Working on tooling to improve the performance and reliability of other software systems
  • A chaotic fast-paced environment, which emphasises shipping, and with lots of opportunity for ownership and impact

Career level-wise, we expect this to be a good role for mid-to-senior and senior developers.

You should be in GMT ±4 hours. We are currently spread across Ireland, Germany, England, and UAE.

We are a distributed company, and we try to be as async as possible to optimize for deep work. That means we rely heavily on written communication, and on communicating proactively.

Why work with us? (or the bit where we sell the role)

  • We’re a small technical team building tools for other developers, and we talk to our users every day.
  • We’re a commercial open source company, a lot of your work will be open source.
  • We have paying customers who love our product.
  • This is the proverbial ground floor. You will be among the first 20 people at Artillery, not engineer no. 200 on team no. 17 at $YOUR_FRIENDLY_NEIGHBORHOOD_BIG_CO. You will have a huge amount impact and the opportunity to help build the kind of team and company you want to work for.
  • Meaningful equity and ownership.
  • We’re a distributed team with a very lightweight process that optimizes for shipping and deep work.

The compensation range for this role is $80-125k plus equity. This is a full-time job with vacation time, hardware budget, learning budget, and all the usual stuff.

Next steps?

  1. Drop us a line on team+jobs@artillery.io. Tell us a little bit about yourself, and about something you built (a project at $DAY_JOB, a side project on Github, etc). Feel free to include a resume too, but it’s not necessary. If you have any questions you want to ask straightaway, just shoot.
  2. We’ll get back to you with some times to connect on a call. This is an opportunity for us to get to know each other, and for us to pitch the company and answer all your questions about the company, team, and the work we do.
  3. If there’s mutual interest, we’ll go forward from there. Our hiring process is lightweight and we don’t do the typical tech company interview gauntlet here.