Resume comparison · ATS readiness
David Chung · October 2, 2026 · Career research · Tech careers & interview bank · Hotel & luxury careers
ATS means applicant tracking system. All six PDFs pass 8 of 8 local parsing checks. Job-fit numbers below are a transparent resume-evidence review, not Jobscan results, employer scores, or a prediction of an interview. Keep this score in your preparation materials rather than your application resume.
Company comparison
| Target | Local parse checks | Evidence score | Priority improvement |
|---|
| Eight Sleep — Senior Software Engineer, Mobile Android | 8 / 8 | 81 / 100
5 full, 3 partial | Add one real Compose UI/state-management example. Make the architecture pattern explicit only if it describes your implementation. Health/peripheral experience is a bonus gap. |
| Amazon / Ring — Sr. Builder, Mobile Platform | 8 / 8 | 88 / 100
6 full, 2 partial | Lead with platform adoption, rollout ownership and mentoring. Confirm architecture tenure and one modern Compose implementation. AI output acceptance/cycle time remains unmeasured. |
| Waymo — Senior Android Engineer, In-Car Experience | 8 / 8 | 81 / 100
5 full, 3 partial | Add mentoring if space permits and prepare one Compose UI example. Keep Android Auto and Android Automotive OS experience distinct. |
| OpenAI — Android Engineer, Ad Formats | 8 / 8 | 75 / 100
4 full, 4 partial | Replace the generic ads-pin line with the actual component, integration, tracking and launch scope. Add a measured rendering/performance example only if it exists. |
| OpenAI — Android Engineer, Applied Foundations | 8 / 8 | 88 / 100
6 full, 2 partial | This version fits Foundations better than Ad Formats today. Lead with reusable infrastructure and authoritative payment state; clarify identity/security ownership. |
| Anthropic — Staff Software Engineer, Android | 8 / 8 | 81 / 100
5 full, 3 partial | Make influence explicit: which teams adopted your architecture, what decisions you set, and how others delivered independently. Do not change your historical Senior title to Staff. |
| Meta — Android | 8 / 8 | Not scored | Verify the active requisition and team. A role-specific score would be unsupported without the requirements. |
How to read these numbers: Local parsing checks plus a manually selected eight-criterion evidence review per role. Each equally weighted criterion earns 1 for a specific resume example, 0.5 for partial/transferable/skills-only/user-pending evidence, 0 for absent evidence. Score = sum / 8 * 100, rounded. Criteria and credits are judgments, not an external ATS result or interview probability. Scores depend on selected criteria and do not rank employers by difficulty.
Original vs updated resume
| Area | Original | Current |
|---|
| Lyft positioning | AI/ML title with broad business-lift claims | Android title with concrete AI-client and platform ownership |
| Impact | More percentages, with several measurement gaps | Launch, reuse across three products, roughly 750K eligible-driver rollout scope, and targeted service recovery |
| Verdict | Large concurrency, latency and uptime claims | Native payment flows, queue behavior, indexing, compatibility and tested refund correctness |
| Company fit | One generic narrative | Platform/mentoring for Ring; navigation/audio for Waymo; native AI/shared foundations for OpenAI and Anthropic |
The current versions are more defensible and make your Android role clearer. Their weakest line is the generic ads contribution. The missing opportunity is a specific Compose example and a measured product or developer-efficiency result.
AI accomplishment metrics
Supported scope: the delivery workflow produces drafts for two mobile platforms, iOS and Android, with human review gates. The shared speech framework spans three products. These are scope metrics, not productivity uplift.
Best next result to recover: draft-PR acceptance rate. Define it as eligible AI-generated drafts merged after human review divided by all eligible drafts from a fixed request cohort, allowing a fixed follow-up window. Report rejected, abandoned and still-pending drafts separately; deduplicate regenerated drafts for the same task. Pair it with review effort, escaped defects and time to merge so acceptance cannot reward easy or low-value work.
Alternative: time to first CI-passing draft. Start at requirements acceptance and stop when both platform drafts pass agreed checks. Include failures; compare task complexity, and keep this separate from shipping velocity.
Actual values are missing from the supplied reference. The 52 merged PRs in the tool repository describe work on the tool, not generated draft acceptance. Do not convert that count into an AI productivity claim.
Existing labeled practice metrics and measurement plans
Eight Sleep — Senior Software Engineer, Mobile Android
81 / 100 evidence score
| Requirement | Credit | Resume evidence or gap |
|---|
| 6+ years shipping native Android | 1 | FantasyPros, Verdict and Lyft chronology supports the required Android tenure. |
| Kotlin | 1 | Native Kotlin/RxJava payment flows and modernization work. |
| Jetpack Compose | 0.5 | Listed in skills and prior modernization; no specific Compose component or implementation example. |
| Coroutines, Flow and MVVM/MVI | 0.5 | Coroutines/Flow/ViewModel listed; exact MVVM/MVI ownership is not explicit. |
| Scalable and testable app architecture | 1 | Shared speech framework, client/API contracts, unit/UI tests and regression coverage. |
| Polished UI and animation | 0.5 | Consumer chat/voice flows are relevant, but animation/custom Compose ownership is not shown. |
| Stability and app performance | 1 | Physical-head-unit diagnosis and release recovery with a targeted fix. |
| Cross-functional ownership at startup pace | 1 | Startup tech lead plus native/backend contract delivery at Lyft. |
Improve: Add one real Compose UI/state-management example. Make the architecture pattern explicit only if it describes your implementation. Health/peripheral experience is a bonus gap.
Current resume
Amazon / Ring — Sr. Builder, Mobile Platform
88 / 100 evidence score
| Requirement | Credit | Resume evidence or gap |
|---|
| Deep native mobile engineering | 1 | Android ownership across three companies and multiple products. |
| 7+ years architecture/design leadership | 0.5 | Startup and platform ownership are relevant; the specific seven-year architecture tenure is not demonstrated. |
| Shared mobile frameworks and platforms | 1 | Speech framework reused across three products. |
| Modern Kotlin/Compose development | 0.5 | Kotlin examples exist; Compose depth is mainly a skills claim. |
| AI-assisted development systems | 1 | Queued iOS/Android draft-PR pipeline with authenticated ingress and human gates. |
| CI/CD and test automation | 1 | FantasyPros CI/CD, unit/UI testing and release signing. |
| Large-scale production reliability | 1 | Consumer-app work, reported eligible voice audience, OS-cohort mitigation and verified fix. |
| Technical leadership and mentoring | 1 | Two new hires, cross-team delivery and infrastructure alignment. |
Improve: Lead with platform adoption, rollout ownership and mentoring. Confirm architecture tenure and one modern Compose implementation. AI output acceptance/cycle time remains unmeasured.
Current resume
Waymo — Senior Android Engineer, In-Car Experience
81 / 100 evidence score
| Requirement | Credit | Resume evidence or gap |
|---|
| Required software/Android tenure | 1 | Career chronology exceeds the posted five-year software and three-year Android thresholds. |
| Kotlin/Java and Compose depth | 0.5 | Kotlin/Java evidence; no detailed Compose UI example. |
| Native production product delivery | 1 | Driver AI launch, payment flows and six prior Android apps. |
| In-car product integration | 0.5 | Physical head-unit and Android Auto experience transfers; vehicle-resident control UI is not established. |
| Audio/media interaction | 1 | Shared voice framework and prototype evidence for navigation/audio conflict. |
| Android lifecycle and platform behavior | 1 | OS-specific connect diagnosis, lifecycle debugging and 16KB compatibility. |
| Client/backend collaboration | 1 | Shared API contracts and native BFF/payment states. |
| Design leadership and mentorship | 0.5 | Ownership is present, but mentoring is absent from this particular variant. |
Improve: Add mentoring if space permits and prepare one Compose UI example. Keep Android Auto and Android Automotive OS experience distinct.
Current resume
OpenAI — Android Engineer, Ad Formats
75 / 100 evidence score
| Requirement | Credit | Resume evidence or gap |
|---|
| Production Android ownership | 1 | Driver AI launch, native financial flows and consumer app ownership. |
| Kotlin and Jetpack Compose | 0.5 | Kotlin evidence is concrete; Compose depth is not shown. |
| Ads-format implementation | 0.5 | Ads-pin contribution is user-reported; rendering, tracking and launch responsibility are unspecified. |
| Shared rendering/UI primitives | 0.5 | Shared speech work supports reusable infrastructure, but shared ad-rendering primitives are not established. |
| Networking, state and lifecycle systems | 1 | Shared contracts, payment pending states and native lifecycle diagnosis. |
| Rendering/media performance optimization | 0.5 | Reliability is documented; frame time, media load latency and rendering optimization are not specific. |
| Automated quality and release workflows | 1 | Unit/UI tests, CI/CD, regression tests and release verification. |
| Cross-functional technical leadership | 1 | Android lead, shared contracts and three-product framework ownership. |
Improve: Replace the generic ads-pin line with the actual component, integration, tracking and launch scope. Add a measured rendering/performance example only if it exists.
Current resume
OpenAI — Android Engineer, Applied Foundations
88 / 100 evidence score
| Requirement | Credit | Resume evidence or gap |
|---|
| Production Android ownership | 1 | Launched products and native client implementation. |
| Kotlin/Java | 1 | Explicit languages and native Kotlin payment work. |
| UI, networking and local state | 1 | Chat/voice client, contracts and native pending payment flows. |
| Payments/commerce correctness | 1 | Provider callbacks and declined-withdrawal refund regression. |
| Identity/account security | 0.5 | Secure release/signing and authenticated tooling transfer; no account/family features are shown. |
| Reusable Android foundations | 1 | Speech framework reused across three products. |
| Performance and product trust | 0.5 | Reliability and financial correctness are clear; performance measurements are less specific. |
| Backend/product partnership | 1 | End-to-end native/BFF/API delivery and negotiated shared contracts. |
Improve: This version fits Foundations better than Ad Formats today. Lead with reusable infrastructure and authoritative payment state; clarify identity/security ownership.
Current resume
Anthropic — Staff Software Engineer, Android
81 / 100 evidence score
| Requirement | Credit | Resume evidence or gap |
|---|
| Production Android/Kotlin | 1 | Native client ownership and Kotlin/RxJava flows. |
| Compose/UI architecture | 0.5 | Compose skill and modernization claim; component-level depth is not shown. |
| 0-to-1 AI product ownership | 1 | Driver AI specification-to-launch leadership. |
| Full-stack product delivery | 1 | Startup client/backend ownership and Lyft contract integration. |
| Polished UX and app performance | 0.5 | Chat/voice delivery is relevant, but accessibility/rendering performance evidence is unspecified. |
| Staff-level technical influence | 0.5 | Cross-product framework and shared tooling are relevant; broader adopted technical direction needs clearer evidence. |
| Mentoring | 1 | Two new hires and coached progression toward independent feature ownership. |
| Audio experience | 1 | Shared speech framework and voice-client delivery. |
Improve: Make influence explicit: which teams adopted your architecture, what decisions you set, and how others delivered independently. Do not change your historical Senior title to Staff.
Current resume
Parsing checks and limits
- Extractable text
- Contact details
- Standard section headings
- Employment reading order
- Dates and education
- Small text-based PDF
- Unicode font mappings
- Visible Android keywords
Poppler extraction confirms text and reading order locally. The source layout is a single column, with contact details in the body. This does not test an employer’s parser or its automatic field assignment. Role headers combine company/title and dates on one line; verify autofilled fields when applying. The FantasyPros promotion arrow may also require manual field review. Minor line-break hyphenation is present.
No resumes were uploaded to a third-party scanner. No application content was changed solely to raise a score. ATS scores are review aids, not an accomplishment to append to your resume.