Perforce is seeking an Open Source Software Support Engineer to join our OpenLogic team, responsible for providing support and services on Open Source technologies to our OpenLogic customers. This position will work closely with members from Support, Sales and Professional Services to assist in resolving a wide variety of customer issues. This critical position demands a systems engineer with strong networking skills and some programming capabilities. You would be responsible for ensuring the success of our customers by effectively providing dependable and timely resolutions related to open source software. The ideal candidate is expected to be self-motivated, proactive, results-oriented and able to provide a high level of customer satisfaction through the delivery of world-class technical support services.
Responsibilities:
Interact with end users on technical problems;
Tier 1, 2 and 3 support for open source products;
Drive resolution of those problems, which include:
Open source software issues
Questions around open source software usage
Questions around use and best practices
Review of the architecture and design where software is implemented
Conduct professional services and training engagements
Research, understand, and advocate open source software
Interact with various open source communities
Drive early resolution of issues
Be a part of the on-call rotation
Present knowledge via articles, blogs, and conference presentations.
Requirements:
Minimum of 2 years of software development and design or systems administration or level 3-4 technical support experience;
At least 2 years in a senior position ( senior/lead developer, engineer, or DBA);
Minimum 3 years implementation and troubleshooting experience on 3 or more of the following: #ActiveMQ, #CentOS, Apache Tomcat, #PostgreSQL, Apache HTTP Server (#httpd), Java Development Kit (#JDK), #Wildfly Application Server, #Jenkins CI, #ApacheKafka, or #ApacheCassandra;
Preference given to candidates with implementation and troubleshooting experience on one or more of the following: #ApacheCassandra, #ApacheKafka, #ApacheSolr, #Couchbase, #DockerCE, #ElasticSearch, #Kubernetes, #MongoDB, #Redis, #WSO2, #ApacheNifi, #Kubespray, #Minio, #Foreman, #Kiali, #Terragrunt, #OpenLiberty, or #Kong
Strong #RHEL/CentOS background required
#Debian/ #Ubuntu, #SUSE/ #openSUSE/ #SLES, other distro background a bonus
#C, shell scripting, #Python, etc;
#Linux distro package building a plus (#rpm, #deb, #ipkg, etc);
Virtual Machine experience with #qemu/ #kvm, #Azure, #AWS, #VirtualBox, #Vagrant;
database administration (not just db "power user") experience very desirable; #postgresql/ #mysql/ #mariadb experience preferred;
Experience working in production environments, especially enterprise/carrier environments;
General experience a plus such as: radius/Kerberos, ldap, ipa/idm, monitoring, vpn, containers, centralized systems management, automation (#ansible, #chef, #puppet, etc), version control (#git, etc), security hardening (CIS, STIGS, PCI-DSS, etc);
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software;
Excellent written, verbal, and presentation skills;
Knowledge of open source packages;
Experience speaking at conferences/comfortable speaking in front of large crowds;
Fast and creative thinker, quick on their feet to respond quickly to complex and difficult problems Proven track record of acquiring strong proficiency in new technologies quickly.
Interact with end users on technical problems.
Tier 1, 2 and 3 support for #CentOS and related open source products.
Drive resolution of those problems, which include:
Open source software issues.
Questions around open source software usage.
Questions around use and best practices.
Review of the architecture and design where software is implemented.
Conduct professional services and training engagements.
Research, understand, and advocate open source software.
Interact with various open source communities.
Drive early resolution of issues.
Make strategic contributions to the CentOS core and surrounding ecosystem, provide bug fixes ahead of the community where needed
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
Requirements:
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Strong knowledge of the Linux #kernel and system architecture.
Understanding of software best practices; #SDLC, #SCM and #Agile development principles.
Ability to develop with #C / #C++ in a UNIX environment.
Utilization of common #Linux C/C++ build tools such as #gcc.
Solid understanding of CentOS 6.x and 7.x and included frameworks like #firewalld, #systemd, etc.
Strong #RHEL/CentOS background required
#Debian / #Ubuntu, #SUSE / #openSUSE / #SLES, other distro background a bonus
C, shell scripting, #perl, etc
Virtual Machine experience with #qemu / #kvm, #Azure, #AWS, #VirtualBox, #Vagrant
General experience such as: radius/Kerberos, lda, ipa/idm, monitoring, vpn, containers, centralized systems management, automation (ansible, chef, puppet, etc), version control (git, etc) or security hardening (CIS, STIGS, PCI-DSS, etc)
Excellent written, verbal, and presentation skills
Knowledge of open source packages
Database administration; #postgresql / #mysql / #mariadb experience very desirable
Experience with Linux distro package building (#rpm, #deb, #ipkg, etc) preferred
Existing contributions to the CentOS community a major plus
@musicman Does #virtualbox give your machine an IP address on the LAN, or does it NAT through your machine? If you're going to remotely access services in the VM, you'll likely need a LAN address.
RT @MartinezPeck@twitter.com OS virtualization (#VMWare, #VirtualBox, etc) started to use the concept of "image" and people got it. Linux containers, #Docker, etc continue that pattern and people still get it. Why is then so difficult for devs to understand what a #Smalltalk image is?
What's the best way to get an #Ubuntu and #Mint virtual machine running with "default" settings? I want to review what a default graphical installation looks like.
I'm currently trying with #VirtualBox and #Vagrant. Maybe there's a ready-made image or vagrantfile out there for me?
I now have #TiddlyWiki#NodeJS setup within a #Lubuntu VM in #VirtualBox. All that's left is to assemble some basic guides and backup/live upload scripts so that general-ish users can just start using the powerful personal #wiki (and/or website editor), in lieu of going the more technical route of installing it and setting it all up on their own.
Use #Linux as the main host OS (or the maturing #Qubes OS which is a hybrid of Xen+Linux) and then run Wine-incompatible software with #virtualization like #Virtualbox . Then you can disable its network/web access and do not need to worry about that bit, which essentially is not part of the software's scope.
Other SW that DO need web access: run those in separate Virtualboxes.