Technical jobs / Archive listing

Healthesystems

Principal Appian Engineer

Healthesystems | Principal Appian Engineer | Remote (US - Most States) | Full-Time | $119k-164k

Location
Remote (US - Most States)
Work mode
Remote
Employment
Full-time
Compensation
$119k-164k
Posted
Source author
@brunz36

About Healthesystems

Healthesystems is a specialty provider of innovative medical cost management solutions for the workers’ compensation industry. Our diverse suite of services includes a leading Pharmacy Benefit Management (PBM) program and Clinical Review Services as well as a revolutionary Ancillary Benefits Management (ABM) program for managing and adjudicating ancillary medical services.

Company website: healthesystems.com

Original job description

Healthesystems | Principal Appian Engineer | Remote (US - Most States) | Full-Time | $119k-164k

Healthesystems is a specialty provider of innovative medical cost management solutions for the workers’ compensation industry. Our diverse suite of services includes a leading Pharmacy Benefit Management (PBM) program and Clinical Review Services as well as a revolutionary Ancillary Benefits Management (ABM) program for managing and adjudicating ancillary medical services.

Tech Stack(Job Scoped): Appian, SQL Server, MongoDB, Kafka

Role Overview: The Principal Engineer is responsible for establishing and governing Appian design patterns, development standards, and platform governance across the organization. In this capacity, you will define best practices, enforce architectural principles, and ensure consistency in Appian application development enterprise-wide. This includes architecting and implementing seamless integrations between Appian and the existing technologies, including containerized microservices on k8 and SQL Server.

Apply at: https://healthesystems.com/careers-list/?gh_jid=7587287003

I will do my best to keep an eye here. Have a great day. You can also reach me(Bruno Ribeiro Principal Engineer) at:

https://www.linkedin.com/in/bruno-engineer/

Open application

View original source post