Background

We’re looking for a senior engineer to extend the amount of big bets we can take on as a team to help us make the world more accessible by empowering teams to build the world’s most widely-adopted identity wallets and ecosystems. We’re early on our journey and this is a unique and exciting opportunity to be part of something that is going to change the world in a drastic way.

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.
• 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, challenging and very exploratory. We hire people that want to do the work of their lives at Trinsic and are up for a challenge.
• You’ll be the 8th engineer, which means you’ll be 12.5% of the engineering capacity. That’s a huge potential for impact. Thus, you’ll be recognized and rewarded for your work.
• You won’t be micromanaged. You’ll be given objectives, context, and a supportive team, and are expected to take a lot of ownership.
• You won’t spend more than 4 hours in scheduled meetings per week on average. We get those meetings out of the way on Fridays so you have 4 focus days. You'll meet with your team shortly once a day, the head of engineering once every two weeks, and the whole company at an all-hands once every 2/3 weeks. That's it, those are all the scheduled meetings. We have optional “water cooler”-style hangouts as well.
• 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.

Being an engineer at Trinsic is about a lot more than code, it’s really about helping us iterate as quickly as possible through the most viable customer input and ideas to get to Product Market Fit.

We’re looking for people that are a Barrel, a senior engineer that can help us take on some of the big projects and pivots we’re considering, someone with high autonomy, comfortable taking on a lot of responsibility and a great collaborator. You should be excited to wear many hats, and anticipate your role will need to adapt to the company’s changing needs and likely require you to leverage very different styles and skills over time.

With the product management team, you want to be finding out what you should be working on, and why, rather than letting that all up to the product manager. This is not a job where you get your Github issues assigned and you churn through them. We want you to play with our competitors, listen in on customer calls and bring engineering insight to the internal product discussions.

You should be a reliable engineering counterpart to this product exploration phase, following the existing technical strategy while being flexible, enjoying the exploration of new tools, other systems and standards. You should be clear about the trade offs of solutions you’re proposing and not fall into the trap of exciting new technologies but have the wisdom of choosing boring choices (don’t worry, we use a ton of fun tech where appropriate). You’re joining Trinsic to help solve a big problem in a sustainable way.

We want you to own features end-to-end, and live and breathe the company’s Ownership value while doing that. Building up the specification, prototyping and validating with customers, to building it and validating it really solves the customer’s need, to analyzing and monitoring the metrics and ensuring it really reaches customer satisfaction. You get excited to know “how is your work really doing” and diving into the reasons why it perhaps isn’t.

We’re looking for a senior engineer that can help us take on some of the big projects and pivots we’re considering.

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 (we’re working to reduce our usage of that). Our frontends are written in React, and we use a tiny bit of Rust for native SDK development. We host our (micro)services in Kubernetes in Microsoft Azure and use Infrastructure As Code (Pulumi) 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.

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.