.NET Back-end Engineer

About this role

About Linkfire and the team Linkfire is the marketing platform the music industry uses to connect fans with the music they love. Thousands of artists and labels use our smart links every day, and rely on our reporting to understand how their campaigns perform. Every click runs through our platform and lands on the right streaming service in milliseconds, millions of times a day. Our .NET services carry a large part of the platform: the APIs the product runs on, the integrations with the major streaming services, the scanning that keeps links valid across them, and the email marketing integrations behind fan communication.

Engineering is small and distributed, which means a wide surface area and real ownership rather than a slice of a slice. You would work alongside the engineers who have been building this platform for years, and they will spend real time bringing you into how it all fits together. What you will do Take .NET and API work from a roadmap item through spec to production. The thinking before the code and the follow-through after it, not only the implementation.

Own contained parts of the platform end to end, and grow that scope as you learn the systems. Build the APIs the frontend and data sides of the team depend on, so design decisions get made with them rather than handed over. Break large work into pieces that is shipable, flag risk early, and say clearly when something is going to be late. Explain what you are building, and why, to people who are not engineers. Use generative AI as part of how you work.

What we are looking for Three or more years building .NET services and APIs, with enough depth that you can take a medium to large feature to production without anyone checking on you. The ability to go from a roadmap item to a spec to working software, including asking the questions that need answering before any code gets written. Pragmatism. You pick the simplest thing that works and can explain the trade-off you made.

You already use AI in your daily work and have formed opinions about where it helps and where it gets in the way. Tell us about it when you apply, we expect you to. Curiosity that does not stop at your own stack. We work T-shaped, so depth in .NET with real interest in the surrounding pieces matters more to us than a longer list of technologies. You say what you think, including when you disagree with someone more experienced than you.