Job Description
Job Description
CDS Platform Developer
Role Context
The CDS Platform Developer is a proactive, collaborative engineer responsible for building and maintaining robust, scalable software solutions across the full stack. This role requires navigating complex codebases, diagnosing and resolving issues, and implementing new features within a cloud-native AWS environment. By balancing technical rigor with cooperative problem-solving, the Developer contributes to the stability and evolution of the CDS Platform, ensuring high-quality code and infrastructure through clear communication and shared ownership.
Responsibilities
The CDS Platform Developer is responsible for actively engaging with the existing technology stack to maintain platform health and extend functionality. In this capacity, they apply logical reasoning and collaborative practices to diagnose issues, resolve straightforward problems, and effectively contribute to team goals and product roadmaps with varying levels of autonomy. The developer is expected to:
- Read and comprehend existing codebase patterns, tracing execution paths to understand runtime behavior.
- Apply sound logical reasoning to diagnose straightforward bugs or extend current logic.
- Solve problems effectively in straightforward situations.
- Work cooperatively and independently, balancing autonomy with a moderate level of guidance and direction.
Skills and Competencies
- Proactive problem-solving: Capable of diving into complex, existing codebases and understanding intricate logic.
- Analytical & Debugging: Efficiently diagnose and resolve problems.
- Communication & Collaboration: Demonstrate excellent interpersonal skills; approach technical disagreements with empathy and constructive reasoning, prioritizing team cohesion and collective goals over individual preferences.
- Ownership: Be driven, self-motivated, and results-oriented, with the ability to manage tasks effectively within limited timeframes.
Technical Capabilities
Full-stack developer familiar with the following domains, possessing hands-on experience in several key areas:
- Frontend: Familiar with building UI with JavaScript, HTML, CSS. Can follow existing patterns to be productive in design/CSS or front-end logic. Can implement new pages, components, and behaviors based on existing patterns and framework code. (React, TypeScript, testing libraries such as Jest, React Testing Library, and Playwright)
- Backend: Understands the function and structure of basic web services. Can follow conventions to write code for standard MVC-style services that use a database and serve an API. (Kotlin and/or Java, Spring Boot, testing libraries such as JUnit, Mockito, REST Assured, Docker)
- Infrastructure: Practical experience writing Terraform to manage AWS resources like S3, Lambda, VPC, ALB/NLB. Can modify and extend existing infrastructure code with support. Understands how to structure infrastructure to be reusable and testable. Can write and maintain basic infrastructure tests using tools like Terratest or similar. Familiar with AWS CLI, IAM roles/policies, and troubleshooting common issues in a dev/test environment. (AWS, Terraform, GitHub Actions, Datadog)
- Domain: Knowing FHIR is a plus but not critical.
- Collaboration tools: Slack, Microsoft Suite, Google Suite, GitHub.
- Automated Testing / Testable Solutions: Understands that tests should be present and how code design impacts testing. Can articulate and apply multiple levels of the testing pyramid.
Expectations / Ways of Working
- Willing to adopt the team’s agreed-upon development practices, including pair programming, test-driven development, continuous integration, and continuous delivery, while contributing fresh ideas for improvement.
- Able to provide application support within the Platform team and for other dependent CDSCollaborative teams.
- Available during the team’s core working hours (minimum schedule overlap timeframe):
- EST: 11:00 AM – 5:00 PM
- CST: 10:00 AM – 4:00 PM
- MST: 9:00 AM – 3:00 PM
- PST: 8:30 AM – 2:30 PM
- Available for at least one weekly shift of off-hours on-call support (7:00–11:00 AM or 4:00–8:00 PM ET).
- Contributes to the team and program’s collective goals by working within established guidelines, while also identifying where processes or solutions can be improved.
- Willing to ask clarifying questions, proactively share knowledge, partner effectively with stakeholders, and give/receive feedback.