My First Software Developer Job
I've been learning my whole life that every day is a chance to improve me skills and up my potential. The unique part of a developer's job is that you MUST approach each day this way if you really seek to innovate and improve the lives of others.
This is a long overdue post, but I've been settling into my role as an iOS Developer at McKesson Corporation since March of this year. The job search was a tedious and stressful venture, but I would go through it all over again the same way for this exact outcome. College taught me that LinkedIn, cold outreach, and networking events were the way to secure a job.
I realized much too late that I should've abandoned the traditional business-world practices when I abandoned my business degree at BYU last year. Hundreds of applications and LinkedIn connections but nothing to show for them after months of persistent job hunting. On a whim, I tried to expand my Twitter network by looking for other iOS developers, no matter the stage in life or career their platform stood on. All of the sudden, wonderful content was at my fingertips that nurtured my limited knowledge of software development. Tech was starting to feel less foreign.
A developer I follow posted a job opportunity to bring on several engineers onto the McKesson mobile technology platform and I immediately DMed and applied, despite knowing close to nothing about McKesson, health care, or even a few of the specified background requirements to the job.
I received a phone call within a few days, a simple phone screen that gave me a chance to detail a few of the projects listed in my resume that I had completed as part of the Lambda School curriculum. I was asked to expand upon some basic iOS development principles, and felt confident that my answers would warrant another interview. The call ended after a short 20 minute discussion, and I went about the next week or so as usual.
Another company I had done a phone screen with asked about any current negotiation stages I might be in while discussing the possible next interview steps to proceed with them. I remembered my McKesson phone call, and realized I had done no sort of follow-up work after my phone screen with them. I DMed the developer that interviewed me again, and a random number called me a few hours later with an impressive offer that left me shaking in tears and excitement. I accepted on the call (you should always ponder your offers before accepting them, but the offer had everything I had wanted and more).
The past few months have been a joyful whirlwind. I have a wonderful team that is always happy to coach me through misunderstandings and assist whenever my limited skillset needs a little boost. Working remotely has been a peaceful transition in helping me adjust as a Lambda student to a full-time software developer. While every day challenges me to learn more and do better, I gain more and more confidence that solutions will present themselves as long as I am putting in my best effort and using my resources appropriately. Sometimes I still sit in awe, thinking about how I was so sure that I would never get that job offer, yet here I am today, writing this from my "office" where I develop software for a Fortune 10 company.
If there is anything I would say to my past self, or anyone doubting whether they'll break the ceiling and get that first developer job, it would be to anticipate good things to learn every day and new skills to develop along the way. Approach a new day, ready to challenge yourself and be better than you were yesterday. That concept is the more core and fundamental part of being a software developer. Be hungry to learn and eager to improve, and someday, someone who gets your DM or job application or email will see that shine through and pull the trigger on you.