Immediate apologies for the title; I'm incurably practical.
YOU DID IT.
You finally got it done. You completed every course, turned in your last paper, completed your final assessment, pushed your last commit for school onto GitHub.
Now you need to get paid for it.
Bless his dorky heart.
In looking for a job, I realized a few things and thought I'd share them here, in case anyone else found what I did: spare information for the new job seeker fresh out of college/boot camp/technical school.
I went to a technical college and was immersed in code every day for hours at a time. Yes, I was learning, and it was through hands-on experience. I built my own apps. It was exhilarating and challenging and exhausting.
Here's what you need to do, my fellow mobile devs:
1. LinkedIn
I know. I'm not a social media person, and adding another platform sounds horrible. Just hear me out. This is how I found a job. EVERY EMPLOYER WHO INTERVIEWED ME LOOKED AT MY PROFILE.
The Mighty Duck(s).
Use this tool (I just did the free trial version for a month) to send messages to a specified search group. Because I was looking for connections in Tampa, I sent this message to every "Android developer" in the "Greater Tampa Bay Area":
Hi F_N,
I'm looking for some connections in Florida, specifically the Tampa area. I'm just finishing my 2-year mobile app development program. Do you know of any Tampa-based tech groups? Do you have any advice or insight that might help me find a first job placement? Thanks for your time!Emily
F_N or whatever the variable is, plugs in the person's first name (yay object oriented programming!). The idea is to create a professional connection and to genuinely ask if they have any advice. They are, after all, already in the field, and so they'll have more experience they can draw upon to level any sage wisdom in your direction.
- Post screenshots of your work in "Featured" - make sure it's YOUR work, and also create a link to your GitHub profile here, if you have one.
- List the position you WANT as your profession, not where you're at right now. For example: "Android Developer - Kotlin, XML" is my profession listed.
- Make sure you mention something about teamwork and collaboration in your "About" section. Even though technical skills are the most important for most employers, the soft skills are highly critical. Show your amiability, you charmer.
- Refrain from dates in Education. It's irrelevant. It's enough that you know your stuff.
- If you have licenses or certs, same. Don't list dates. You got the achieve already, you stallion.
- Find any relevant groups and join them. I joined "Developers - Android, iOS developer, Blockchain..." and other mobile dev groups.
- Skills and endorsements: This is up for debate about how important it is. Maybe get a couple people to endorse you for skills, but literally anybody can endorse you for anything on LinkedIn. It's far more preferable to get a Recommendation, because that shows that someone you've worked with/are connected with thinks you're dope and they're willing to tell everyone who looks at your profile. You can ask for Recommendations by scrolling down to that section and clicking "Ask for a recommendation".
2. Dice
This is a great little app for recruiters to find technical prospects. Brush up your resume (there are plenty of examples, so I'm not listing it here) and post it here. You'll get hits pretty quickly. CAUTION: resume farms also prowl this platform, so be prepared for spam calls/emails. It's worth it for the recruiters you can connect with, but it can be annoying.
3. Glassdoor
Do. Your. Research.
Glassdoor has ratings from employees and interviewees about any given company. It's worth checking them out here, but it does mean you have to go through the process of posting a review to sign up, if you're not already there.
The most helpful posts I've seen here are from the interviewees for the position/department I'm interviewing. Some give very detailed information, and you can also get a feel for the culture of the company based on employee reviews.
Speaking of research...
4. RESEARCH
Please research your interviewer, the company, download the app if it's available, etc. Don't go into an interview blind - it only hurts YOU. Employers can tell if an interviewee hasn't done their due diligence in checking them out. You want to go into an interview with some position-specific questions, and they will be impressed if you show you've seen something you can help fix.
5. Know Your Basics
With Android, MVVM is the preferred architecture. Do you know why? If you don't, you need to know. Give it a goog, my friend. You'll get thrown questions about API calls, contrasting MVVM with MVC/MVP and what the differences are, particular programming patterns (haha alliteration!), if you've used dependency injections and how they work/what they are, what experience do you have with Gradle, and everything coroutines.
Though my examples are Android-specific, they can be applicable on some level to iOS, too. Here are some helpful courses I've found on Udemy for the technical interview:
- (Android):
https://www.udemy.com/course/android-developer-interview-prep/
https://www.udemy.com/course/coding-interview-cram-must-know-algorithms-and-questions/
- (iOS):
https://www.udemy.com/course/the-swift-arcade-data-structures-and-algorithms-bootcamp/
https://www.udemy.com/course/coding-challenges/
6. You Will Be Tested
Nearly every interview I've completed has some sort of coding challenge. I've had to build apps, do take-home coding challenges, and live interview coding challenges. They sound scary, but most are chill once you've had some practice. Here are a couple highly recommended places to start:
Remember that YouTube is your BFF 4 lyfe, and there are plenty of fantastic tutorials to guide you through the challenges if you're struggling. We all have been there.
7. Be Kind to Recruiters
Recruiters have a crap job. They're generally paid on performance, which means they really REALLY want you to get the job they're recruiting you to do. If they don't get a successful candidate, they don't get that money money, and that just sucks.
Having said this: be aware that there are so many rude people out there. If you feel at any time that your recruiter isn't doing their damnedest to get you hired, find another one who will. But be self-reflective: If you're being the jerk, they're not going to be as cool to you. Everyone wants to be treated like a human first.
FINALLY
Don't decide that, because an employer is looking for 2+ years of experience, that you're unqualified. These are mostly "ideal candidate" postings, and those unicorns are so rare they hardly ever fall into employers' laps. Most of us laypeople are just doing the good work of clean code, one line at a time. Be confident in your abilities. You've worked HARD to get here. Now go get that job, you wizard.






