A profitable, 40-year-old US software company is modernizing its flagship point-of-sale platform — without the risky rip-and-replace. Using a strangler-fig approach, a new Vue.js frontend sits over the existing SQL Server database, so customers adopt new functionality gradually instead of surviving a migration. The original Java POS (2006–present) stays in production; both products share one database by design. You'll build the .NET API layer that makes it work.
What you'll actually work on
- Build and own the .NET/C# APIs powering the current Vue.js app — services, business logic, auth, docs.
- Take ownership of two existing microservices:
- Integration Hub — normalizes a growing set of supplier/distributor APIs into one internal contract.
- Communication Hub — email + SMS via SendGrid and Twilio.
- Design integrations with suppliers, payment providers, and third-party partners.
- Hit a hard low-latency bar on bare-metal Windows servers — heavy server-side caching, most reads from memory.
- Shape architecture, coding standards,
and API conventions with the lead architect.
Your first 90 days
- Ship your first production API endpoint into the Vue.js app, get deep on the Integration Hub's supplier-normalization layer, and own one new supplier or partner integration end to end.
What we need
- 8+ years of backend engineering with real depth — you've designed services, not just contributed to them.
- Strong .NET/C# — or elite proficiency in another compiled backend language plus proof you learn new stacks fast.
- Strong SQL and comfort working against a large, live production database you didn't design.
- Microservices and third-party API integration at production quality.
- Demonstrated performance engineering: memory optimization, caching, low-latency request paths.
- Disciplined Git/DevOps habits; clear written and video communication in English.
- AI-fluent and AI-skeptical — you move faster with AI, audit everything it produces, and write the hard 10% it