You Go First
We face many choices in life, and one of the most important decisions we make as software development professionals is about the companies we choose to work for. Joining a company which fits well with your personality, lifestyle and values will bring a sense of purpose and fulfillment. On the contrary, if you’ve picked the wrong company, you might be setting yourself up on the bumpy ride of futile expectations and setbacks. What can we do to make sure that we are about to commit our time and effort to an organization which indeed is a good fit for us, in many respects? Or, given that we do our homework by the book, in our job search, might we be missing some subtle clues which can make or break the relationship between us and the prospective employer?
First, let’s look into what is usually meant by doing a job search “by the book”. We look at a job description, and we see a criteria by which a potential employer outlines what they expect from the candidates, and what a candidate can expect from them in return. Basically, such job descriptions provide an idea of the work skills required as well as the info on financial compensation, benefits & perks, and other details, e.g. hours flexible (or not), remote work possible (or not). The potential employers will also mention what their company is like in terms of culture and organizational framework, e.g. are they a start-up or an established company. Then, they would describe the opportunities for career growth at their organization (if any).
And, here’s the catch. When we are focused on what the potential employer says about themselves, or about us, as the candidates, we find ourselves in the “employer goes first” position. The employer hasn’t yet met us in person, they know nothing about us. Yet, we know about their expectations from the job description, and our mind is mainly centered on answering this question: “Am I the right fit for this organization?” It might seem a tiny irrelevant detail, but, in the end, what will matter for us would not be the answer to “am I the right fit for them?” question. We have to reframe our thinking, and put it along the lines of “are they the right fit for me?”, because that’s what matters. And, the job description, or the description of their organization, as given by the employer, does not usually provide an in-depth answer to this question, because this information comes from their standpoint.
So, if we are to step into our power and reverse the tables, putting ourselves first, how are we supposed to check if what they’re saying about themselves would or would not be O.K. with us? First, it might be a good idea to define where exactly you stand, and what you are looking for from the potential employer. You go first, not the employer. And, there’s a simple technique which might help. I call it “reading behind the lines”. For example, if your potential employer comes across as “an established company”, what does it mean in their world, and what does it mean in your world? Let me give an example. Facebook does pose as an established company, sure, and they used to be a dream employer. For some, they still are. However, would you be willing to join “an established company” which now finds itself at this point in their organizational journey:
“It’s the bunker mentality. These people have been under siege for 600 days now. They’re getting tired, getting cranky — the only survival strategy is to quit or fully buy in.” — source
Or, if your employer paints themselves as a vibrant start-up in the job description, while what’s going on in truth for them is this:
“Startups focus on speed since they are burning cash every day as they search for product/market fit. But over time code/hardware written/built to validate hypotheses and find early customers can become unwieldy, difficult to maintain and incapable of scaling. These shortcuts add up and become what is called technical debt. And the size of the problem increases with the success of the company.” — source
… would you be enthusiastic about joining them, or rather not?
Another example. If the job would involve a relocation, wouldn’t you think not only twice but many times, before committing to a job location where you would either have to pay a high-sky rent, or to spend several hours per day commuting? Not to mention the resentment of non-tech folks towards those who work in tech, which may even lead to outright hostility.
As a general principle, the approach that you will want to take would involve scrutinizing any and all information that the employer has made available about themselves. Check if they are sugarcoating some major organizational fault which might be a deal-breaker for you. There are communities online where people give feedback about their employers, e.g. Glassdoor. Or, even better, if you know someone who works at a company which you consider joining, see what you can find out from them. Just do your homework diligently, sit down with yourself and decide what is acceptable for you, and what is not. Most importantly, ask the questions that give the answers which are meaningful for you, rather than relying on what someone has said about themselves. There are a myriad scenarios by which employers and employees might fit together or not, and it would take many many articles to cover even a fraction of those. I’ve only provided some hints which would help you switch to the “me first” mentality and go from there.
Related articles:
Integrity: The Costs of Bitterness
To Glass Cliff Walkers With Love
