Words cannot express the pure joy felt when the fruits of your labor blossom, and you drink from the sweet nectar of success. That is precisely how I would describe my state of mind when job offers came rolling in. Little old me, who has overcome so much — poverty, homelessness, public assistance, single-motherhood — has finally grabbed life by the horns and made her own way.
With that being said, what I thought was a dream come true turned out to be just short of a nightmare, and it didn’t take long to realize, my road to success had only just begun.
Let me start by saying that the company I worked for seems nice, I wouldn’t know as I was only permitted on the payroll for one month. During that month I made more money than perhaps I would have made in a quarter employed as a call center/customer service/sales rep; my previous ‘profession’.
If you’ve never worked in a call center, they have a way of training the psyche of employees to fear authority, grovel at the feet of those who sign off time sheets, and leave said employee feeling slightly less human at the end of the day.
Here I am with my shiny new dev skills, and a new since of purpose and accomplishment juggling job offers, when a year before, I was a brow beaten sales lady.
The thing is that, even though I had the skills, acing technical interviews, and in possession of a wonderful power to make websites do my bidding, I didn’t believe it for myself. This is what I — and many others I believe — call impostor syndrome. And I’ve got it bad.
Truthfully, my lead likely could not code his way out of a brown paper bag. For my first project, I was instructed to use some some ancient jQuery plug-in with four year old documentation, when I knew in my heart that youmightnotneedjquery.
He was also, in a way, afraid of me. I could not quite pinpoint it, but something in the way he would avoid eye contact and send me a message on Slack, rather than just pop over to my desk. We sat right next to each other.
My very good friend, Simone, and co-organizer for blackGirlsCode(2) has an eerily similar story. Her first job was just as nightmarish and she was let go with excuses like you aren’t catching on to things quite quick enough. I too was told the same, but when you have two days to build a site from scratch (whatever that means) don’t get mad if your minimal viable product is super minimal.
My frustrations began to bleed through and I could see the team slowly distancing themselves from me. Not inviting me to lunch. Having meetings without me. Questions directed towards anyone to gain clarity (I am, after all, new) were met with blank stares and thinly veiled confusion, or told, why are you trying to change it? (uh, ’cause its spaghetti code).
I didn’t become a developer to be told what to do.
Now, again, I am less than year into coding, I’ve barely scratched the surface of all the nuances involved with doing this professionally. And there in-lies it’s greatness. It took me a total of six weeks to learn everything there is to know about being a recruiter. How to talk to people, how to negotiate salary, federal laws that govern employment.
Coding, however, is only for life-learners. The folks that dedicate their lives to the very thing that sustains them (i.e. pays them).
For context, Charlotte is a banking town. In fact, it is the second largest financial center in the US. Because of this, you can’t walk two feet at a tech meetup without walking into a developer who’s sold their soul to Wells Fargo or Bank of America. You corner one of the old-timers on the verge of retirement at a bar and they’ll tell you how many days left until he cashes out. While chatting with one, 278 days from retirement, he confessed his refusal to learn anything new. And that, it seems the sentiment of other folks I’ve met along the way who just don’t give a damn about knowing anything other than Java or C#.
(I don’t mean any disrespect, Kiley, I love you!)
I try to be as language agnostic as possible, and choose the best tools for the job. That being said, I will not blindly go with the status quo, wear the uniform (stupid tee and wrinkled jeans) or conform to any one person’s idea of what a developer should look/talk/walk/eat like.
But, back to my original point of my employer. The very minute I began to question whether or not I belonged there was the minute things went sour.
My thoughts were should I have these opinions? will they know I’m not worth the salary I negotiated? will I be fired? Oh no, I’m late, again, I’ll be fired.
Believe it or not, people can feel your fear. They can see right through to the very thing you try to hide. This experience allowed me to reevaluate who I am, my strengths, weaknesses. The most difficult part was explaining to loved ones that my dreams had been cut short. I spent nearly 4,000 hours coding, conducting my own workshops, organizing meetups for Freecodecamp Charlotte. I was back the drawing-board.
While the worst had already happened — been fired and disgraced — it was even harder to muster the courage to try again. But, it would have been even more disgraceful to tuck my tail in fear and give up my pursuits. It took nearly four additional months to find another (much better) job. During that time, I revised my resume, and completed projects using technologies that even the most seasoned developer may have never even heard of.
I leveraged my minimal experience, coupled with previous business exposure to get a gig on my own terms.
So, dear code newbie, (truly) know your worth, and never question your greatness for one, single, solitary moment. be confident in your opinions, and know you have so much to offer. Looking for a job is like dating — you gotta kiss a lot of frogs to catch your Prince Charming; and like finding a mate, there are plenty of fish in the sea. Luckily, for a software engineers, there are approximately 223,000 fish that desperately need you, too.