Disclaimer: We know that the title is a contradiction but it’s exactly what you’ll do
This job ad is exactly the same as the job description for "Technical Account Manager '' and "Senior Technical Support Engineer". Internally, we'll refer to your job as an Account Engineer (m/f/d).
So why have 3 different titles for the same job? Tl;dr: no one outside of Giant Swarm understands what we mean by Account Engineer ;) And each of the existing titles falls short in bringing across what we actually mean by it. You're confused? No problem! So were we initially, but we're more than happy to explain this in detail :) #namingishard
- You ensure that customers have the correct technical resources and knowledge to be successful while using the Giant Swarms product.
- We are on a journey with our customers - You want to learn more? Check here
- While having the best interest of our customers constantly in your mind you shield and by that enable your colleagues within GS to focus on what they do best - building an amazing product!
- A superpower that might help? Being a horse whisperer towards our customers - what does that mean? According to the definition: You need to adopt a sympathetic view of the motives, needs, and desires of the horse. And we couldn’t agree more with that apart from the fact that you deal with our customers instead of horses.
You think that sounds like something you could be interested in but you are not yet 100% convinced? Check what Oli (COO) thinks about the position and why we decided to split Solution Engineering into Account Engineering and Solution Architecture on our Blog.
Here’s what Ben our first Account Engineer would like to tell you:
We find out what the needful is, to find out how the needful can be delivered.
How working with Giant Swarm is like:
Every new team member changes the team. We love to learn from each other and we are looking for people who know things we don’t.
Becoming part of Giant Swarm means that, by extension, you also become part of the Cloud Native community. We actively contribute to upstream projects and our quarterly hackathons will give you space to work on out-of-the-box projects. Occasionally, when we, as a team, want to fully focus on one project, we scratch all meetings and routines for a certain time to better focus during our hive-sprints.
Continuous learning is important to us - we foster this through bi-yearly personal development talks, a budget for training/certifications/coaching as well as regular feedback talks and workshops. Our teams are cross- functional and collaboration is key.
Nothing crazy, but useful Basics: We don't count holidays but set a minimum number; You choose your own hard- and software; As a company that has almost, if not more, kids than employees, family-friendliness is crucial to us and paid parental leave is a no-brainer; We pay monthly perks that cover your costs for working remotely; We meet twice a year as an entire company and (if possible) see conferences as an important place to catch up with team members; We aim to be fully transparent (finance, salaries) unless it hurts people and trust you, based on this to make the best decisions
We failed in exactly describing our way to approach important company elements that can be described with ‘buzzwords’ such as agile mindset, cross-functional teams, self-organization, value of the individual or trust & teamwork. However, we truly care about them, we live them and we constantly iterate on them. Some snippets about how we do this are posted in our blog but by far not all of them.
Important note: We are not hiring job descriptions. We hire humans. :) We welcome applications from everybody, regardless ethnic or national origin, religion, gender identity, sexual orientation or age.