Impress employers and recruiters.
Choose from hundreds of resume examples.

Target Resume Now

Tailor your resume to this Manager, Software Engineering role.

Rezi rewrites your resume against InComm Payments's job description. Free.

Resume score gauge reading 58 out of 100

Don't guess if your resume is good enough.

See how it scores against the Manager, Software Engineering posting at InComm Payments — free, in seconds.

About the Role

Lead a seasoned Agile team responsible for a mission-critical set of APIs and services built primarily on C# and .NET. The role centers on delivery along with operational discipline — reliable services, accountability and ownership of our systems.

Responsibilities

Lead, coach, and grow a team of experienced software engineers, including senior engineers and tech leads.
Own hiring, onboarding, goal setting, performance reviews, and career development for the team.
Set and hold a high standard for ownership, diligence, and follow-through — raising the operational bar while keeping an experienced team engaged and bought in.
Build a culture where engineers feel genuine ownership of the systems they run: production health is the team’s responsibility, not someone else’s.
Address performance and accountability issues directly and fairly.
Identify skill gaps and create development plans that strengthen team capability over time.
Own and continuously improve an established continuous-delivery pipeline — progressive and canary rollout, automated rollback, and zero-downtime database and schema migrations.
Manage capacity, backlog readiness, and dependencies so the team has a clear, achievable plan.
Track and report engineering performance using deployment frequency, lead time for change, change failure rate, and mean time to restore, alongside SLO attainment.
Protect trust in the pipeline: eliminate flaky tests and keep the path to production fast, green, and safe to use.
Hold the line on pre-deployment verification, peer review, and change practices — automation raises the bar for diligence rather than replacing it.
Surface risks, blockers, and trade-offs early, with clear options and recommendations.
Establish unambiguous ownership for every service the team runs — a named owner, current runbooks, and a documented escalation path.
Own SLOs and SLAs for the team’s services and manage error budgets as a real constraint on the pace of change.
Own observability and alert quality — ensure the team can detect, diagnose, and resolve issues quickly, and that alerts are actionable rather than noisy.
Set and enforce clear expectations for production response: acknowledgement and escalation timeliness, communication during an incident, and urgency proportional to customer impact.
Serve as an incident commander and escalation point; run blameless postmortems that produce concrete corrective actions.
Treat repeat incidents as unacceptable — drive postmortem actions to completion and verify the fix held.
Regular operational review of reliability metrics, open incident actions, alert noise, and on-call load.
Own capacity planning, load and resilience testing, and participation in disaster-recovery and failover exercises.
Available to be on call to work with team to address production issues when necessary.
Drive adoption of AI-assisted development tools (e.g., GitHub Copilot, Claude Code) with appropriate guardrails for mission-critical code — usage guidelines, review standards, and measured impact on productivity and quality.
Uphold backward compatibility and API versioning discipline; coordinate breaking changes carefully with downstream consumers.
Ensure contract and integration testing coverage across consuming systems and services.
Guide the team on design and implementation decisions for .NET-based services, escalating architectural decisions to the Director and architecture group as appropriate.
Uphold engineering standards through code review expectations, automated testing, and definition-of-done discipline.
Manage technical debt deliberately — treat the automation and test suite as a core asset, and balance new feature delivery against platform stability and maintainability.
Operate within PCI DSS, SOC, HITRUST and related change-control requirements without sacrificing delivery speed.
Ensure audit evidence is produced by the pipeline itself rather than by manual ceremony.
Partner with security, risk, and compliance teams on assessments, remediation, and control validation.
Partner with product management, QA, DevOps, and other business units to ensure seamless delivery.
Translate business priorities into clear engineering work and communicate status in terms stakeholders understand.
Report reliability and delivery performance to senior leadership transparently — including bad news early — so confidence in the team is grounded in evidence.
Communicate clearly and promptly with business stakeholders during and after customer-impacting incidents.
Coordinate with peer engineering managers and consuming teams on shared platforms, standards, and cross-team dependencies.

Requirements

