The 28-Day Employee: How My First Hire Became My First Fire, and What I Learned

If you've ever stepped into the world of hiring, you know it's filled with choices, challenges, and often, unexpected lessons.

One of my most memorable experiences was hiring our first developer, a journey that ended after just 28 days despite the fact that he was a genuinely great guy.

In this article, I'll walk you through the seven key missteps I made during this process. You'll get an inside look at everything from the struggles of defining the right role to the complexities of salary negotiations.

My hope is that by sharing these experiences, I can help you navigate your own hiring journey with a little more confidence and a lot less trial and error. And just to note, we're still on the lookout for great people. We're hiring! ;-)

My saga began with a desperate need for a developer. As a non-technical co-founder of a fledgling startup, you're like a kid in a candy store when it comes to hiring technical staff. The only problem? You've never tasted candy before.

"Any" seems like a good choice, and so, in my excitement, I overlooked a crucial detail - I needed a culinary expert, with experience and I made my first mistake.

Mistake #1

Failing to accurately pinpoint what I really needed, a senior developer as opposed to a junior one. We were looking for a good opportunity, young or senior. If you don't what you want, you might likely not be pleased by what you get.

And the worst part was that I didn't push hard enough on my CTO, who was our gatekeeper to the tech world. I let the technical tests slide as easily as a buttered bagel. They were simply too easy, which led me to my second mistake.

Mistake #2

During the early days of our hiring journey, we were so eager to fill our vacant developer role that we allowed the complexity and thoroughness of our technical evaluation process to slide.

No matter the role you're hiring for, assessing a candidate's aptitude with real-world tests is crucial. Resumes and references are only part of the story; the rest must come from tangible evidence of a candidate's skills and compatibility with your business requirements and coding philosophy.

Learning from our missteps, we now employ a comprehensive technical evaluation that involves sending a long piece of code from a GitHub repository to our candidates. We ask them to go through the code and provide detailed comments. They have to spot security flaws, identify what's missing, suggest improvements, and more. This rigorous approach doesn't just test their technical prowess; it also gives us insight into their problem-solving skills, attention to detail, and approach to secure coding practices.

This process paints a much clearer picture of the candidate's capabilities and their fit with our existing team.

Don't underestimate the value of a thorough technical evaluation. It may seem like a lot of effort, but trust me, it pays dividends in ensuring you're bringing on board someone who's not just technically sound, but also aligned with your company's coding philosophy and standards.

Mistake #3

unveiled itself during that limbo period after we'd signed the contract but before his official first day. We had an onboarding dev book, a pretty handy guide that my CTO gave him when we signed the contract, but he passed it over. It wasn't his favorite pastime, and I suprisingly understood. "It's okay, some people prefer Youtube or Netflix over a paperback.

His reluctance to indulge in reading should have raised an eyebrow or two, but I rationalized it away. After all, we were still in that 'pre-honeymoon' period, and he was a youngster. Maybe youngsters don't like to read much nowadays, right? Turns out, this was more of a red flag than a generational gap.

In addition, he never quite got around to installing WP Umbrella anywhere. Again, I overlooked this. He wasn't technically our employee yet. But now when I look back, these were early signs that we weren't on the same page before it even started and thus it should have started at all.

Mistake #4

Initially, my first hire aspired to a freelancer's lifestyle. This wasn't a lack of commitment or drive, but rather a different perspective on work-life balance and professional autonomy.

However, I, believing in the stability and structure a permanent contract could offer, persuaded him to embark on this new journey. This wasn't a sly business move; it was rooted in my earnest desire to build a dedicated team, convinced that this approach was best for everyone involved.

In retrospect, it's clear this decision didn't fully honor his professional aspirations. As I learned, it's vital to ensure each team member's professional journey resonates with their personal goals for a harmonious work environment.

Mistake #5

In an attempt to build bridges and start our work relationship on a positive note, I agreed to my hire's salary terms without negotiation. This wasn't about being a pushover, but about a genuine desire to avoid creating an atmosphere of discontent or frustration from the get-go. After all, nobody likes a gruelling salary negotiation, for 2k/year right?

However, this well-intentioned decision unintentionally stirred a different pot of frustration – one that belonged to me and my associate. It was akin to a well-meaning chef adding a bit too much spice in the soup. The intent was to enhance the flavor, but the result was a dish too hot to handle.

Reflecting on Mistake #5, it's not about the money per se, but about the importance of balance and open communication in every aspect of a working relationship, including financial matters. Salary negotiation isn't just about the numbers; it's about understanding and respecting the value each party brings and finding a mutual agreement that feels fair to all involved.

The lesson here isn't to become a hardline negotiator, but to cultivate a dialogue where everyone feels heard, valued, and comfortable with the outcomes.

Mistake #6

In my quest to fill our vacant developer role, I chanced upon a candidate who seemed promising. I was delighted and relieved to find someone who appeared to fit our needs so well. So, without much ado, I decided to bring him on board, skipping the usual protocol of interviewing multiple candidates.

This wasn't about cutting corners, but a genuine belief in the potential I saw in him. Sometimes, when you find something that looks just right, it's tempting to grab it and not look further. It's like finding the perfect pair of shoes in the first shop you enter - who wants to spend the whole day shoe shopping, right?

However, reflecting on Mistake #6, I realized that patience is not just a virtue but a necessity in hiring. The hiring process is a bit like gold panning; you need to sift through the sand to find the nuggets. You might occasionally find gold in the first pan, but it's not a given.

That's not to say the person we hired didn't have value; quite the contrary. The lesson here is about the importance of a thorough hiring process - one that includes interviewing enough candidates to ensure a good fit for the role, the team, and the company culture. After all, even the most beautiful pair of shoes isn't much use if it doesn't fit well.

Mistake #7

Navigating the early stages of a bootstrapped company can be likened to embarking on an expedition in uncharted territories. There's a sense of adventure, but also the inherent uncertainties of the unknown. This mindset created a bias where I felt inclined to consider anyone showing interest in our mission. This wasn't indicative of a lack of vision, but rather it showcased the enthusiasm of an early-stage entrepreneur eager to build a robust team

However, upon reflection, I realized Mistake #7 was a profound learning curve about the significance of selective recruitment and self-belief. While it's true we were at the start of our journey, it didn't make our venture less compelling or our vision less valid.

The key here is not merely about hiring anyone who's interested, but engaging those who truly resonate with your mission and who can contribute to your shared vision. The uniqueness of a startup lies in its potential for innovation, its flexibility, and the passion of its team.

This paradigm shift from 'why would they join us' to 'why wouldn't they' was an insightful realization that has profoundly enriched our hiring process, and our belief in what we're building.