Manager, Software Engineering

InComm Payments•Atlanta, GA

13d

About The Position

When you think of InComm Payments, think of Innovative Payments Technology. We were founded over 30 years ago and continue to be a pioneer in the payment (FinTech) industry. Since our inception, we have grown to be a team of over 3,000 employees in 35 countries around the world. We own over 400 global technical patents and a network that includes over 525,000 points of retail distribution that points to our industry expertise. InComm Payments works with the most recognized and valued brands in the world, and we are partnered with most of the world’s leading merchants. InComm Payments is highly focused on our people and their growth, and we work hard to make a career at InComm Payments meaningful and rewarding. We value innovation, quality, passion, integrity, and responsibility in all that we do, and we are looking for great people to join our team as we move forward towards a very bright future. You can learn more about InComm Payments by visiting our Website or connecting with us on LinkedIn, YouTube, Twitter, Facebook, or Instagram. We are seeking a Software Engineering Manager to 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. This position reports to the Director of Software Engineering. Why Join Us? A clear, visible mandate with senior leadership’s attention: strengthen the reliability of systems the business depends on 24x7. A strong technical foundation to build on — automated testing, continuous delivery, and an experienced team — with room to raise the operational bar. Own APIs and services that are directly relied upon by the business and its customers. Collaborative culture that values innovation, growth, and impact. Competitive compensation, benefits, and career growth opportunities.

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.
Ownership mindset — treats the health of production systems as personal accountability, not a shared abstraction.
Follows through — closes loops on commitments, corrective actions, and the unglamorous work that prevents the next outage.
Calm, decisive, and clear-headed under pressure.
Sound judgment about what to change and what to leave alone; improves a working system without destabilizing it.
Execution focus — consistently converts plans into delivered outcomes.
Strong communication skills with technical, product, and senior leadership audiences.
Ability to manage competing priorities in a fast-paced environment.
Coaching mindset and genuine investment in engineers’ growth.
Technically credible — able to engage in design and code discussions and hold a quality bar.

Nice To Haves

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).

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.