> Markdown version of [/jobs/ext/2716790-software-engineer-rejections-denials](https://www.wearedevelopers.com/jobs/ext/2716790-software-engineer-rejections-denials). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer, Rejections & Denials - **Company:** Commure Inc. - **Location:** United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Code Review, Python (Programming Language), Nagios, Rule Engine, Software Engineering, TypeScript, ReactJS, Large Language Models, Backend, Git, Kubernetes, Information Technology, Front End Software Development, Docker - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/senior-software-engineer-rejections-denials-commure-8399096 ## About the Role * Bachelor's or Master's degree in Computer Science, Engineering, or a related field, or equivalent extensive experience * 5+ years of professional software development industry experience * Proficiency in frontend languages like Typescript and React. * Proficiency in backend languages like Python or Go. * Experience including but not limited to Git, GCP / AWS, Docker, Kubernetes, relational and non-relational DBs, and monitoring/alerting tools * Proven track record of designing and implementing end-to-end solutions and making successful architectural decisions * Excellent communication and collaboration skills, with the ability to work in a fast-paced, dynamic environment. ## Description At Commure, our Revenue Cycle Management (RCM) Core team is building the autonomous backend that turns healthcare's most manual financial workflows into intelligent systems. The Rejections & Denials team builds the AI and rules infrastructure that fixes claims autonomously. The team is turning what used to be repetitive human work (reading a denial, figuring out the fix, correcting the claim, resubmitting, appealing) into auditable, automated workflows. What You'll Do * Build LLM-powered automation that decides how to fix a denied claim, with evals, dry runs, and audit trails rigorous enough to let it act autonomously on real money. * Design guardrails that keep automation safe: identity guards, payer-type guardrails (dental, Medicare A vs. B), duplicate-prevention, and dry-run / QA gates before anything touches production. * Scale a rule engine that runs hundreds of configurable conditions and actions per customer across high transaction volumes - safely, idempotently, and with full explainability for operations teams. * Build the observability that turns a long tail of edge cases into a prioritized roadmap: dashboards for automated resubmission approval rate, denial-to-resubmission cycle time, and failure rates broken down by insurance type, denial category, and site. * Generate appeal letters and medical-record packets automatically, with validation scoring that decides what's safe to send unattended. * Deliver a unified automations console where ops can see and manage every rule engine (billing rules, pre-submission validation, adjustments) in one place. * Contribute to the technical direction of the RCM platform by proposing and implementing improvements to architecture, tools, and technologies. * Build end-to-end products to revolutionize revenue cycle management for providers and administrators * Take ownership of end-to-end integration workflows, from design and development through to deployment and post-launch monitoring. * Collaborate with cross-functional teams (product, engineering, and healthcare) to gather integration requirements, define technical approaches, and prioritize tasks based on business needs. * Mentor and guide engineers, fostering a culture of technical excellence and continuous learning * Conduct in-depth code reviews, uphold best practices, and drive architectural improvements across the stack ## Related Videos - [Hiring AI Native Talents](https://www.wearedevelopers.com/videos/100268-hiring-ai-native-talents) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Building the Next Generation of Software](https://www.wearedevelopers.com/videos/100186-building-the-next-generation-of-software) - [Docker build without Docker](https://www.wearedevelopers.com/videos/100114-docker-build-without-docker) - [Git for Code Reviews](https://www.wearedevelopers.com/videos/429-git-for-code-reviews) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [React Developer Salary [2023]](https://www.wearedevelopers.com/magazine/198-react-developer-salary-2023) - [Résumé-Driven Development: How IT trends affect the job market for software developers](https://www.wearedevelopers.com/magazine/59-resume-driven-development-how-it-trends-affect-the-job-market-for-software-developers) - [Should senior developers refuse interview coding challenges?](https://www.wearedevelopers.com/magazine/29-should-senior-developers-refuse-interview-coding-challenges)