I believe that people do their best work when it's easy for them to wake up in the morning, they have low stress, they like their colleagues and don't hate the stuff they are working on. What we're really just looking for is a healthy mix of passion and experience in the field. We give our employees a lot of freedom to structure their work day. Felt like people might have been reading your comments in a slightly exaggerated interpretation and it could use some other perspectives. Like, I like doing work within my niche, but it's not my everything or even my core identity.ĭoesn't sound like you're asking potential candidates to profess their undying devotion and pile on gratitude. I say this because I'm fairly niche in my skillset for animation and design, and I only really reach out to studios/ agencies for this very specific skillset, and will turn down jobs (or refer others who might be a better fit) where it's better suited for a generalist or outside of my range. It didn't sound to me like you're asking someone to be a zealot, sycophant, brown-noser, or some kinda corporate drone who drinks the kool-aid and wears the company swag. I'm not in your field, but I read it as such from the get-go and I thought, "Yeah I know what this person is talking about – basically, not seeking someone who lays it on too thick about being in love with the company (or even the specific software/ work), but someone who reads the job description, and is fairly assured they are very capable of doing the work, and wants to do the work because it's interesting to them." It's about transparency of our goals align. On our end, we need to filter out people who really just want to fill a role to make ends meet. It's fine if your focus is your private life and you really just need a paycheck. We offer you the opportunity to work together with a smart bunch of people on a very hard problem. Our long term goal is to build the GitHub for APIs, a collaborative platform to enable true collaboration between API producers and API consumers.Įither you're excited about this as much as we are, or you just send a CV. We're the first to build a Backend for Frontend Framework, unifying the ideas of API Gateway, BFF and package manager. We're looking for people who actually want to do work at WunderGraph. We don't want job applications from people who are looking for a job. I understand where you're coming from, but see it differently. What's the purpose of sending a CV when I have to do all the hard work? Why should I read your CV when you didn't bother skimming through my landing page, docs, or open source repository. If you apply for a job with us and you don't have an opinion whether you like what we do or not, it's really hard to gauge interest. We're doing a lot of innovative stuff in the API segment. I've had too many candidates who never checked out our landing page ( ). Simply out, show interest and explain why you're a good fit. I have previous experience in this field and wrote an open source library to solve some of the issues you might be facing (link). Especially that you're working and X thing really got my attention as I know that Y and Z are super important for the customer segment you're working on.Ģ. I've read through your website and documentation and are truly inspired by your vision. Simply answer the following 2 questions briefly in plain English.ġ. The chances of getting to the interview stage with this approach are almost zero.īecause everyone does this, you can easily stand out. Most candidates really only submit a resume. I keep giving this advice on how to significantly increase your chances of getting to the interview stage.
0 Comments
Leave a Reply. |