Staff Software Engineer (Dentrix)

Henry Schein One is hiring a Staff Software Engineer to lead engineering across dental payments, financial workflows, and electronic healthcare claims. The role sets architectural direction, modernizes a Windows desktop application, and drives correctness, reliability, and technical leadership across teams.

Responsibilities:

• Own the correctness of money movement: posting, reconciliation, batch processing, billing, and statements ensuring transactions are accurate, idempotent, and auditable, with data integrity preserved end to end
• Lead the design and reliability of payment integrations, including card-present terminals, online payments, tokenization and cards on file, and third-party processors and harden these flows against partner outages, network failures, and partial results
• Drive engineering for real-time electronic claims over a national healthcare claims network, covering submission, retries, response parsing, and error handling so failures are rare, recoverable, and easy to diagnose
• Turn regulatory and fee-schedule changes into correct, well-tested behavior on deadlines the business can rely on, partnering with product and compliance to get the details exactly right
• Lead the modernization of legacy native C++ modules and the C++/CLI interop layer toward the managed, layered C# architecture, lowering risk and tech debt without changing behavior customers depend on
• Improve performance and reliability in high-traffic financial and claims workflows, and back it with telemetry so regressions get caught before customers feel them
• Set the testing strategy using TDD, dependency injection, and clean seams to keep business logic testable away from native and infrastructure dependencies, and grow real coverage on the code paths that handle money
• Hold architectural guardrails across a codebase made of many projects and packages: keep domain boundaries clean and coordinate package and version alignment as components ship on their own timelines
• Lead production troubleshooting for financial and integration incidents – Get to root cause and land durable fixes that protect both data integrity and customer trust
• Build cross-team roadmaps that span six to twelve months, plan and sequence the work realistically, and grow other engineers through design reviews, pairing, and code review

Requirements:

• To be considered, candidates must be authorized to work in the United States for Henry Schein One without the need for current or future employer sponsorship
• 8 or more years building solid Windows desktop and backend enterprise applications in C#/.NET and C++, or an equivalent mix of education and experience
• A real track record of technical leadership at the staff level: setting architecture, influencing across teams, and lifting standards without leaning on a title to do it
• Experienced with object-oriented design, SOLID, clean and layered architecture, and MVVM, backed by dependency injection and unit testing
• Background in transactional or financial systems, or anything else where being correct and auditable isn't optional
• Comfort moving around a codebase that's part native and part managed, including C++/CLI or P/Invoke interop between older C++ and newer C#
• A strong grip on relational or embedded data stores (FairCom c-treeACE, SQL Server, or similar) and the judgment to evolve legacy data models without breaking things
• A history of building cross-team roadmaps in an agile environment and estimating work over six-to-twelve-month horizons
• Sharp debugging instincts in production, integration-heavy systems, especially where money is moving or third-party APIs are involved
• Clear communication and a genuine instinct to mentor, with a preference for a collaborative, knowledge-sharing culture across engineering, QA, support, product, and compliance
• Bachelor's Degree in Computer Science or a related field
• Prior experience as a team or technical lead
• Hands-on experience with dental or healthcare claims or other regulated healthcare data
• Payments experience with PCI-minded engineering habits around tokenization, card-on-file, the card updater, and careful handling of cardholder data in code
• Experience modernizing legacy Win32 or MFC desktop financial modules toward layered or service-oriented designs
• Familiarity with FairCom c-treeACE, or with migrating off CodeBase/DBF-style data
• Experience with Crystal Reports or a similar reporting for financial and practice-analysis reporting
• Comfort instrumenting analytics to track performance and adoption and catch regressions early
• Some exposure to Behavior-Driven Development (BDD)