Financial & Operations Analyst - Remote (Hr58093)

Sagan World Llc.; Rosario; Remote; ARS 137,946,000 - 275,891,000; Full time

Benefits offered by this job

Remote across LATAM

Weekly USD contractor pay

Up to 20 days PTO per year

Direct line to Head of Engineering

Job summary

Sagan World Llc. is hiring a UX Analyst (Product Workflows) for a field-operations SaaS product. This fully remote LATAM role focuses on mapping and improving end-to-end workflows from field capture to reporting, collaborating with an engineering-driven team to ensure builds are accurate and scalable.

You will design the flow logic, states, and handoffs, prototype in Figma, and validate with usability tests, while embracing accessibility and offline/retry considerations.

Qualifications

• Experience designing complex, multi-step workflows for B2B/SaaS products.
• Portfolio showing full problem-to-logic-to-final flow, not only polished screens.
• Systems thinking across states, branches, permissions, errors, and edge cases.
• Clear flow documentation and specs engineers can build from.
• Strong Figma for mapping, prototyping, and handoff.
• AI fluency to explore options without lowering quality.
• Awareness of accessibility considerations in flows and interactions.

Responsibilities

• Map property-management workflows end to end from field capture to review.
• Talk to workflow users and redesign with fewer steps.
• Write the logic, branches, and edge cases behind each flow for build accuracy.
• Design offline and retry states so users know status when signal drops.
• Prototype in Figma and validate with quick usability runs.
• Annotate specs for engineering with states, rules, and microcopy.

Skills

Workflow design

Portfolio evidence

Systems thinking

Flow documentation

Figma mapping

AI fluency

Accessibility

Tools

Figma

AI tools

Job description

UX Analyst (Product Workflows) | Field Operations SaaS | Remote (LATAM)

Our client is a software company that helps property managers inspect properties and turn what they find into clear, shareable reports. Someone opens the app on their phone, walks a property capturing photos, video, and voice notes even with no signal, since it works offline and syncs later, then reviews everything and runs reporting on the web. It plugs into the property-management systems teams already use, so the data doesn't sit in a silo. They've been at this since 2014, profitable and self-funded the whole way, and today more than 20,000 people use it across the U.S. and 20-plus countries, together capturing over 100 million inspection photos. There's even a new AI feature that turns spoken notes into a finished report on its own, so an inspector can walk a property, say what they see, and skip the typing.

Your Role

You own how work moves through the product from the first step to the last: the steps, the logic, the states, and the handoffs between the phone in the field and the review screen back at the office. You'll map how property managers actually work, find where a flow gets confusing or breaks, and redesign it so the next person doesn't have to think about it. There's another designer on the team who leans visual and component-level, so you lean process and flow, and together you cover the whole surface. This is a design role about how work behaves, not visual polish. You report to the Head of Engineering, and what you design gets built instead of sitting in a backlog.

You'll

• Map property management workflows end to end, from field capture to sync to review to report
• Talk to the people who live in a workflow, then redesign it with fewer steps
• Write the logic, branches, and edge cases behind each flow so engineering builds it right the first time
• Design the offline and retry states so users always know what's happening when the signal drops
• Prototype in Figma and check it with quick usability runs
• Hand engineering annotated specs (states, rules, microcopy) they can build from with little back-and-forth
• Review builds, log precise issues, and confirm the fixes before sign-off

You Bring

• Experience designing complex, multi-step workflows (B2B, SaaS, operations, or field tools). We care more about how the flows in your portfolio hold up than about a year count, and we'll happily hire someone earlier in their career who clearly has the instinct for this
• A portfolio that shows the whole path, problem to mapping to logic to final, not just polished screens
• Systems thinking: you design for the states, branches, permissions, errors, and empty cases, not just the happy path
• You write clear flow documentation and specs engineering can build straight from
• Strong Figma for mapping, prototyping, and handoff
• AI fluency: you use tools like ChatGPT, Claude, or Figma AI to move through options and specs faster without lowering quality
• A working handle on accessibility (contrast, tap targets, text size, focus order)

Bonus Points

• Service design or process mapping (journey maps, service blueprints, workflow diagrams)
• Background in workflow-heavy B2B products: property management, field services, logistics, or operations tooling
• Comfort using analytics to confirm a redesigned flow actually performs better

What's Offered

Fully remote across LATAM, around 40 hours a week, flexible for the right person, with a few hours of overlap during U.S. Pacific business hours

What we'd estimate for a role like this: around $2,000 to $4,000 USD a month, based on experience. Tell us the range that fits you and we'll go from there

Paid weekly in USD as a contractor

Up to 20 days of paid time off a year (10 vacation days plus 10 local public holidays)

A two-person design team where you own the flow side and a counterpart owns the visual side, plus a direct line to the Head of Engineering

A team that ships small, steady improvements over big rebuilds, so your work gets built instead of sitting in a backlog

Interview Process

1. Intro call: your background and how you approach workflow and product design
2. Practical exercise: map and simplify a real inspection workflow
3. Portfolio and collaboration deep dive: with the designer you'd partner with
4. Conversation with the Head of Engineering: handoff and how design fits release cycles
5. Final conversation with the CEO: context and next steps

Timeline: most people go from first call to decision in about 2 to 3 weeks.