Automatically Screen LinkedIn Applicants With AI

# Screening Assessment: Maria Gomez

## 1. Candidate Summary
Maria Gomez is a backend engineer with 6 years of experience spanning Stripe and a Series B lending startup, with deep fintech and payments expertise. She has hands-on experience building ACH payment rails in Python/Django and led a significant AWS Lambda migration.

## 2. Fit Score
**92/100** — Exceeds the core requirements across experience, stack, and domain; only minor unknowns around seniority signals and scope of leadership.

## 3. Strengths vs. Job Requirements
- **Experience threshold met:** "6 years software engineering" exceeds the 5+ year requirement.
- **Payments domain — strong match:** Worked at "Stripe" and "built ACH payment rails," directly satisfying the "must have payments experience" requirement.
- **Python proficiency confirmed:** "Built ACH payment rails in Python/Django."
- **AWS experience confirmed:** "Led migration to AWS Lambda," indicating both technical depth and leadership.
- **Fintech relevance:** Tenure at both "Stripe" and a "Series B lending startup" demonstrates sustained fintech focus.
- **Education:** "BS Computer Science from UT Austin" — solid CS foundation.
- **Location alignment:** "Open to remote roles in US" — matches typical remote U.S. postings.

## 4. Gaps & Red Flags
- **Scope of Lambda migration unclear:** "Led migration to AWS Lambda" is not quantified (team size, scale, duration).
- **Breadth of AWS services unknown:** Only Lambda is mentioned; senior backend roles often require RDS, SQS, IAM, etc.
- **Seniority signals limited:** No mention of mentorship, architecture ownership, or cross-team leadership typical for a Senior title.
- **Tenure split not detailed:** Years at Stripe vs. the lending startup are unspecified — could affect depth assessment.
- **Payment breadth:** ACH is called out, but no mention of card rails, wires, or ledger/reconciliation systems.

## 5. Suggested Screening Questions
1. Can you walk me through the AWS Lambda migration you led — what was the pre-existing architecture, the scale (traffic, services migrated), and what tradeoffs did you weigh vs. ECS/EKS?
2. At Stripe, what part of the payments stack did you own, and how did that experience inform how you built ACH rails at the lending startup (idempotency, retries, reconciliation, NACHA compliance)?
3. Describe a time you made a senior-level architectural decision that impacted other teams — how did you drive alignment and measure the outcome?

## 6. Recommendation
**Advance to Interview** — Strong alignment on all must-haves (Python, AWS, payments, 5+ years, fintech). Recommended next step: technical screen focused on payments systems design and AWS architecture breadth.

# Screening Assessment: Maria Gomez

## 1. Candidate Summary
Maria Gomez is a backend engineer with 6 years of directly relevant experience at Stripe and a fintech lending startup, demonstrating both payments expertise and AWS infrastructure work. She holds a CS degree and has led significant technical initiatives aligned with the role's core requirements.

## 2. Fit Score
**92/100** — Exceptional alignment with all primary requirements: 6 years experience exceeds 5+ threshold, proven payments domain expertise (ACH rails), AWS proficiency (Lambda migration), Python/Django backend skills, and fintech context.

## 3. Strengths vs. Job Requirements

- ✅ **Experience level**: 6 years meets/exceeds 5+ year requirement
- ✅ **Payments expertise**: Built ACH payment rails in Python/Django—directly addresses "must have payments experience"
- ✅ **AWS proficiency**: Led migration to AWS Lambda, demonstrating hands-on cloud infrastructure work
- ✅ **Python backend**: Explicit Django/Python experience in fintech context
- ✅ **Fintech domain**: Two positions in fintech (Stripe + lending startup) show deep industry knowledge
- ✅ **Education**: BS Computer Science from UT Austin provides strong foundation
- ✅ **Work arrangement**: Open to remote roles in US matches likely flexibility needs

## 4. Gaps & Red Flags

- ⚠️ **Vague startup details**: "Series B lending startup" lacks specifics on scale, outcomes, or role scope (tenure, team size not mentioned)
- ⚠️ **Timeline unclear**: No explicit dates provided; cannot verify 6-year claim or assess employment continuity
- ⚠️ **Leadership scope ambiguous**: "Led migration" suggests seniority, but no mention of team size or mentorship experience
- ⚠️ **Technical breadth unknown**: Profile focuses on payments/AWS; unclear experience with other critical systems (databases, monitoring, APIs beyond payments)

## 5. Suggested Screening Questions

1. **On payments depth**: "Walk us through the ACH payment rails you built at the lending startup—what volume did they handle, what were the key architectural decisions, and how did you handle reconciliation and failure scenarios?"

2. **On AWS/Lambda transition**: "Tell us about the Lambda migration you led—what challenges did you face moving from the previous infrastructure, how did you handle state management, and what were the cost/performance outcomes?"

3. **On career timeline & motivation**: "I see you have 6 years of fintech experience. Can you walk me through your roles chronologically, including tenure at each company and why you're interested in this role now?"

