About Field
At Field, we design and build products to solve difficult health logistics problems in places with poor infrastructure. Our investor-backed health logistics platform, Field Supply, powers the planning and distribution of public health commodities across the continent; and provides the digital infrastructure for our pharmacy supply and financing service, Shelf Life.
Job Summary
We're looking for a Product Designer to join our Supply Chain Tooling pod - the team building practical, operational tools that facility workers and logistics managers use daily to move health products efficiently.
Where you'll spend your time: 80% of your energy will go into UX and workflow design - figuring out the right flows, the right information hierarchy, the right sequence of steps. The remaining 20% is assembling those flows into UI using our existing design system. The hard thinking is in the workflows; the UI should be relatively straightforward because we have strong patterns to build from.
Our design philosophy: We're building good enough tools that work together seamlessly, not expert-level tools that compete with SAP or Oracle. We're pragmatic, not precious. We ship fast, learn quickly, and kill features that don't work.
What makes this unique: You'll be designing for users in rural Nigeria and Kenya - facility workers reporting stock on their phones, logistics managers routing shipments with spotty connectivity. Your designs need to work in the real world: on basic Android phones, with interruptions, for users who might be semi-literate. If it only works on a MacBook with perfect wifi, it doesn't work.
What You'll do
Research & Validation
- Conduct lean user research with facility workers and logistics managers to understand operational pain points
- Prototype and test concepts quickly - we validate in weeks, not months
- Work with the Product Manager to run rapid validation cycles (sketch → prototype → pilot → iterate)
Design Operational Workflows (Your Primary Focus)
- Design the flow and logic of stock reporting, ordering, and transportation workflows - making complex supply chain processes feel simple
- Figure out the right sequence of steps, what information to show when, and what decisions users need to make
- Map out user journeys that account for interruptions, edge cases, and real-world chaos
- Think through error states, validation logic, and "what happens when..." scenarios obsessively
AI-Augmented Design Process
- Use AI tools (Figma AI, Lovable, v0, etc.) to rapidly generate and iterate on UI concepts
- Prototype multiple workflow options quickly to test with users
- Leverage AI to speed up the boring parts so you can focus on the hard thinking about flows and logic
Support-Aware Design
- Design to minimize support tickets
- Build in-app guidance, clear error messages, and validation that prevents user mistakes
- Collaborate with the support team to understand where users get stuck
Design System Contribution
- Work within and evolve Field's design system to accommodate configuration-heavy products
- Document workflow patterns that can be reused across diverse client configurations
- Balance consistency with the flexibility needed for 20+ clients with different workflows
Collaboration
- Work closely with engineers on feasibility and performance constraints
- Partner with the PM to pitch features to clients and gather feedback
- Facilitate lightweight design reviews with cross-functional stakeholders
Some travel to our offices (and out to the field) in Nigeria and Kenya may be required. We are generally flexible with travel arrangements.
Application Requirements
- 4-6 years designing operational software - tools people use to get work done, not browse casually
- Strong UX and workflow design skills - you excel at taking a messy process and making it simple
- Solid visual design skills - you can create clean, functional interfaces, especially when working within a design system
- Strong portfolio showing your process: user flows, journey maps, wireframes, validation work, iterations, and final UI
- Figma proficiency - our primary tool
- Pragmatic mindset - comfortable with "good enough" solutions and ruthless prioritization
- Rapid prototyping skills - you can mock up testable workflows in days, not weeks
- Systems thinking - you can simplify complex operational processes without breaking them
- Willingness to kill your work - you're not precious about designs that don't validate
- Clear communication - you can explain your reasoning and rationale to stakeholders
Bonus Points
- Experience with AI design tools or strong interest in incorporating them into your workflow
- Designing for low-literacy users or challenging usage contexts
- Experience with design systems that support heavy configuration/variation
- B2B SaaS or enterprise software experience
- Understanding of supply chain, logistics, or operational workflows
- Experience designing for emerging markets or low-connectivity environments
- Prototyping tools beyond Figma (Framer, etc.)
- Knowledge of HTML/CSS
- Familiarity with data-driven design and A/B testing
Portfolio Requirements
We want to see 2-3 detailed case studies that show your thinking about flows and user problems, not just polished UI screenshots.
For each project, include:
Project context:
- What problem were you solving? For whom?
- What constraints did you have? (timeline, technical, user, business)
- What was your role on the team?
Your process:
- Show the messy middle: user research findings, user flows, journey maps, wireframes, iterations
- How did you figure out the right workflow? What alternatives did you consider?
- How did you validate your ideas? What feedback did you get?
- How did you collaborate with PMs and engineers?
What you shipped:
- Show the final design (screenshots, links, videos)
- Walk us through the key flows and explain your decisions
- What tradeoffs did you make? What did you intentionally leave out?
Impact & learning:
- How did you measure success? What were the results?
- What did you learn? What would you do differently?
- Bonus: Tell us about something you designed that failed and why