Scientific Programmer IV jobs in United States
cer-icon
Apply on Employer Site
company-logo

ECS · 14 hours ago

Scientific Programmer IV

ECS is a leading mid-sized provider of technology services to the United States Federal Government. They are seeking a highly experienced Scientific Programmer to work remotely, who can communicate effectively with science teams and leadership while taking ownership of tasks through closure.

Artificial Intelligence (AI)Cloud InfrastructureComplianceConsultingCyber SecurityInformation TechnologyMachine LearningSecuritySoftware
badNo H1BnoteU.S. Citizen Onlynote

Responsibilities

Strong communication skills: Ability to communicate clearly, respectfully, and calmly—both verbally and in writing—with a wide range of stakeholders (e.g., PhDs, scientists, developers, managers, and business stakeholders)
Documentation mindset: Demonstrated willingness to document actions, decisions, assumptions, and open questions in tools such as JIRA, Confluence, and similar platforms. Able to be clear, concise, and explicit about uncertainties
Critical thinking and constructive challenge: Confidence to ask questions, incorporate feedback, and respectfully push back on ideas that appear incorrect, with a focus on reaching the best possible solution
Software and cloud development knowledge: Working knowledge of software development and cloud concepts. Deep expertise is not required, but the candidate must be willing to learn from guidance, self-teach as gaps are identified, and continuously improve
Experience with non-serverless architectures: Familiarity with non-serverless infrastructure such as EC2, containerized workloads, and related compute models
Infrastructure as Code (IaC) exposure: Some hands-on experience with Infrastructure as Code tools (e.g., Terraform, AWS CDK, Azure Bicep, or equivalents), even if limited
Architecture comprehension and feedback: Ability to review AWS architecture diagrams, ask clarifying questions, mentally model the system, and provide constructive, co-architectural feedback to ensure solutions are fit for purpose
Diagramming and visual communication: Experience creating architecture diagrams (AWS-focused preferred) to clearly communicate ideas and designs beyond written explanations
Strong sense of ownership (absolute requirement): Takes responsibility for their work end-to-end. Proactively monitors and fixes issues without being asked, seeks improvement independently, and treats failures as learning opportunities. Ownership is defined by accountability and growth—not perfection

Qualification

PythonCloud development knowledgeInfrastructure as CodeCI/CD pipelinesDocker containersKubernetesAWSMicrosoft AzureGoogle Cloud PlatformsAgile/Scrum experienceGitLab runnersConfiguration management toolsAnalytical skillsFederal government experienceAtlassian SuiteCommunication skills

Required

BS/BA in Computer Science, a Technical Field, or other related disciplines
Excellent communication and ability to communicate clearly, respectfully, and calmly—both verbally and in writing—with a wide range of stakeholders (e.g., PhDs, scientists, developers, managers, and business stakeholders)
Demonstrated experience migrating scientific applications from on-premise systems to a Cloud environment
Demonstrated experience programming in Python and experience with Docker containers and Kubernetes using CI/CD pipelines
Demonstrated experience working in an agile/scrum team
Experience building and leveraging GitLab runners
Experience with code-defined Infrastructure, configuration management tools, and CI/CD
Experience working with Cloud Service Providers, including AWS, Microsoft Azure, and Google Cloud Platforms
Experience and understanding of large-scale infrastructure deployments in enterprise-wide environments leveraging DevOPS principles and utilizing a CI/CD pipeline
Excellent written, verbal, and analytical skills
Ability to obtain a Public Trust Clearance
Strong communication skills: Ability to communicate clearly, respectfully, and calmly—both verbally and in writing—with a wide range of stakeholders (e.g., PhDs, scientists, developers, managers, and business stakeholders)
Documentation mindset: Demonstrated willingness to document actions, decisions, assumptions, and open questions in tools such as JIRA, Confluence, and similar platforms. Able to be clear, concise, and explicit about uncertainties
Critical thinking and constructive challenge: Confidence to ask questions, incorporate feedback, and respectfully push back on ideas that appear incorrect, with a focus on reaching the best possible solution
Software and cloud development knowledge: Working knowledge of software development and cloud concepts. Deep expertise is not required, but the candidate must be willing to learn from guidance, self-teach as gaps are identified, and continuously improve
Experience with non-serverless architectures: Familiarity with non-serverless infrastructure such as EC2, containerized workloads, and related compute models
Infrastructure as Code (IaC) exposure: Some hands-on experience with Infrastructure as Code tools (e.g., Terraform, AWS CDK, Azure Bicep, or equivalents), even if limited
Architecture comprehension and feedback: Ability to review AWS architecture diagrams, ask clarifying questions, mentally model the system, and provide constructive, co-architectural feedback to ensure solutions are fit for purpose
Diagramming and visual communication: Experience creating architecture diagrams (AWS-focused preferred) to clearly communicate ideas and designs beyond written explanations
Strong sense of ownership (absolute requirement): Takes responsibility for their work end-to-end. Proactively monitors and fixes issues without being asked, seeks improvement independently, and treats failures as learning opportunities. Ownership is defined by accountability and growth—not perfection

Preferred

Federal government experience
2+ years' experience with Atlassian Suite (Jira, Confluence, Bitbucket)

Company

ECS is a fast-growing 4,000-person, $1.2B provider of advanced technology solutions for federal civilian, defense, intelligence, and commercial customers.

Funding

Current Stage
Late Stage
Total Funding
unknown
2018-01-31Acquired
2015-04-10Private Equity

Leadership Team

leader-logo
Keith McCloskey
VP / Chief Technology Officer
linkedin
leader-logo
Ryan Garner
Chief Financial Officer
linkedin
Company data provided by crunchbase