.NET 后端工程师
.NET Back-end Engineer
关于Linkfire和团队
Linkfire是音乐行业用来将粉丝与他们喜爱的音乐连接起来的营销平台。成千上万的艺术家和唱片公司每天使用我们的智能链接，并依靠我们的报告来了解他们的活动表现。每一次点击都通过我们的平台，毫秒级地跳转到正确的流媒体服务，每天数百万次。
我们的.NET服务承载了平台的大部分功能：产品运行的API、与主要流媒体服务的集成、确保链接在各平台有效的扫描功能，以及支持粉丝沟通的电子邮件营销集成。
工程团队规模小且分布广泛，这意味着更广的覆盖面和真正的所有权，而不是一丁点的职责。你将与多年来构建这个平台的工程师一起工作，他们会花时间带你了解整个系统的运作方式。
你将负责
· 从路线图中的一个条目，经过规格说明，最终部署到生产环境，包括代码前的思考和代码后的跟进，而不仅仅是实现。
· 独立负责平台中的一块功能，随着你对系统的学习，逐步扩大职责范围。
· 构建前端和数据团队依赖的API，因此设计决策是在与他们协作中做出的，而不是被单方面交付的。
· 将大任务拆分成可发布的部分，尽早标记风险，并清楚说明何时会延迟。
· 向非技术人员解释你在做什么以及为什么这么做。
· 将生成式AI作为工作流程的一部分。
我们寻找
· 三年或以上构建.NET服务和API的经验，具备足够的深度，可以独立将中大型功能部署到生产环境，无需他人监督。
· 能够从路线图条目到规格说明再到可用软件的完整流程，包括在编写任何代码之前提出需要回答的问题。
· 实用主义。你选择最简单的可行方案，并能解释你所做的权衡。
· 你已经在日常工作中使用AI，并对它在哪些地方有帮助、哪些地方造成阻碍形成了自己的看法。申请时请告诉我们，我们期待你这样做。
· 好奇心不止于你自己的技术栈。我们采用T型人才模式，比起更长的技术列表，我们更看重在.NET上的深度以及对周边技术的真实兴趣。
· 你能表达自己的想法，包括当你的观点与更有经验的人不同时。
· 清晰的写作能力。我们的大多数沟通都是书面形式
查看英文原文
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.
- Clear writing. Most of our communication is asynchronous and written.
- A bachelor's degree in Computer Science, Software Engineering, or equivalent practical experience.
The stack
- .NET 10, with ASP.NET Core Web API and gRPC for the internal and public-facing APIs we run at scale.
- EF Core on SQL Server for data access, with Elasticsearch for search and Redis for caching.
- AWS as our cloud platform, with SQS and SNS for messaging between services.
- Docker and Kubernetes for containerised deployment.
- GitHub, GitHub Actions and Terraform for CI/CD and infrastructure as code.
- OpenTelemetry with Grafana, Mimir and Tempo for observability and monitoring in production.
- NUnit and Testcontainers for unit, integration, end-to-end and performance testing, as part of the workflow rather than after it.
Nice to have
- Experience designing APIs that other teams consume, and an API-first mindset.
- Experience working asynchronously in a distributed team where you had to own decisions yourself.
- Exposure to the pieces around the backend: frontend, data, or cloud infrastructure.
Location
Anywhere within European timezones. Copenhagen office if you want one, fully remote if you do not. This is a full-time permanent role.
Why join Linkfire
- Engineers who will invest in you. You join people with deep knowledge of the platform whose explicit job is to bring you up to their level, not to hand you tickets.
- Scale you can see. Millions of fan interactions a day, and your work sits behind it.
- High ownership and real impact. A small team and a large platform, so what you build matters and you can point at it.
- Remote-first culture. Flexibility, and colleagues across several countries.
- Competitive compensation and benefits. A package that recognises your expertise and contribution.
Originally posted on Himalayas