CV-eksempel for Mobile Developer

Choose the right format for a Mobile Developer resume

Use a reverse-chronological format. Hiring managers at app studios, product companies, and consulting firms all expect to see your most recent role first, and applicant tracking systems (ATS) parse this layout most reliably. Keep the document to one page if you have under ten years of experience; two pages is acceptable beyond that.

Stick to a single-column layout with clear section headers. Avoid graphics, icon-heavy skill bars, or multi-column designs — these break ATS parsing and obscure the technical details recruiters actually read. Use 10–12 pt font, consistent margins (0.75–1 inch), and save as a PDF unless the job posting explicitly requests a .docx file.

• Name your file: FirstLast_MobileDeveloper_Resume.pdf
• Sections in order: Summary, Skills, Experience, Projects (if relevant), Education, Certifications
• Link to your App Store or Google Play published apps directly in the header or project section
• Keep hyperlinks live — portfolio URLs, GitHub, and LinkedIn are all expected

Write a professional summary that positions you immediately

Your summary should name your platform specialization (iOS, Android, or cross-platform), your years of experience, and one or two concrete outcomes. Recruiters spend six to ten seconds on an initial scan; make your niche obvious in the first line. Avoid phrases like 'passionate developer' or 'team player' — they add no information.

Example: "iOS developer with 6 years building consumer-facing Swift applications across fintech and health tech. Shipped 4 App Store apps with a combined 2M+ downloads; reduced average crash rate from 1.8% to 0.3% at Brightpath Health by refactoring the networking layer to async/await. Experienced with SwiftUI, Combine, and MVVM architecture."

Write work-experience bullets that show impact, not just duties

Each bullet should follow an action verb → task → measurable result structure. Mobile development has abundant metrics available to you: crash rates, app store ratings, load times, DAU/MAU, release cadence, and binary size. Use them. Vague bullets like 'developed features for mobile app' are the single fastest way to get screened out.

Quantify performance improvements, user growth, and delivery speed whenever possible. If you led a migration — Objective-C to Swift, REST to GraphQL, or MVC to MVVM — say what it improved and how long it took.

• Rebuilt the checkout flow in Jetpack Compose, cutting average screen-load time from 2.1 s to 0.6 s and increasing conversion rate by 14% (A/B tested, 90-day window, 400K users).
• Led migration of a 180K-line Objective-C codebase to Swift over 8 months; post-migration crash-free session rate improved from 97.1% to 99.4% and build time dropped by 35%.

Skills and certifications recruiters and ATS systems look for

List skills in a dedicated section using exact terms from job postings — ATS systems match keywords literally. Separate languages, frameworks, and tools into logical groups rather than dumping everything into one comma-separated line. Certifications carry real weight in mobile: Google's Associate Android Developer credential and Apple's App Development with Swift curriculum are the most recognized entry-to-mid credentials; for senior roles, AWS Certified Developer or Google Cloud Professional Cloud Developer signals backend integration depth.

Cross-platform experience in Flutter or React Native is increasingly required at smaller teams, so list it explicitly even if it is secondary to your native work.

• Languages: Swift, Kotlin, Dart, TypeScript, Objective-C
• Frameworks/Tools: SwiftUI, UIKit, Jetpack Compose, Flutter, React Native, Xcode, Android Studio
• Testing: XCTest, Espresso, Detox, Firebase Test Lab
• CI/CD: Fastlane, Bitrise, GitHub Actions, TestFlight, Firebase App Distribution
• Certifications worth listing: Associate Android Developer (Google), App Development with Swift (Apple), AWS Certified Developer – Associate

Education, licenses, and extras that round out the resume

A BS in Computer Science, Software Engineering, or a related field is the standard expectation at most mid-to-large companies, but a strong portfolio of shipped apps can offset a non-traditional background at startups and agencies. List your degree, institution, and graduation year — GPA only if above 3.5 and within five years of graduation.

Add a Projects section if you have published apps not tied to an employer. Include the app name, platform, a one-line description, peak download count or rating, and a direct link. Open-source contributions on GitHub that demonstrate mobile work belong here too. Omit hobbies unless they directly connect to the role — a side project with 50K installs is relevant; recreational hiking is not.

• Include App Store / Google Play links with download or rating data
• List relevant coursework only if you are a new grad with limited experience
• WWDC session attendance or Google I/O talks you have presented at are worth one line

Mistakes to avoid

• ×Listing every technology you have ever touched instead of prioritizing the stack named in the job description, which dilutes credibility and confuses ATS keyword matching.
• ×Omitting platform version and OS compatibility details — stating 'supports iOS 15+' or 'targets API level 26+' signals production awareness that generic bullets miss.
• ×Using screenshots or app icons in the resume file, which corrupt ATS parsing and rarely render correctly when the document is printed or converted by a recruiter's system.
• ×Describing team size and project scope without naming your individual contribution, leaving hiring managers unable to judge your actual level of ownership or technical depth.

Frequently asked questions

Should I have separate resumes for iOS and Android jobs?

Yes, if you apply to both platforms seriously. Tailor the summary, skill order, and bullet emphasis to match the platform — an iOS recruiter scanning for SwiftUI experience should not have to read past Kotlin details to find it. Keep a master document and maintain two targeted versions.

How important is a GitHub profile for a Mobile Developer resume?

It is expected at most companies, especially those with a technical screen early in the process. Link it in your header, but make sure pinned repositories are clean, have README files, and reflect the kind of work you want to be hired for. An empty or outdated GitHub is worse than no link at all.

Do I need to list every app version I worked on, or just the current one?

List the app once per employer and describe the arc of your work across versions in your bullets — for example, noting that you contributed from v1.2 through v4.0 tells a stronger story than separate entries. Focus bullets on the features or improvements you owned, not the version numbers themselves.