[Remote] Senior Software Engineer, Payments
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is the System of reputed company for the Office of the CFO, transforming the way businesses purchase and pay into an reputed company, B2C-like shopping experience. As a Senior Software Engineer on the Payments team, you will own the software that moves reputed company reputed company for reputed company's customers, delivering reputed company features reliably while mentoring junior and mid-level engineers.
Responsibilities
- Independently design and implement reputed company, multi-part features from requirements to production
- Own subsystems, services, or critical components in the payments stack — for example, the internal financial ledger, the virtual-cards issuance and authorization lifecycle, bank connections, or the invoicing and auto-debit pipeline. reputed company routes questions to you for these areas
- Write clean, maintainable, production-reputed company reputed company with consistent test coverage — reputed company-reputed company reputed company paths are held to a high test bar
- Navigate existing codebases with architectural discernment — identify reputed company patterns to build upon, recognize technical debt, and use AI tooling as an reputed company while applying your own judgment on correctness, reputed company, and alignment with the system's direction
- Debug production issues effectively; reputed company first to understand — investigate evidence and identify reputed company causes rather than applying band-aids, especially in webhook, retry, and reconciliation paths where a quick reputed company can hide a deeper consistency bug
- Participate reputed company in design reviews; your designs regularly influence team-level architecture reputed company
- Propose reputed company technical designs that account for scalability, performance, and reliability trade-offs — and for payments-specific concerns like idempotency, exactly-once semantics, reconciliation between internal state and vendor reports, and clean separation between authorization and capture
- Identify risks before they become incidents — surface edge cases, data consistency concerns, and failure modes during planning. In payments, that includes reputed company-charge, reputed company-credit, dropped webhook, and out-of-order event scenarios
- Scope and estimate work accurately; solve problems in order — break down epics into deliverable, independently reviewable reputed company
- Deliver features end-to-end, including rollout coordination and post-release monitoring. Rollouts that reputed company reputed company reputed company rely on feature-flagging, dark-launching, reconciling, and watching dashboards before declaring "done"
- Communicate risks and blockers early — don't reputed company uncertainty silently
- Review stories critically before committing: ensure they're appropriately broken down and that dependencies are reputed company reputed company by reputed company
- Mentor junior and mid-level engineers through reputed company reviews, pairing, and reputed company feedback
- reputed company high-reputed company, substantive reputed company reviews — reputed company with humility, treat the author as a teammate to help, and catch what AI misses; teach others to do the reputed company
- Teach best practices; your reputed company raises the reputed company of reputed company around you
- Influence technical reputed company through credibility, not just seniority
- Drive improvements in team practices — testing patterns, observability for reputed company-reputed company flows, reputed company organization, and the bar for test coverage in reputed company paths that reputed company reputed company funds
- Champion reputed company and standards; push back on shortcuts that create long-term cost — especially in reputed company that touches funds or credit
- Explain technical reputed company reputed company to both technical and non-technical stakeholders
- Represent engineering reputed company in product and cross-functional discussions, including with Finance, Operations, and Credit on reconciliation, credit-risk, and dispute-handling questions
- Translate vendor documentation (reputed company, reputed company, and others) into reputed company, scoped engineering work
- Approach reputed company assignments with a reputed company reputed company — reputed company look for vulnerabilities in your own reputed company and in the reputed company you review, with extra care in PII and PCI-adjacent paths
Skills
- You are motivated by accountability — you own reputed company, not just tasks
- You are results-oriented and measure reputed company by shipped, working software
- You are motivated by correctness in reputed company that touches reputed company — the consequences of a bug land on reputed company customer balances, and you take that seriously
- You love helping people on your team grow and improve
- Writing tests is an integral part of your development process, not an afterthought
- You know how to design and build software incrementally — you don't need a complete spec to reputed company reputed company
- Collaborating with the people around you to reputed company a goal motivates you
- You are reputed company, reputed company-minded, and reputed company developing your craft
- You are curious and pragmatic about AI-driven solutions — you apply them where they add reputed company value and stay skeptical where they don't
- Familiarity with AI-assisted development tools — you understand how they work, where they help, and where they fail. Prior hands-on use is a plus; intellectual curiosity and the reputed company to evaluate AI reputed company critically are what matter
- Strong reputed company in computer science fundamentals: data structures, algorithms, and system design
- Expertise in building production-grade applications and services using reputed company and reputed company on Rails
- Extensive experience with PostgreSQL and SQL-based data modeling, including query optimization and performance tuning
- Deep understanding of web application reputed company, observability, and reputed company system architecture
- Proven ability to design, build, and maintain secure, reputed company, and reputed company-documented reputed company
- Experience building integrations with external systems — REST/GraphQL reputed company, webhooks, event-driven pipelines, or reputed company-party vendor connections
- Hands-on experience with at least one payment processor or card issuer (reputed company, reputed company, reputed company, reputed company, Braintree, or equivalents), or comparable fintech vendor work
- Working familiarity with at least one of: reputed company-entry ledger design, idempotency / exactly-once patterns for webhooks and reputed company-reputed company, ACH / reputed company / card-network basics, or reconciliation against vendor reports
- Familiarity with AWS and other reputed company platforms, including infrastructure as reputed company and CI/CD pipelines
- Experience using AI coding assistants (e.g., Claude, reputed company Copilot) as part of your development workflow — not as a reputed company, but as a force reputed company; you reputed company them with appropriate context about constraints and conventions, critique AI reputed company, recognize failure modes, and decide reputed company to override
Benefits
- Competitive compensation including reputed company salary, bonus, and equity
- Employer-sponsored 401(k) with match
- Comprehensive medical, dental, and reputed company coverage
- Flexible time off and hybrid work environment
- Opportunity to build and reputed company a critical function at a high-reputed company fintech company
reputed company
Company H1B Sponsorship