June came and went, but our pride will be forever!
Throughout the past month, we celebrated diversity and inclusion with themed lunches and activities. We love getting together as a team to do fun projects and go to outings, because it’s important to work hard and play hard! First, we did a tie-dye activity. It was a gorgeous day outside, so we set up a tarp, grabbed all the rubber bands we could find, and colored away. Then we showed off our wearable artwork at the Bogota Golf Center for a round of mini-golf!
In the process, we raised money in support of the Human Rights Campaign, a foundation dedicated to the advocacy of LGBTQ equality. Additional funds were donated for every hole-in-one, so we tried our best to be the next Tiger Woods of mini-golf! Thank you to all who participated and helped spread the love.
As Sulzer US continues to grow, we have been lucky enough to find some of our employees through various bootcamps! In “Bootcamp Breakdown,” we’ll give you insight from our experienced team members on how they prepared for coding bootcamp and what they learned from their journeys.
A little about Evan…
Evan found the Columbia Full- Stack Web Development bootcamp through an online ad. The bootcamp sent him some basic paperwork in the mail and after completing it, he was ready for the six-month, part-time journey. Evan found coding in a group to be very different from other types of group projects. He found constant communication was a must. It was also important to be extremely careful when editing someone else’s code. Besides covering dozens of other different technologies, Evan is pleased to have learned a lot about how to use Google’s search engine to its maximum benefit.
By the end of the bootcamp, Evan created his favorite project–a pronunciation quiz for his ESL (English as a Second Language) students. The quiz played audio of two similar English words and the student had to choose what word was being said. Evan used jQuery and Bootstrap. Even though these technologies aren’t as advanced as others, Evan was able to complete the project early in the bootcamp. That’s impressive!
What is his advice for future bootcamp students?
“Take every assignment one step further. The homework assignments are practically spoon-fed to you if you pay attention to the classwork. The best way to learn more is to push the limits and try to do something that’s way out of your depth.”
Meet Christian Egglin, Software Developer. Christian started with Sulzer US as an intern and recently flipped to a full-time position! His favorite aspect of the role is seeing front-end development finally come together since it requires a lot of problem solving and hard work. Christian’s biggest accomplishments at Sulzer US so far have been building out the BMW Online Driver’s Guide and Daimler Digital Claim Management projects. His goal is to eventually become a project lead. When he’s not handling all things development, Christian enjoys playing soccer, basketball, and tennis.
Coding bootcamps are high-impact training courses for coders looking to enter the tech industry job market. They are popular among students who want to learn the skills that employers in the real world are looking for, and therefore also popular among job recruiters. Often referred to as the “fast track” to well-paying tech jobs, bootcamps offer lower tuition costs, shorter class times, and a practical learning curriculum.
As Sulzer US continues to grow, we have been lucky enough to find some of our employees through various bootcamps! With the introduction of our new blog series, “Bootcamp Breakdown,” we’ll give you insight from our experienced team members on how they prepared for coding bootcamp and what they learned from their journeys.
A little about Garrett…
Despite the 5 days per week, 8 hours per day of learning, coding, and practicing at a frantic pace, Garrett successfully created a final project─ an app for comedians. The app would record all their notes and jokes and then craft “routines” using the recordings. The project including a culmination of things he learned over the course of the program.
What is his advice for future bootcamp students?
“Forget everything you know and all the old ways you know of doing things. I had to work hard on, sort of, re-writing my brain chemistry to start thinking like a developer, instead of like a journalist who codes. Have an open mind and don’t be scared by the challenges – embrace them and use them to make yourself better.”
Quick overview of role:
I have a hybrid role: Application Support for our clients as well as performing System Admin and support tasks for our Internal Sulzer US users.
8:00am – We have a rotating shift so depending on the week I can start my day at 8am or at 10 am. First thing I check is e-mails and ticket queue.
9:00am – Check the database for one of our projects with BMW. We check to see if any of the data needs to be manually updated. If the data needs to be updated, I proceed with adding the values to the database.
10:00am-11:00am – Around this time most of the users are in the office and issues arise. It can be Networking issues for example, reaching a host though our VPN to a client’s network. Some other issue can be that something isn’t working with their laptop or account password.
1:00pm – After lunch I check the ticket Queue and E-mails for any notifications for arising issues. Proceed with troubleshooting.
2:00pm – Besides working on troubleshooting tickets, we perform reporting for some of our applications.This consists of a monthly meeting that we analyze our tickets and create a presentation. If there aren’t any tickets/internal issues and/or client reporting, I work on professional development to help increase my knowledge. Currently I am expanding my knowledge of Python.
3:00pm – Review database data check for one of the applications that we support. We get the result in a form of an e-mail that is delivered internally to the team members that support the application.
5:00pm – Work is completed for the day. If I am on the later shift which starts at 10:00am I would stay until 7:00pm.
Favorite part about role: My favorite part of the role is the diversity of tasks, from troubleshooting client issues to internal support tasks. Prior to Sulzer US, I didn’t have much experience with Linux operating system and now I enjoy Linux a lot. I also enjoy the time we get for professional development, learning anything new is exciting.
Words of advice for someone starting their career: Always think about the knowledge you’re gaining. If your first role isn’t exactly what you were looking for – it is experience. Also finding the perfect work environment helps keep you excited about your tasks at work and not stressed.
Quick Overview of Role: I take care of all AWS issues, including creation and set-up of servers, user permissions, network security, and automation of our environment.
7:00am: Waking up looking at my clock, hoping I still have an hour to sleep!
8:00am: Arriving around 8:30 and having breakfast so I don’t get hangry in the morning.
9:00am: Start my day looking through documentations and testing some of my fixes that I worked on the night before.
10:00am: Possibly having a meeting or creating more documentation for future projects so we are prepared for what’s to come.
11:00am: Working on diagrams to estimate our company cost of the architecture we are using and looking for ways to improve and where we can save money.
12:00pm: Going to lunch and losing to Frank in foosball. (Our current record is Frank-28 / Me-0.)
1:00pm: Testing new templates I made for automation and finishing any of my short-term tasks that I have on my agenda.
2:00pm: Looking at educational videos of AWS services and what we can do to implement these in our environment.
3:00pm: Either helping other teams with any resources that they need in AWS or working with Ben on implementing changes that will improve our security in the AWS network.
4:00pm Doing maintenance on any servers that are scheduled to be reset and tested.
5:00pm: Working on troubleshooting documentation so we have all issues that we ran into during the day documented and fixed. We can use these if the same issues turn up again in the future.
6:00pm: Wrapping up my work around 6:30pm and losing to Frank in foosball, again, before I leave the office.
7:00pm: Getting home and thinking what there is to work on for the next day and implementing some test environments at home to try any new ideas to apply in the morning.
There is an endless amount of knowledge that you can take in. AWS has so many different services and is always changing, so you can’t ever get bored or worried about doing the same things over and over. I also put work in outside of the office to learn more, which is a good challenge.
Don’t come into this career thinking you know everything. Be humble enough to know that you still have a lot to learn from others and be ready to document everything you do to make life easier.
Do your research on the company, even before applying. Keep in mind: “Are their values something I believe in?
Is their culture something I want to be a part of?” Have a general sense of what the company does and if
the company will be a good fit for you, as well as if you will be good fit for the company.
Know your resume inside out and make sure it is up to date. You should be able to walk anyone through your resume
and thoroughly explain your experience without hesitations. You’ll come across as more knowledgeable and confident!
Ask questions in the interview. This shows the recruiters that you did your homework! When asking technical questions for jobs in the technology industry,
interviewers will be signaled that you understand the requirements of the position. When asking non-technical questions, this shows them that
you came prepared and are truly interested in the position.
Be ready for anything. Once you are in the interview, you should be prepared to solve
various problems. For the tech industry specifically, you may be asked to answer using various methods,
such as on a computer or on a whiteboard.
Give yourself time during your entire interview process. When you are scheduling interviews with multiple companies,
try not to overload yourself. It may be easy to schedule multiple interviews in one day, however, it can get overwhelming.
Know your limit so that you can stay efficient and succeed in each of interview!
Send a “thank you” note after your interview. It can be in the form of an e-mail or a quick LinkedIn message, or even a brief phone call.
Interviewers love that you take the time to contemplate the interview and genuinely thank them for their time. This is also a great avenue to ask
any last minute questions you didn’t get the chance to ask in the interview.
Enjoy the experience! While interviews can be nerve-racking, there is always something to learn from them!
Honorable founders, engineers, and innovative women have taken the tech world by storm! Here are a few women who made history in the tech industry and continue to be an inspiration to women all over the world.