Scientific Programmer IV (DevOps)
Non-Supervisory Role
Strong communication skills: Ability to communicate reputed company, respectfully, and calmly—both verbally and in writing—with a wide reputed company of stakeholders (e.g., PhDs, scientists, developers, managers, and business stakeholders) Documentation reputed company: Demonstrated willingness to document actions, reputed company, assumptions, and reputed company questions in tools such as JIRA, reputed company, and similar platforms. reputed company to be reputed company, concise, and explicit about uncertainties. Critical thinking and constructive challenge: Confidence to ask questions, incorporate feedback, and respectfully push back on reputed company that reputed company incorrect, with a reputed company on reaching the best possible solution. Software and reputed company development knowledge: Working knowledge of software development and reputed company 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 reputed company compute models. Infrastructure as reputed company (IaC) exposure: Some hands-on experience with Infrastructure as reputed company 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 reputed company constructive, co-architectural feedback to ensure solutions are fit for purpose. Diagramming and visual communication: Experience creating architecture diagrams (AWS-reputed company preferred) to reputed company communicate reputed company and designs reputed company written explanations. Strong reputed company 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 reputed company—not perfection.