Job description template

Xamarin Developer

Build, maintain, and enhance cross-platform mobile apps using Xamarin in a production environment. You will work independently on well-defined work, collaborate with product and engineering stakeholders, and deliver reliable releases with maintainable code.

Responsibilities

Develop and maintain Xamarin.Forms/Xamarin.iOS/Xamarin.Android features based on product requirements
Debug and resolve performance, stability, and release issues across iOS and Android
Design and implement clean app architecture patterns that improve readability and long-term maintainability
Integrate REST APIs and manage client-side data flow, including authentication and error handling
Write and maintain automated unit/UI tests where applicable and support regression prevention
Coordinate with backend and QA to ensure consistent behavior across platforms and devices
Review pull requests and contribute to engineering best practices for mobile development

Must-have qualifications

Hands-on experience building production mobile apps with Xamarin
Experience with Xamarin.Forms (or equivalent Xamarin UI patterns) for cross-platform development
Strong debugging skills for iOS and Android using logs, crash reports, and device testing
Experience integrating REST APIs in mobile clients, including authentication and error handling
Competence with app performance and stability improvements in Xamarin-based apps

Nice to have

Experience working with CI/CD pipelines for mobile builds and releases
Familiarity with automated testing frameworks for Xamarin (unit tests and/or UI testing)

What success looks like in 12 months

Ship planned mobile features independently and on schedule
Improve app reliability and reduce production issues
Enhance app performance and responsiveness
Strengthen API integration quality and user data flows
Increase maintainability through code quality and test coverage

Logistics

Full-time (40 hours a week), remote from Latin America.
Working hours overlap with US business hours.

About the company

[About your company: what you build, your stage and team size]

Want it tailored to your stack, seniority and time zone?

Customize with the free generator →

Interview scorecard

Score every candidate against the same bar

Deliver reliable, maintainable Xamarin mobile features that improve product outcomes while ensuring stability across iOS and Android.

Outcomes to measure

What this hire should deliver in the first year. Replace [N] with your own targets.

Ship planned mobile features independently and on schedule. Measure: deliver [N] features or user stories that meet acceptance criteria within [X] weeks of the planned date
Improve app reliability and reduce production issues. Measure: reduce mobile production incidents/crashes by [X]% over 12 months
Enhance app performance and responsiveness. Measure: improve key performance indicators (e.g., screen load time, API latency, or responsiveness) by [X]% measured in [chosen monitoring tool] over 12 months
Strengthen API integration quality and user data flows. Measure: increase successful API request rate by [X]% and reduce client-side error rate by [X]% over 12 months
Increase maintainability through code quality and test coverage. Measure: raise mobile automated test coverage (unit/UI where applicable) by [X]% or improve static quality metrics (e.g., lint rule pass rate) by [X]% over 12 months

Competencies and weights

What to evaluate, how much it counts and what a strong answer looks like.

Xamarin Production Engineering · 25%
This role requires direct, hands-on delivery in Xamarin-based production apps. Evaluated in Round 1.

Weak: Describes prior Xamarin work at a high level without explaining key implementation decisions or tradeoffs.
Meets the bar: Explains how they built and shipped Xamarin features, including relevant components and patterns they used.
Strong: Walks through specific production implementations, including constraints, debugging steps, and how they improved reliability.

API Integration Reliability · 21%
Mobile features depend on correct REST integration, resilient error handling, and secure auth flows. Evaluated in Round 2.

Weak: Gives general statements about calling APIs without discussing authentication, retries, or failure modes.
Meets the bar: Describes how they implemented REST calls and handled authentication, timeouts, and error states.
Strong: Details how they improved integration reliability (e.g., retry/backoff, token refresh handling, and consistent user messaging).

Xamarin.Forms UI Implementation · 19%
Cross-platform UI behavior must be implemented consistently and maintainably. Evaluated in Round 1.

Weak: Relies on vague explanations of UI code without addressing state, navigation, or platform differences.
Meets the bar: Explains how they structure Xamarin.Forms pages/components and manage view models/state.
Strong: Provides concrete examples of resolving UI consistency issues across iOS and Android and improving user experience.

Debugging and Crash Resolution · 19%
The role must quickly diagnose and resolve iOS/Android issues impacting releases. Evaluated in Round 2.

