Job descriptions usually aren’t very helpful. Here are the things you probably care about:
- Everybody on the team is smart and down-to-earth. No jerks or egomaniacs.
- You won’t spend more than 4 hours in scheduled meetings per week on average. We get all the meetings out of the way Monday mornings.
- You won’t be micromanaged. You’ll be given objectives, context, and a supportive team, and expected to take ownership.
- You’ll be the 8th engineer, which means you’ll be ~15% of the engineering capacity. That’s a huge potential for impact. Thus, you’ll be recognized and rewarded for your work.
- We’re solving one of the only remaining truly unsolved problems on the web and we’re using sexy technologies to do it. So the work is fun.
- There are things we suck at, things that are broken, fires raging, etc. You need to be comfortable with that and be willing to make Trinsic better.
You’ll join us in developing the open source libraries, standards, and drivers our platform needs. We try to hire people who will do the work of their lives at Trinsic. That person is likely:
- A well-rounded engineer who is particularly strong in backend and cloud architectures. Rust is our language of choice for native development, and Go, .NET, and Node in a microservices setup. Kubernetes native development and Protobuf across the board.
- Has experience building customer-facing APIs or experience building systems implemented on top of well defined standards & protocols like gRPC, REST, OIDC/OAuth
- An exceptional communicator who is excited to work on a remote team
- Someone who identifies with the core values and philosophy of self-sovereign identity, namely privacy, autonomy, and individual dignity
Within the first 30 days, you'll work with your onboarding buddy closely to implement your first PR on a key open source codebase. By 60 days, we expect you to be implementing features autonomously and by 90 days we expect you'll be irreplaceable because of your knowledge and domain expertise in a particular aspect of the codebase.
Engineering Interview Process: what to expect