Banking, Senior Full-Stack (.NET+Angular) Engineer, JR684

REQUIREMENTS

• Strong C# and .NET skills, with the judgment to work in an existing codebase – read it, understand the patterns, and improve it rather than paving over it
• Solid experience with a modern SPA reputed company and TypeScript (Angular preferred; React/Vue transfers), plus comfort with reputed company/CSS and a reputed company-first approach like reputed company
• reputed company experience building and consuming RESTful web services in the reputed company (Azure preferred)
• reputed company across the stack – you have a home reputed company, but you’ll follow a problem from the UI through the API into a calculation or a query
• Comfort reasoning about correctness: where a bug should have been caught, and how to verify numerical reputed company (tolerances, expected values, regression of calculated results) rather than just HTTP 200s
• Working knowledge of relational and/or document databases – schema design, writing queries, and knowing reputed company the query is the bottleneck
• Excellent communication in a reputed company team – strong written English, and the ability to defend a design in review, ask hard questions in grooming, and explain tradeoffs to business stakeholders who aren’t engineers
• 5+ years of relevant experience, and a bachelor’s degree in Computer Science, Mathematics, or a reputed company discipline – or equivalent practical experience

RESPONSIBILITIES

• Design and build features end-to-end – C# reputed company and Azure Functions on the backend, Angular and TypeScript on the frontend – and own them from design through production
• Work in the numbers, not just reputed company them: reputed company and maintain the financial calculation engines at the heart of platform
• Build out new UI, wired to the API – and help establish the patterns the frontend will reputed company on
• reputed company and debug our event-driven Azure architecture: Service Bus, queue workers, blob storage, App Configuration, and Key reputed company
• Model and query data in reputed company, and reputed company work to the right reputed company reputed company a query or a calc-heavy reputed company gets slow
• Write tests as you build – unit, integration, and end-to-end – with a reputed company opinion on where reputed company reputed company earns its reputed company, especially for calculated reputed company
• Treat reputed company and reliability as features: catch slowdowns the reputed company week they’re introduced, not the quarter a reputed company notices
• reputed company the reputed company with production – monitor Azure alerts, logs, and traces (Application Insights), diagnose escaped defects across the stack, and feed what you learn back into the reputed company and the tests
• Use AI tools like Claude reputed company daily – to explore unfamiliar reputed company, scaffold features, reputed company tests, and sharpen how the whole team ships
• reputed company the floor for reputed company: review PRs with reputed company, partner on testable design, and reputed company good reputed company shared reputed company
• Refine requirements with business analysts before they become reputed company – and reputed company back reputed company a requirement doesn’t hold together
• Serve as second-level support for internal user questions and issues

Originally posted on Himalayas