Senior Software Engineer, CDS - Provider Data

Want more jobs like this?

Get Software Engineering jobs that are Remote delivered to your inbox every week.

Get Jobs

Send me The Muse newsletters for the best in career advice and job search tips.

By signing up, you agree to our Terms of Service & Privacy Policy.

Initial Projects — What will you jump into on day one?

• Design, implement, and operate our provider and network service cost transparency API as a simple, easy-to-use abstraction layer over the underlying implementation
• Inherit ownership of the provider data pipeline and existing microservices that serve current provider data business use cases (e.g. personalized provider recommendations)

Desired Outcomes — What does success look like?

• Achieve team and business impact through high personal output
• Prioritize and scope engineering effort according to expected business value, effectively communicating with teammates and stakeholders
• Lead project execution by managing epics/stories/tasks, providing clarity to the business on delivery timing, and acting as an owner of overall project success
• Design, implement, test, and operate systems with exemplary engineering fundamentals that make appropriate tradeoffs
• Engage in cross-team and cross-functional efforts to ensure timely, successful delivery against team OKRs
• Mentor engineers, improving their technical and non-technical skills to maximize their impact

Competencies:

• Stellar engineering leadership by example — regardless of your language of choice, you separate concerns and define well-abstracted interfaces, leading to functioning, performant, well-tested, maintainable code and systems
• Thinking and communicating in first principles — you are able to explain your points of view from foundational concepts rather than by associative thinking
• Critical thinking with influence — you systematically evaluate the tradeoffs associated with each potential solution to a problem, make an informed decision, and articulate these things well to influence others, driving impact

Technologies:

• Here are some of the technologies we use now or may use in the future; you probably care somewhat if you’re an engineer. Familiarity with these things is nice to have, but not a requirement.
• Go, Python, Ruby, Scala, Java
• Django
• GraphQL
• HL7 FHIR, Redox
• gRPC/Protocol Buffers, Thrift, Avro
• Bazel
• OAuth
• MySQL, PostgreSQL
• Kafka
• Redis
• Elasticsearch
• Docker
• Kubernetes
• Terraform
• AWS