## 6. Recommendation
**Advance to Interview** — Maria is a strong fit with minimal friction. Her payments experience (ACH rails, Stripe background) and AWS Lambda expertise directly match job requirements. Screen call should clarify employment timeline, leadership scope, and technical breadth beyond payments to confirm senior-level capability.

# Applicant: Maria Gomez

## 1) Candidate Summary
Maria Gomez appears to be a strong match for a **Senior Backend Engineer (Python, AWS, fintech)** role. She has **6 years software engineering experience** across **Stripe** and a **Series B lending startup**, with direct evidence of **payments**, **Python/Django**, and **AWS Lambda** experience.

## 2) Fit Score
**92/100** — Exceeds core requirements with **“6 years software engineering”**, direct **payments experience** from **Stripe** and **“built ACH payment rails in Python/Django”**, plus relevant **AWS** migration leadership.

## 3) Strengths vs. Job Requirements
- **Meets experience threshold:** Profile states **“6 years software engineering”**, exceeding the **5+ years required**.
- **Strong payments/fintech background:** Worked at **“Stripe”** and a **“Series B lending startup”**, both highly relevant to fintech.
- **Direct payments implementation experience:** Specifically **“built ACH payment rails in Python/Django”**, which strongly aligns with the requirement for **payments experience**.
- **Relevant backend stack:** Hands-on with **“Python/Django”**, directly matching the backend emphasis.
- **AWS experience with leadership signal:** **“Led migration to AWS Lambda”** suggests practical cloud architecture experience and ownership.
- **Education is solid:** **“BS Computer Science from UT Austin”** supports technical foundation.
- **Location/work model alignment:** **“Open to remote roles in US”** fits many remote hiring setups.

## 4) Gaps & Red Flags
- **AWS breadth not fully clear:** Only **“migration to AWS Lambda”** is mentioned; broader AWS services (e.g., RDS, SQS, ECS, IAM, observability) are not specified.
- **Seniority scope needs validation:** “Led migration” is promising, but people leadership, system design scale, and ownership level are not fully detailed.
- **Compliance/regulatory depth not stated:** For fintech roles, experience with PCI, NACHA, fraud/risk controls, reconciliation, or auditability is not mentioned.
- **Scale/performance metrics missing:** No explicit throughput, latency, uptime, or transaction volume details provided.

## 5) Suggested Screening Questions
1. You **“built ACH payment rails in Python/Django”** — what parts of the payment lifecycle did you own, and how did you handle retries, reconciliation, and failure scenarios?
2. You **“led migration to AWS Lambda”** — what drove that architecture decision, what AWS services were involved beyond Lambda, and what measurable outcomes did the migration achieve?
3. At **Stripe** and the **lending startup**, what was your level of ownership in backend design decisions, and can you describe a complex production incident or scaling challenge you solved?

## 6) Recommendation
**Advance to Interview** — Strong evidence of fit on the most important dimensions: **5+ years**, **payments**, **Python backend**, and **AWS** experience, with credible fintech domain alignment.

Of course. Here is the structured screening assessment for the applicant.

***

### Screening Assessment: Maria Gomez

**(1) Candidate Summary**
Maria is a highly relevant Senior Backend Engineer with 6 years of experience in the fintech and payments space at respected companies like Stripe. Her background shows direct, hands-on experience building payment systems with Python and leading migrations to AWS, making her a near-perfect match for the core requirements of this role.

**(2) Fit Score**
**98/100** — Her profile is an exceptional match, with direct experience in Python, AWS, and payments at highly relevant companies.

**(3) Strengths vs. Job Requirements**
*   **5+ Years Experience:** Matches. The profile states

### Maria Gomez

#### Candidate Summary
Maria Gomez is a Senior Backend Engineer with 6 years of experience at Stripe (fintech payments leader) and a Series B lending startup. She specialized in Python/Django for ACH payment rails and led an AWS Lambda migration. Holds a BS in Computer Science from UT Austin and is open to remote US roles.

#### Fit Score
**95/100** - Excellent match on years of experience, Python/AWS skills, and direct fintech payments expertise at Stripe.

#### Strengths vs. Job Requirements
- **5+ years experience**: "6 years software engineering at Stripe and a Series B lending startup" exceeds requirement.
- **Python backend**: "Built ACH payment rails in Python/Django" directly aligns with Python requirement.
- **AWS**: "Led migration to AWS Lambda" demonstrates hands-on senior-level AWS expertise.
- **Fintech/payments**: Stripe role and "ACH payment rails" at lending startup provide proven payments experience in fintech.

#### Gaps & Red Flags
- None significant; profile fully aligns with all stated requirements.
- Minor note: Experience at Series B startup may lack Big Tech scale, but Stripe compensates.

#### Suggested Screening Questions
1. Can you walk us through your work building ACH payment rails in Python/Django at the lending startup, including any challenges with compliance or scalability?
2. Describe the AWS Lambda migration you led at Stripe—what were the key outcomes, and how did you handle serverless payments processing?
3. How have you optimized backend systems for high-volume fintech transactions, and what metrics did you improve?

#### Recommendation
**Advance to Interview**