Job descriptions don't tend to be very helpful. Here's some 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 those meetings out of the way on Tuesdays and Thursdays so you have 3 focus days. You'll meet with your team twice a week, the head of engineering once a week, and the whole company at an all-hands once a week. That's it, those are all the scheduled meetings. We have optional “water cooler”-style hangouts as well.

• You won’t be micromanaged. You’ll be given objectives, context, and a supportive team, and expected to take ownership.

• You’ll be the 7th 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.

A little bit about our technical stack

You’ll join us in developing our platform, the open source libraries, standards and services our platform needs. Most of our backend is written in .NET (C#) and a little bit of Node. Our dashboard is written in React, and we use a bit of Rust for native SDK development. We host our (micro)services in Kubernetes in Microsoft Azure and use Infrastructure As Code to manage this. We use Azure Service Bus for messaging, Azure Storage and Azure Cosmos for storing data.

We host our code in GitHub and, of course, all tests, builds and deployments are automated. We don't have a strict test coverage percentage rule, but write a good amount of unit and integration tests.

We try to hire people who will do the work of their lives at Trinsic. That person is likely:

A little bit about you

• A well-rounded engineer who is particularly strong in backend and cloud architectures.

• Has experience building customer-facing APIs or experience building systems implemented on top of well defined standards & protocols like gRPC, REST, OIDC/OAuth or anything similar.

• You've got experience with distributed systems and know how to manage non-transactional entities with transactional entities. Our customers expect us to deliver the best infrastructure for them to build on, so handling this well is something you find important.

• A great asynchronous communicator who is excited to work on a remote team.

• You know how to balance the pragmatic short-term needs of the business with the longer term roadmap.

• Someone who identifies with the core values and philosophy of self-sovereign identity, namely privacy, autonomy, and individual dignity

When you join

On your first day(s) we'll help you deploy a very simple change (e.g. a log line) to production. Within the first 30 days you'll work closely with your onboarding buddy to implement 5 good first issues. You'll participate in our rituals and complete the Self Sovereign Identity onboarding.

Within 60 days days you'll expand into two small features where you'll be the main owner (though of course with assistance from others) and start pro-actively contributing ideas for our platform. We'll be starting to see that you realize the difference of what work makes an impact.

Within 90 days you'll have picked up 3 features as the main owner, mostly independently. You'll have cleaned up some technical debt or maintenance that you discovered yourself. You'll be contributing/highlighting the value of engineering's business impact during our team meetings.