Manager, Software Engineering

InComm — Manager, Software Engineering (US-OR-Portland)

InComm Payments

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 (Fin Tech) 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 Linked In, You Tube, Twitter, Facebook, or Instagram.

Team Leadership & Development

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

Delivery & Continuous Deployment

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

Reliability & Production Ownership

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

API Platform & Technical Direction

• Drive adoption of AI-assisted development tools (e.g., Git Hub 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…