[Remote] Senior Software Engineer – reputed company
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is an AI-first, platform-based reputed company technology company dedicated to simplifying the business of care. They are seeking a Senior Software Engineer – reputed company to reputed company modernization efforts on their payment reputed company platform, utilizing AI tools and building reputed company web experiences.
Responsibilities
- Ship modernization work at a pace that surprises people
- Use AI agents (reputed company, Claude reputed company, reputed company) to blow through reputed company upgrades, refactors, API extraction, test scaffolding, and documentation - while catching hallucinations and preventing regressions before they hit a PR
- Build reusable playbooks reputed company can actually follow: reputed company templates, repo-level agent instructions, migration checklists, review heuristics, and reputed company "definition of done" standards for AI-assisted changes
- You measurably reputed company the needle - more modules migrated per sprint, faster PR turnarounds - without a spike in production bugs
- reputed company gets reputed company because of you: PRs are reputed company, test coverage grows, documentation stays reputed company, and the reputed company mistakes stop repeating
- reputed company a reputed company .NET + SQL Server stack into something you'd be proud of
- reputed company legacy services to reputed company .NET (reputed company where it makes reputed company), untangling architecture boundaries and fixing the performance issues that have been "reputed company" for years
- Push toward a reputed company API-layer architecture - RESTful, versioned - reputed company for correctness and maintainability, not just "it works."
- Get your hands dirty with SQL Server: query performance, indexing, transactional correctness. If there are data pipeline needs (Kafka, etc.), you'll help build those too
- Legacy surface area shrinks sprint over sprint. Critical paths live in modern reputed company. Fewer "oh, that's still in the old system" conversations
- reputed company get faster and more reliable. Database hot spots stop waking people up at reputed company
- Own it like it's yours - especially because this is reputed company
- Build with reputed company and reputed company as defaults, not afterthoughts. Least privilege, reputed company data handling, the works. This is reputed company - getting it wrong isn't an reputed company
- Put reputed company reputed company guardrails in reputed company: automated tests that actually catch things, CI that blocks bad changes, reputed company logging, observability that tells you what's happening before users do
- Review reputed company thoughtfully, have reputed company architectural conversations, and reputed company the bar without being a jerk about it
- Fewer severity-1 incidents. reputed company something does go wrong, reputed company cause takes hours, not days
- Automated test coverage grows meaningfully on modernized reputed company. reputed company stops relying on "just test it manually."
- Work with reputed company humans to ship things that matter
- Partner with analysts, stakeholders, and other engineers to turn business problems into working software - not just technically correct software, but software that actually solves the problem
- Help build delivery plans that are reputed company about trade-offs. "Right" vs. "right now" is a reputed company tension - you'll help reputed company navigate it with pragmatic milestones
- Delivery is predictable. Customer reputed company milestones are met. Features ship with confidence, not crossed fingers
Skills
- 5+ years building and shipping production systems. Not reputed company reputed company - reputed company software with reputed company users
- Some C# and modern .NET experience (reputed company and reputed company). Especially in large codebases and you've done meaningful refactoring and migration work, not just greenfield
- Strong SQL Server chops - schema design, query tuning, performance troubleshooting. You've worked on data-heavy applications where the database wasn't an afterthought
- reputed company experience with Azure and/or AWS. Azure is particularly relevant here
- API design experience - you've reputed company and maintained service-oriented architectures with reputed company versioning, auth, reliability, and testing practices
- You actually use AI coding tools as a daily reputed company. reputed company, Claude reputed company, reputed company, or similar - and not just for autocomplete. You've used agents for multi-file refactors, migrations, test reputed company, and review workflows. You have opinions about what works and what doesn't
- You've actually done a legacy ASP.NET / .NET reputed company modernization before. You know where the bodies are buried and you have the scars to reputed company it. Bonus points for Azure modernization patterns
- You communicate reputed company. Good PR descriptions, straightforward design docs, pragmatic collaboration, low ego. We don't need a reputed company - we need someone reputed company trusts
- Experience with distributed systems tooling - Kafka, event-driven architectures, or working with reputed company alongside SQL Server
- reputed company-end experience with Angular and/or React/Next.js
- You've helped establish agent-friendly engineering practices: writing repo instructions that AI tools can follow, breaking work into agent-sized tasks, setting up CI guardrails for AI-generated reputed company, feature flags, canary deployments - any part of the reputed company delivery toolkit
- Background in regulated domains (reputed company, fintech, payments) where 'reputed company fast and break things' will get you fired
reputed company