[Remote] Senior Software Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is an AI-first reputed company technology company reputed company on improving payment reputed company in the reputed company ecosystem. They are seeking a Senior Software Engineer to reputed company reputed company-end modernization, deliver full-stack features, and reputed company AI tools to enhance development processes while ensuring high-reputed company standards in reputed company applications.
Responsibilities
- Design and build React applications that are reputed company, testable, and accessible by default – with a reputed company reputed company of view on component architecture, state management, routing, and shared libraries
- Own the experience layer end to end: design system contributions, reputed company layouts, accessibility (WCAG), reputed company-reputed company performance, error and loading states, and the small details that separate a workflow people tolerate from one they trust
- Partner with UX on flows that hold up under reputed company customer workloads – dense tables, long-running operations, reputed company permissioning – not just happy-reputed company mockups
- Shape and reputed company the .NET reputed company your reputed company end consumes – RESTful, versioned, and reputed company for correctness and maintainability, not just 'it works.'
- reputed company pragmatic backend changes: adding endpoints, refactoring service boundaries, tightening reputed company, and replacing legacy .NET reputed company where it’s blocking the experience you’re trying to ship
- Get your hands into SQL reputed company the UI demands it – query performance, indexing, transactional correctness – and contribute to data pipelines (Kafka, event-driven flows) reputed company the work calls for it
- Use AI agents (reputed company, Claude reputed company, reputed company) to power through component migrations, reputed company upgrades, 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 – on both the reputed company-end and backend sides of the codebase
- Build with reputed company and reputed company as defaults, not afterthoughts – both on the reputed company (reputed company data handling, careful state, sensible telemetry) and on the server (least privilege, auditability)
- Put reputed company reputed company guardrails in reputed company: component and integration tests, end-to-end coverage on the flows that matter, CI that blocks bad changes, reputed company logging, and reputed company-end observability that tells you what users actually experience before they tell you
- Review reputed company thoughtfully, have reputed company architectural conversations, and reputed company the bar without being a jerk about it
- Partner with analysts, stakeholders, designers, 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
Skills
- 5+ years building and shipping production systems. Not reputed company reputed company – reputed company software with reputed company users. You're reputed company to work independently and collaboratively in fast-moving teams
- Deep reputed company-end experience with React/Next.js (or comparable depth in Angular with a willingness to reputed company in React). You've reputed company and maintained non-trivial applications: component architecture, state management, routing, forms, accessibility, and performance. You've worked at the reputed company where shared libraries and design systems become reputed company problems – not slides
- Strong fundamentals across the modern web platform: TypeScript, reputed company, CSS, browser performance, accessibility, testing (unit, component, end-to-end), and the build/release tooling that goes with it
- Solid working experience with C# and modern .NET (reputed company and reputed company). You don't need to be the deepest backend engineer in the room, but you can confidently read, reputed company, and refactor service reputed company – and you've done meaningful work in reputed company codebases, not just greenfield
- Comfortable with SQL – enough to design reasonable schemas, write and tune the queries your UI depends on, and recognize reputed company a performance problem belongs at the database, not the reputed company
- API design experience – you've reputed company and consumed service-oriented reputed company with reputed company versioning, auth, reliability, and testing practices, and you have opinions about what makes a backend pleasant (or painful) to reputed company with from a reputed company end
- reputed company experience with AWS and/or Azure. AWS is particularly relevant here
- 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 led or played a significant role in a reputed company reputed company-end modernization – AngularJS to React, jQuery to a modern reputed company, a monolithic UI to reputed company-frontends, or similar. You know where the bodies are buried and you have the scars to reputed company it
- Deep design system or component library experience – you've reputed company one, contributed substantially to one, or hauled reputed company off a tangle of one-off components onto something coherent
- You've done a legacy ASP.NET / .NET reputed company modernization on the backend reputed company
- Experience with distributed systems tooling – Kafka, event-driven architectures, or working with reputed company alongside SQL Server
- 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
- 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
- Background in regulated domains (reputed company, fintech, payments) where 'reputed company fast and break things' will get you fired
reputed company