ZipRecruiter

Log In

2

Part Time Android Developer Jobs in Chicago, IL (NOW HIRING)

All JobsAndroid Developer JobsPart Time Android Developer JobsPart Time Android Developer Jobs in Chicago, IL

Part Time Android Developer information

See Chicago, IL salary details

$11

$63

$85

How much do part time android developer jobs pay per hour?

As of Aug 13, 2026, the average hourly pay for part time android developer in Chicago, IL is $63.02, according to ZipRecruiter salary data. Most workers in this role earn between $55.29 and $72.60 per hour, depending on experience, location, and employer.

What is a part time Android developer?

A Part Time Android Developer is a software developer who specializes in building and maintaining applications for Android devices, but works less than a standard full-time schedule. They may be employed by a company, work as freelancers, or contribute to multiple projects at once. Their responsibilities typically include writing code in Java or Kotlin, debugging, testing, and collaborating with other team members to deliver functional Android apps. Part time positions allow for flexible work hours, which can be ideal for students, parents, or professionals seeking work-life balance.

What does a part time Android developer do?

A part-time Android developer has responsibilities that focus on designing and creating new applications and software for the Android operating system on a schedule of fewer than 35 hours each week. Your duties are to devise new applications, write the code for them, test them for errors and other bugs, and create updates for applications to keep them fresh and functional. Part-time Android developers collaborate with other people on the development team to carry out the development process from ideation to completion. You must understand the differences between various frameworks to decide which one to use for each application.

What are the key skills and qualifications needed to thrive as a part time Android developer, and why are they important?

To thrive as a Part Time Android Developer, you need proficiency in Java and Kotlin, a solid understanding of Android SDK, and prior experience delivering Android apps, often supported by a relevant degree or portfolio. Familiarity with development tools like Android Studio, version control systems such as Git, and experience with RESTful APIs and Firebase are typically required. Strong problem-solving, time management, and communication skills help you efficiently collaborate and deliver quality work in a limited schedule. These competencies ensure you can build, maintain, and enhance Android applications effectively while meeting project deadlines.

How do part time Android developers typically collaborate with full time team members on projects?

Part-time Android developers often work closely with full-time engineers, designers, and product managers through scheduled meetings, shared documentation, and collaboration tools like Slack, Jira, or GitHub. Clear communication and well-defined tasks are essential to ensure alignment and smooth handoffs. While part-time roles may involve fewer hours, developers are expected to actively participate in code reviews, sprint planning, and regular check-ins to stay integrated with the team and maintain project momentum.
More about Part Time Android Developer jobs
What are the most commonly searched types of Android Developer jobs in Chicago, IL? The most popular types of Android Developer jobs in Chicago, IL are:
What are popular job titles related to Part Time Android Developer jobs in Chicago, IL? For Part Time Android Developer jobs in Chicago, IL, the most frequently searched job titles are:
What job categories do people searching Part Time Android Developer jobs in Chicago, IL look for? The top searched job categories for Part Time Android Developer jobs in Chicago, IL are:
Part Time Android Developer jobs near you
Infographic showing various Part Time Android Developer job openings in Chicago, IL as of August 2026, with employment types broken down into 22% Full Time, and 78% Part Time. Highlights an 70% In-person, and 30% Remote job distribution, with an average salary of $131,088 per year, or $63 per hour.

Fractional Product Systems Designer (Web + iOS) - Remote (U.S. Based)

Serious Development

Chicago, IL • Remote

Part-time

Posted 20 days ago

Job description

Part-time: 20-30 hours per month

Details: Competitive hourly rate (Senior, Fractional). Long-term engagement if mutually successful

Job ID: 26FRA301

Fractional Product Systems Designer (Web + iOS) - Remote (U.S.- based)
    Overview

    Serious Development builds internal business applications at speed using: v0 for prototyping, Angular + PrimeNG for implementation, Native iOS apps that feel like iOS, not web-on-a-phone. We are seeking a Fractional Product Systems Designer (Web + iOS) to design how our products behave over time.

    Why This Role Exists

    We build internal business applications at speed using:

    • v0 for prototyping
    • Angular + PrimeNG for implementation
    • Native iOS apps that must feel like iOS, not web-on-a-phone

    As our velocity increased, traditional screen-based design became unnecessary. What did become necessary is system-level UX ownership.

    This role exists to ensure our products remain:

    • Predictable
    • Consistent
    • Native to their platforms
    • Easy to learn and hard to misuse

    You will not be designing every screen. You will be designing how the product behaves over time.

    Who You AreRequired
    • Senior-level product or systems designer
    • Experience with internal or enterprise applications
    • Strong systems thinking; comfortable defining rules and constraints
    • Deep familiarity with iOS as a platform (not just mobile UI)
    • Comfortable challenging PMs and saying don't ship that
    • Pragmatic, opinionated, and not precious about visuals

    Strong Plus

    • Experience cleaning up inconsistent products
    • Familiarity with component-based design systems
    • Experience working with engineers directly
    • Prior fractional or advisory roles

    Red Flags (for us)

    • Portfolio-first, system-light background
    • Strong preference for redesigns over convergence
    • Focus on delight over clarity and predictability
    • Reliance on Figma as the primary output
    What You'll Be Responsible ForProduct-wide UX coherence
    • Own interaction patterns across the product
    • Ensure similar problems are solved the same way
    • Reduce inconsistency as new modules are added
    • Prevent UX drift as multiple PMs and teams ship in parallel
    Working within existing products
    • Audit current applications and patterns
    • Identify what already works and should be preserved
    • Drive convergence not redesign-for-the-sake-of-redesign
    • Respect user muscle memory
    Web UX (Angular + PrimeNG)
    • Define how PrimeNG components are used (tables, forms, filters, modals)
    • Establish behavioral standards:
    • States
    • Errors
    • Permissions
    • Progressive disclosure
    • Prevent almost-the-same component variants
    iOS UX (Native-first)
    • Ensure strict alignment with Apple Human Interface Guidelines
    • Catch web/Android patterns leaking into iOS
    • Enforce native navigation, gestures, and control usage
    • Prioritize platform correctness over internal consistency when they conflict
    Partnering with PMs
    • Review v0 prototypes and early implementations
    • Provide fast, opinionated feedback
    • Help PMs reason through UX tradeoffs
    • Establish clear guardrails PMs can confidently operate within
    What You Will Not Be Doing
    • Pixel-perfect mock production
    • Designing every feature or screen
    • Maintaining Figma parity with code
    • Visual branding or marketing design
    • Creating handoff artifacts for engineers
    • If your default output is screens, this is not the right role.
    What Success Looks Like
    • UX feels consistent across modules and platforms
    • PMs move fast without inventing new patterns
    • Fewer usability questions from users
    • Faster onboarding with less training
    • No why does this work differently over here? moments
    • No large-scale UX rewrites six months later
    How You'll Work
    • Review-heavy, not production-heavy
    • Embedded early in feature thinking, not late-stage polish
    • Prefer rules, patterns, and written guidance over visuals
    • Use Figma only when a concept cannot be expressed clearly in text or prototypes
    • Code and prototypes are the source of truth.