Senior Software Developer, CRM Platform; C# and ASP.NET

Senior Software Developer, CRM Platform (C# and ASP.NET)
Job Type: Contractual No. of Vacancies: 1

Experience:

4 Years+

Riseup Labs is looking for a  Senior Software Developer, CRM Platform (ASP.NET).  We are hiring for our client, a Canadian SaaS company in the landing page, conversion optimization and CRM space, currently going through an AI-first product transformation. This is a backfill role on the client’s CRM platform engineering team, reporting to engineering leadership. They will build and support the CRM platform, which runs on ASP.NET

MVC and .NET Framework 4.8 alongside AWS services. They will work in an existing codebase from the first week, so reading unfamiliar code and changing it safely matters more than greenfield design.

Job Responsibilities:

Design and implement scalable, maintainable features and fixes for the CRM platform.

Write modular, testable code and give thoughtful code reviews.

Build and support solutions using AWS services such as Lambda, S3, EC2 and DynamoDB.

Work across service boundaries and understand how systems depend on each other.

Use Team City, Octopus and monitoring tools such as Datadog, Raygun, Papertrail and Cloud Watch to ship safely.

Apply web application security and performance practices, including mitigation of common vulnerabilities.

Break complex problems into well-scoped tasks and give accurate estimates.

Support onboarding and knowledge sharing for newer developers through code reviews and pairing (informal, with no people management).

Join the team’s two-week Release Developer and Production On-Call rotations once production access is approved. Until then, work on features, code reviews and business-hours support.

About the rotations

Release Developer : coordinates release builds, makes sure changes merge on time, and deploys to production.

Production On-Call : first responder to Pager Duty and Slack alerts, 24/7, with a 15-minute response before the alert escalates to engineering leadership. Playbooks exist for each alert type.

Frequency : about one two-week rotation every four weeks. A developer is never on both rotations at the same time.

Typical alert volume:

About 2-3 pages a week across the team, mostly early morning (6-9 AM PT) or evening.

True overnight pages (10 PM - 7 AM PT) average about one a week.

About 60% clear on their own or need only a quick check.

Roughly once every two weeks, an incident needs hands-on action, such as restarting services, taking a memory dump, or working with infrastructure on a load balancer or host issue.

Real incidents usually last 15 minutes to a couple of hours.

A few times a quarter, one problem triggers 20-40 alerts, which counts as a single incident.

Phased Start : a shadowing period before taking on rotations is expected.

Requirements:

4+ years of professional software engineering, delivering production software.

Hands-on AWS experience with at least two of Lambda, S3, EC2 and DynamoDB.

Strong understanding of object-oriented programming, software architecture and design patterns.

Experience with CI/CD pipelines, production monitoring and Dev Ops practices.

Experience carrying a 24/7 on-call rotation and responding to production incidents.

Experience working in a large existing codebase written by others.

Experience mentoring or leading less experienced developers.

Ability to work a full Pacific Time business day.

Additional Requirements:

Nice to have

Team City, Octopus, Pager Duty and Datadog

Migrating legacy .NET Framework code to modern .NET

Windows-hosted .NET applications alongside AWS services

CRM or B2B SaaS platform experience

Designing APIs alongside a mobile team

Culture fit

Owns a system end to end and stays calm under a 2 AM page.

Shows honesty when something will take longer than hoped, rather than hoping it…