The Filter Behind the Listings
Most hiring pages read like wish lists. Zippi's open roles read like a filter: each is priced and scoped to surface build evidence, not pedigree.
The company provides affordable financial services to micro entrepreneurs in Brazil, a fintech using machine learning for credit risk, pricing sensitivity, and limit sensitivity. The four roles on its board: Senior Software Engineer (São Paulo or remote Brazil), Product Manager (same location), FP&A (Remote, US), and Growth Designer (Remote, US).
| Role | Location | Salary Range |
|---|---|---|
| Senior Software Engineer | São Paulo or remote Brazil | USD 50K–120K/yr |
| Product Manager | São Paulo or remote Brazil | USD 70K–150K/yr (Zero G Talent's board data shows) |
| FP&A | Remote, US | Not disclosed |
| Growth Designer | Remote, US | Not disclosed |
Board overall band across two salaried roles: $52K–$147K (median $135K), according to Zero G Talent's board data
Third-party trackers show similar headcount but diverge on pay transparency. JobScroller's daily scrape of Zippi's careers page counted four roles as of October 20, 2026, and noted none disclosed compensation. That snapshot included a Growth Business Analyst and two "Banco de Talentos" pipeline listings: talent pools, not open requisitions. Pipeline listings inflate apparent headcount without representing actual hiring slots. The Zero G Talent board surfaces only roles with live apply links and, where available, salary data the company chose to publish.
The founder team — Andre Bernardes, Bruno Lucas, Ludmila Pontremolez — has kept the organization lean since the $16M Series A led by Tiger Global in 2022. Glassdoor data from 23 candidate-reported interviews puts the average hiring cycle at 21 days, though that figure spans every function: Customer Experience roles closed in two days on average, while People Analyst searches stretched to 45. Engineering and product roles sit somewhere in the middle; the company has not published its own timeline.
The role mix signals a screen built for demonstrable build experience over credentials. A Senior Software Engineer role priced in Brazil isn't competing on cash with US hyperscalers; it filters for engineers who have shipped payments or risk infrastructure at scale and want ownership of a core product surface. The Product Manager band sits above the engineering median, reflecting the premium on someone who can translate thin-file underwriting into product decisions. The two US-remote roles, FP&A and Growth Designer, signal the next phase: capital efficiency storytelling and acquisition loops that don't rely on platform leverage.
What Clears the First Filter
Zippi's screening workflow isn't publicly documented like a Big Four firm's. The clearest first-party signal comes from a 2023 Arize blog post where the company's data team described how it evaluates candidates for machine learning practitioner, data scientist, and analytics engineer roles. The criteria — strong analytical thinking, problem solving, business acumen, high autonomy, flexibility, collaboration — read less like a wish list and more like a filter: each trait is observable in work product, not just claimed on a resume. The post makes the priority explicit: "When we hire data scientists, we prioritize candidates with a strong interest in statistics and machine learning, as well as experience working with real-world data." That phrasing — the quoted criterion — is the tell. A candidate who has only cleaned benchmark datasets or completed coursework projects will not clear the bar.
The interview loop reinforces that filter. One question the team "often asks" has candidates walk through the most challenging problem they've solved and reflect on what they'd do differently. The prompt surfaces two things simultaneously: depth of technical judgment and ability to communicate that judgment to a mixed audience. The post states it directly: "We believe that effective communication is critical to success in data science. Therefore, we look for candidates who can explain complex problems and insights in a clear and concise manner to both technical and non-technical stakeholders." In practice, a screening conversation punishes a technically correct answer that cannot be translated for a product manager or a founder.
The current open roles extend beyond the data team (FP&A, Growth Designer, Senior Software Engineer, Product Manager), but the same logic applies across functions. The founders are the decision makers behind those reqs. The compensation range signals a lean, high-leverage team where every hire must operate with the autonomy the data team explicitly called out.
Research shows no formalized multi-stage gate, with no public mention of an automated assessment, recorded video screen, or case study round. The Arize post dates to March 2023; current open roles span disciplines that didn't exist on the data team then. The screening workflow for a Growth Designer or FP&A lead may differ materially from the data science loop described two years ago. What remains consistent is the evidence bar: demonstrable build experience, communicated clearly, with business context attached. Candidates who lead with a portfolio of shipped work (models deployed, dashboards that drove decisions, features that moved metrics) and can narrate the tradeoffs they made will match the filter. Candidates who lead with credentials, certifications, or generic "passion for AI" language will not.
Who These Roles Fit — and Who They Don't
Senior Software Engineer. The role sits in a fintech building credit infrastructure for micro entrepreneurs. Candidates who have shipped payments, risk, or lending systems at scale, not just generic web backends, match the bar. Experience with high-throughput transaction processing, fraud detection, or real-time decisioning carries more weight than a degree from a top CS program. A GitHub history showing latency optimization, idempotency patterns, or regulatory-compliant data handling signals readiness. The São Paulo base and BR salary band indicate the engineering center of gravity is in Brazil; US-based applicants need a clear reason to work async across that time zone.
Product Manager. The role demands someone who has owned a technical product from spec to shipped iteration, preferably in fintech or B2B SaaS. The job involves translating that into product decisions: credit models, pricing levers, limit assignment. Candidates who have run A/B tests on credit flows, designed model-evaluation harnesses, or negotiated scope with ML engineers will recognize the work. Pure feature-factory PMs without technical depth, unable to read model evals or debate retrieval architecture, are out of scope.
Growth Designer. Not a brand or marketing design seat. It sits inside the product loop, designing onboarding, activation, and referral loops for a financial product. A portfolio showing funnel optimization, lifecycle messaging, or PLG motion in a technical product is the filter. Visual polish without metric-driven iteration history does not pass.
FP&A. Supports a company with two salaried roles: small, early, capital-efficient. The fit is an operator who has built models for pre-Series B or Series B fintech, comfortable with usage-based revenue, cohort forecasting, and runway scenario planning. Big-four audit background without operating experience is a mismatch; so is a corporate FP&A track that never touched a board deck.
Geography is explicit: two roles US-remote, two Brazil-based (São Paulo state) with remote BR flexibility. Candidates requiring visa sponsorship for Brazil or unable to overlap BR business hours for engineering and product roles should self-select out. The founders run a lean team; there is no relocation package, no immigration support, no onboarding ramp for time-zone misalignment.
Seniority is compressed. The "seniorization" trend documented across frontier tech in 2026 (entry roles demanding leadership, judgment, creativity) applies here in reverse: these are not entry roles, but they carry zero management overhead. An IC who wants to write code, design flows, or build models 80% of the time, and spend 20% on cross-functional alignment, fits. A candidate looking for title progression, direct reports, or a structured career ladder does not.
The filter rewards evidence of building, breaking, and fixing in production. A candidate who claims "led credit strategy" but cannot walk through a specific model failure, its root cause, and the fix deployed, will not advance. Applicants who cannot point to a shipped artifact (a repo, a live flow, a model card, a financial model that survived board review) should not apply.
How to Tailor an Application to Zippi's Bar
Frontier-tech hiring converges on one pattern: the first filter is almost always automated; the second is a human scanning for proof of build. Zippi runs a lean team; its four open roles span the same quartet, and the founders read applications directly. Your resume passes software first, then a founder's eyes. Both screens reward specificity.
Resume: match the exact vocabulary, then prove the work
Applicant tracking systems parse for the precise terms in the job description. The Senior Software Engineer posting lists a tech stack; the Product Manager posting names product frameworks. Mirror those terms verbatim in your Skills and Experience sections, not synonyms. Standard headings (Experience, Skills, Projects) keep parsers from dropping sections. But keyword matching alone backfires at the human layer. Founders at early-stage companies report discarding resumes where the claimed stack doesn't match the project evidence. For each role you list, add a one-line build artifact: "Shipped the checkout redesign that lifted conversion 12% in A/B test" beats "Responsible for frontend improvements." Recruiters consistently reward quantified impact over responsibility lists.
Portfolio and LinkedIn: make the proof searchable
A resume gets you to the portfolio review. The Growth Designer role demands a portfolio link; the FP&A role benefits from a public model or dashboard you've built. Host work on a personal site or GitHub with clear READMEs, not a PDF. LinkedIn functions as a secondary index: the same keywords from the job description should appear in your Headline, About, and Skills sections. Searchable LinkedIn profiles outperform resumes at the portfolio-review stage, recruiters at frontier-tech firms report. For Zippi's Brazil-based roles (Senior Software Engineer, Product Manager), bilingual project descriptions (Portuguese and English) signal readiness for the distributed team.
Cover note: short, specific, or skip it
Founders at seed-to-Series A companies read cover notes when they're short and signal genuine homework; they skip generic ones. The 1752.vc startup guide recommends a three-sentence format: why this company, why this role, one concrete thing you've built that maps to the top responsibility in the job description. For Zippi, that means referencing the product area the role owns: growth loops for the Growth Designer, financial modeling for FP&A, platform scalability for the Senior Software Engineer. If you can't name a specific Zippi initiative or metric you'd move, don't send a note. A sloppy note hurts more than no note.
Interview prep: demonstrate the skill, don't describe it
Research warns against keyword stuffing you can't defend. Zippi's screen will test the exact competencies in the job description. For the Senior Software Engineer, expect a live coding or system-design exercise in the posted stack. For Product Manager, prepare a 10-minute walkthrough of a real feature you shipped: problem definition, trade-offs, measured outcome. For Growth Designer, bring a case study with before/after metrics. For FP&A, walk a model you built from raw data to board-ready output. AI tools can help you rehearse by generating likely follow-up questions from the job description, but the substance must be yours. The board's salary bands reflect roles where demonstrated output sets the offer, not pedigree.
What This Hiring Push Signals — and What It Doesn't
Zippi's four roles form a deliberate quartet, not a hiring spree. The composition (one senior engineer, one product lead, one growth designer, one finance operator) maps to the AI-native startup pattern: teams 25% smaller than non-AI peers, engineer shares 13% higher, hierarchies half a seniority level flatter. Zippi's founders are building a core that can ship product and manage capital without the bloat that characterized the 2020–2022 expansionary phase.
The Brazil–US split across engineering and product roles (São Paulo and remote Brazil for Senior SE and PM; remote US for FP&A and Growth Designer) reflects a talent strategy that predates the current correction. Zippi isn't chasing arbitrage; it's accessing a region where senior engineering and product talent exists at a fraction of Bay Area burn.
This push does not signal a return to 2021 hiring velocity. The correction that began in late 2022 shifted leverage to employers. YC batches self-identifying as AI rose from roughly 15% in early 2020 to over 50% in 2024, but capital concentrated early: 70% of AI startup funding in 2024 went to seed through Series B, with US firms supplying roughly half of Series C+ dollars. Zippi's four roles sit in that early-stage window: targeted, not sprawling.
Anthropic's trajectory offers a sharper contrast than any sector average. The company tripled headcount in a year while junior technical hires collapsed from 27% to 9% of new technical roles; postings for juniors fell sharply after December 2025. Agent hours outnumbered human hours six to one by August 2026. Code commits per engineer rose 5x in six months. Zippi's Senior SE role asks for proven build experience, not potential, exactly the profile that survives an environment where agents absorb implementation work and humans direct it. The FP&A role signals the same discipline: capital efficiency over headcount growth.
The broader frontier-tech market shows conflicting signals. LinkedIn-tracked startups grew headcount 20.6% year-over-year, nearly double Big Tech's 10.6%, while biotech and pharma announced layoffs in the thousands across October 2026 alone. Microsoft's Work Trend Index found 78% of leaders considering AI-specific hires (95% at "Frontier Firms"), yet 33% also plan to use AI to reduce headcount. Forty-seven percent prioritize upskilling existing employees. Zippi's Growth Designer role sits in that tension: a specialized hire to amplify acquisition, not a generalist add.
None of this makes Zippi a bellwether. Four roles at one company indicate a specific build plan at a specific stage. The filter holds because the roles demand it. The screen isn't published — it's encoded in what the work requires.
Working in frontier tech? Zero G Talent tracks the openings: see every open Zippi role, browse frontier tech jobs, the companies hiring, and the people building the field.