Weak: Cannot explain a clear debugging approach from symptom to root cause.
Meets the bar: Describes using crash reports/logs and device testing to identify and fix issues.
Strong: Shows a repeatable investigation method, including how they validated the fix and prevented recurrence.

Performance and Stability Improvements · 10%
Sustaining a responsive, stable app is essential for production success. Evaluated in Round 3.

Weak: Focuses only on theoretical performance tips without linking to observed measurements or outcomes.
Meets the bar: Explains how they improved performance/stability based on metrics and profiling evidence.
Strong: Provides specific examples where they reduced latency/memory usage and prevented stability regressions.

Independent Delivery Mindset · 6%
Mid-level, independent ownership is required for well-defined work. Evaluated in Round 3.

Weak: Relies heavily on others for task breakdown and decision-making, with limited ownership.
Meets the bar: Describes how they plan work, make implementation choices, and communicate progress/risks.
Strong: Shows clear examples of taking ownership end-to-end and coordinating with others only when needed.

Interview questions

Questions for every interview round

Each round has an owner, a time box and questions that test the competencies above.

Round 1: Mobile Xamarin Deep Dive
Mobile Engineering Lead · 50 min

Tell me about a Xamarin feature you shipped to production. What was the requirement, what architecture/pattern did you use, and what tradeoffs did you consider?
Walk through a Xamarin.Forms implementation you’re proud of. How did you structure pages/components and manage state or navigation?
Describe a time you handled platform-specific behavior in a Xamarin.Forms app. How did you keep behavior consistent without duplicating too much code?

Round 2: API Integration and Debugging
Senior Mobile Engineer · 55 min

How do you design REST API integration in a mobile client? Describe authentication handling, request/response mapping, and failure modes you plan for.
Give an example of a production bug tied to API integration (e.g., auth expiry, retries, malformed responses). What was your investigation path and resolution?
When you see crash reports or logs, how do you triage and reproduce the issue on iOS/Android? What signals do you look for?

Round 3: Stability, Performance, and Ownership
Engineering Manager · 45 min

Describe a performance or stability improvement you delivered in Xamarin (latency, memory usage, UI responsiveness, or crash reduction). What measurement did you use and what changed in the app?
Tell me about a time you owned a well-defined mobile deliverable end-to-end with minimal guidance. How did you plan, execute, and validate the outcome?
What’s your approach to preventing regressions after fixes (testing strategy, monitoring, or code review practices)?

Red flags to watch for

Cannot describe concrete Xamarin implementation details from production experience (architecture, UI patterns, or release behavior).
Trouble explaining how they debug using crash reports/logs and validate fixes on both iOS and Android.
API integration is handled in an ad-hoc way (no clear approach to authentication, error handling, retries/timeouts, or user-visible failure states).
Avoids ownership by waiting for others on task breakdown, decisions, or end-to-end validation.

How much does it cost to hire a Xamarin Developer in Latin America?

In 2026, a senior Xamarin Developer in Latin America costs $4,875 to $5,625 a month all-in, versus $14,625 in the US: up to 67% less. Mid-level starts at $3,250.

Country

Mid-level

Senior

Argentina

$3,250

$4,875

Brazil

$3,625

$5,375

Colombia

$3,250

$4,875

Mexico

$3,750

$5,625

United States

$11,875

$14,625

Monthly cost in USD, all-in: the talent's salary plus Teilur's flat 20% fee, from our 2026 rates. The United States row shows what the same role typically costs there.

Compare costs in the calculator →

Frequently asked questions

What does a Xamarin Developer do?

Typical responsibilities include: develop and maintain Xamarin.Forms/Xamarin.iOS/Xamarin.Android features based on product requirements; debug and resolve performance, stability, and release issues across iOS and Android; design and implement clean app architecture patterns that improve readability and long-term maintainability. The full list is in the template above.

How much does it cost to hire a Xamarin Developer in Latin America?

In 2026, a senior Xamarin Developer in Latin America costs $4,875 to $5,625 a month all-in, versus $14,625 in the US: up to 67% less. Mid-level starts at $3,250.

Can I customize this Xamarin Developer job description?

Yes. Teilur's free Job Description & Scorecard Generator rewrites it for your stack, seniority, time zone and hiring urgency in about 15 seconds. No sign-up needed.

Book a Free Consultation

Xamarin Developer Job Description Template