Location: Kingston, NY
Email: hello@trout.software

About the company

Trout Software is a young start-up with an ambitious mission: bringing full visibility for operators on their systems. Think about building a (posh) pivot table (on steroids), able to source data live from pretty much anything, and you get a sense of the functional and technical challenges we address.

We are looking for a senior software engineer to join us as part of our distributed team, and make your mark in building a challenging, but quite rewarding product.

Responsibilities

Well, first things first: writing code. Good, simple, maintainable, performant, secure, … code. It will help (understatement 😉) if you also think about the artifacts associated with said code: design documents, tests, …

But also helping others: reviewing designs and implementations, advising on testing strategies; or just simply lending a sympathetic ear 👂 when someone is having a bad day!

Qualifications

  • Be happy working with pointers, implementing algorithms, reading research paper, …
  • Have spent 3 or more years as part of a bigger software engineering team, especially in a large organization (the kind where you have to get product management to approve before you can start in earnest).
  • Expertise (5+ years) with Go (C++, C#, Java, … are good equivalents).
  • Some experience working in small set-up would definitively be a plus
  • You like functional immutable data structures, think about eventual consistency in your sleep, bore all your friends to death talking about consistent hashing? We want to hear about it 🤓 !

Admin:

  • Flexible role attached to one of our hub in Paris or Dublin.
  • Base salary range 70,000-97,000.
  • Stock

How to Apply?

We love to zoom in on the (sometimes gory) details of the work you have done in the past; so we usually ask for two portfolio samples.

For those not familiar with the format, a work sample presents in a 1 (max 2) page document a technical situation you faced, and includes:

  • a short introduction to what the system was supposed to do
  • a diagram of the system under consideration
  • a few salient details about the system itself (e.g. interesting algorithm, advanced observability, high efficient concurrency pattern, …)
  • a small discussions about choices that, with hindsight, would probably have been made differently

We understand producing this document is a serious commitment, and we make sure to read it with great attention and promptly reply, even if your application ends up not being a match.