Bachelor’s degree in Computer Science, Engineering, or related field.
5+ years of experience managing software engineering teams, including direct people-management responsibility (hiring, performance, and career development).
8+ years of overall experience in software development with Microsoft technologies such as .NET and SQL Server.
Hands-on experience adopting and scaling AI-assisted development tools such as GitHub Copilot or Claude Code within an engineering team, including setting usage guidelines and measuring productivity and quality outcomes.
Experience operating in a mature continuous-delivery environment — frequent production deployments against high-availability targets. Experience sustaining and improving such an environment is more relevant here than experience introducing one.
Production ownership of customer-facing or revenue-critical systems, including accountability for uptime and SLA commitments.
Direct incident command experience, with a track record of driving postmortem actions to closure and eliminating repeat incidents.
Demonstrated success raising the operational bar on an existing team — establishing service ownership, response expectations, and follow-through discipline.
Hands-on experience with observability tooling (NewRelic, Splunk, or similar).
Working knowledge of cloud platforms (Azure preferred), microservices, and API-first design, including versioning and backward-compatibility practices.
Familiarity with relational databases and application performance troubleshooting.
Solid understanding of CI/CD pipelines, automated testing, and DevOps tooling.
Experience delivering in a regulated environment (PCI DSS, SOC, or equivalent change-control regimes).
Background in payments, financial services, healthcare, or other regulated industries.
Experience with front-end frameworks (Angular).
Experience managing distributed or hybrid teams.
Certifications in Azure, .NET development, or Agile/Scrum (CSM, PSM, SAFe).

Skills

C#
.NET
Agile
API development
Service development
Operational discipline
Reliable services
Accountability
Ownership
Continuous delivery
Automated testing
Progressive rollout
Canary rollout
Automated rollback
Zero-downtime database migration
Schema migration
Capacity management
Backlog management
Dependency management
Deployment frequency tracking
Lead time for change tracking
Change failure rate tracking
Mean time to restore tracking
SLO attainment
Pre-deployment verification
Peer review
Service ownership
Runbooks
Escalation path documentation
SLOs
SLAs
Error budgets
Observability
Alerting
Incident command
Blameless postmortems
Corrective actions
Capacity planning
Load testing
Resilience testing
Disaster recovery
Failover exercises
On-call support
AI-assisted development tools
GitHub Copilot
Claude Code
Backward compatibility
API versioning
Contract testing
Integration testing
Design decisions
Implementation decisions
Code review
Definition of done
Technical debt management
Test automation
Platform stability
Maintainability
PCI DSS
SOC
HITRUST
Change control
Audit evidence generation
Product management collaboration
QA collaboration
DevOps collaboration
Business unit collaboration
Stakeholder communication
Reliability reporting
Delivery performance reporting
Cross-team dependency coordination
Microsoft technologies
.NET Core
SQL Server
Azure
Microservices
API-first design
Relational databases
Application performance troubleshooting
CI/CD pipelines
DevOps tooling
Angular
Distributed teams
Hybrid teams
Azure certifications
.NET development certifications
Agile/Scrum certifications
CSM
PSM
SAFe
Ownership mindset
Follow-through
Calmness under pressure
Decisiveness under pressure
Clarity under pressure
Sound judgment
Execution focus
Strong communication skills
Managing competing priorities
Coaching mindset
Technical credibility

Experience Level

5+ years of experience managing software engineering teams
8+ years of overall experience in software development

Education Level

Bachelor’s degree in Computer Science, Engineering, or related field.

Benefits

Competitive compensation
Benefits
Career growth opportunities

About the Company

InComm Payments is a pioneer in the payment (FinTech) industry with over 30 years of experience.
The company has grown to over 3,000 employees in 35 countries.
InComm Payments holds over 400 global technical patents and a network of over 525,000 retail distribution points.
The company partners with recognized and valued global brands and leading merchants.
InComm Payments is highly focused on employee growth, making careers meaningful and rewarding.
Core values include innovation, quality, passion, integrity, and responsibility.

Equal Opportunity

InComm Payments provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, sexual orientation, gender identity or national origin, citizenship, veteran’s status, age, disability status, genetics or any other category protected by federal, state, or local law.