> Markdown version of [/jobs/ext/2585382-controls-software-engineer](https://www.wearedevelopers.com/jobs/ext/2585382-controls-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Controls Software Engineer - **Company:** Lawrence Berkeley National Laboratory - **Location:** Berkeley, CA, United States - **Experience:** Experienced - **Salary:** $104,580.0 - $127,836.0 - **Contract:** Temporary to permanent - **Skills:** C++ (Programming Language), Code Review, Collaborative Software, Computer Engineering, Linux, Graphical User Interface, Monitoring of Systems, Issue Tracking Systems, Python (Programming Language), Shell Script, Software Engineering, Software Project Management, Systems Integration, Data Logging, Delivery Pipeline, Information Technology, Software Version Control - **Published:** August 19, 2026 - **Apply:** https://jobs.localjobnetwork.com/apply/add/88078333/1 ## About the Role * Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, another engineering discipline, the physical sciences, or a related field, and a minimum of two years of related professional experience; or an advanced degree in a related field without required experience; or equivalent work experience. * Developing professional knowledge of software engineering concepts and the ability to apply organizational policies, procedures, and established technical practices to troubleshoot and resolve a variety of moderate-scope issues. * Experience developing software in C/C++ and Python. * Experience using Linux operating systems and shell scripting. * Ability to gather relevant information, interpret logs and test results, evaluate identifiable factors, and determine an appropriate course of action within defined practices. * Knowledge of collaborative software development practices, including version control, issue tracking, code review, documentation, testing, and release or deployment workflows; and the ability to develop and maintain reliable software interfaces and applications. * Effective written and verbal communication skills and the ability to build productive working relationships with engineers, scientists, operators, software developers, and other partners. * Ability to organize assigned work, manage priorities, meet commitments, and work effectively with general instruction on routine assignments and detailed instruction on new projects or assignments. * Ability to learn and apply Laboratory safety requirements and to perform work safely in an operational scientific environment. In addition to the above, Level 2: * Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, another engineering discipline, the physical sciences, or a related field, and a minimum of five years of related professional experience; or a master's degree in a related field and a minimum of three years of related professional experience; or equivalent work experience. * Ability to analyze software and system problems of diverse scope, evaluate identifiable factors, interpret logs and test results, and exercise good judgment in selecting methods and techniques for obtaining solutions. Desired skills/knowledge: * Experience with EPICS or a comparable distributed control system. * Experience supporting scientific experiments, accelerator facilities, beamlines, laboratories, or other research environments. * Experience integrating software with instruments, sensors, data acquisition systems, or control hardware. * Experience contributing to a multi-developer software project and participating in peer review and shared development workflows. ## Description * Develop, modify, test, deploy, and maintain EPICS-based control system software, services, and associated tools for accelerator and beamline operations. * Develop and maintain graphical user interfaces, data acquisition and logging applications, monitoring tools, and related operator-facing software using standard ALS and EPICS tools. * Support the integration of control software with instruments, sensors, control hardware, and operational infrastructure in collaboration with engineers, scientists, operators, and other technical partners. * Participate in software and system commissioning, validation, troubleshooting, and operational support. Analyze moderate-scope issues, review relevant technical factors, select appropriate actions within established practices, and escalate issues when needed. * Create and execute appropriate software tests; participate in peer code reviews; and use established source control, issue management, release, documentation, and testing practices. * Prepare and maintain clear technical documentation describing software designs, interfaces, configurations, test results, operating procedures, and completed work. * Produce initial technical reports or analyses for review by more experienced team members. * Build productive working relationships and collaborate with internal and external partners to resolve shared technical and operational problems. * Communicate status, risks, technical findings, and support needs clearly and promptly. * Complete required Laboratory safety training and consistently apply applicable environment, health, safety, and security requirements in daily work. * Provide occasional scheduled or emergency off-hours support, consistent with Laboratory practices, to help sustain reliable operation of the ALS as a 24/7 user facility. In addition to the above, the Level 2 will: * Design EPICS-based control system software, services, and associated tools for accelerator and beamline operations. * Plan and carry out the integration of control software with instruments, sensors, control hardware, and operational infrastructure in collaboration with engineers, scientists, operators, and other technical partners. * Perform software and system commissioning, validation, troubleshooting, and operational support. Analyze moderate-scope issues, review relevant technical factors, select appropriate actions within established practices, and escalate issues when needed. * Enhance relationships with senior internal and external partners to resolve shared technical and operational problems. Adapt communication to the audience and clearly convey status, risks, recommendations, and findings, using persuasion when needed. ## Related Videos - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [Are Code Reviews Worth It? Insights from 16 Years of Review Data](https://www.wearedevelopers.com/videos/1135-are-code-reviews-worth-it-insights-from-16-years-of-review-data) - [MCP doesn’t suck — your agent does](https://www.wearedevelopers.com/videos/100202-mcp-doesn-t-suck-your-agent-does) - [Strange New Worlds: shaping the future of the digital age](https://www.wearedevelopers.com/videos/677-strange-new-worlds-shaping-the-future-of-the-digital-age) - [Docker exec without Docker](https://www.wearedevelopers.com/videos/1094-docker-exec-without-docker) - [Great DevEx and Regulatory Compliance - Possible?](https://www.wearedevelopers.com/videos/1426-great-devex-and-regulatory-compliance-possible) ## Related Articles - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Software Engineer Career: Things You Should Know](https://www.wearedevelopers.com/magazine/143-software-engineer-career-things-you-should-know) - [Is Software Engineering Hard?](https://www.wearedevelopers.com/magazine/448-is-software-engineering-hard) - [The Ultimate Software Engineer Career Path Guide for 2023](https://www.wearedevelopers.com/magazine/146-the-ultimate-software-engineer-career-path-guide-for-2023) - [What’s the Difference between a Junior, Mid, and Senior Developer?](https://www.wearedevelopers.com/magazine/238-what-s-the-difference-between-a-junior-mid-and-senior-developer)