UX/UI Designer

• FISCAL features end-to-end - invoice tables, VAT (ƏDV) forms, balance reports, payroll modules, tax-declaration and bank payment UIs
• Data-dense, regulator-facing screens for Azerbaijani accountants and SME owners
• Bilingual interfaces (AZ primary, EN and RUS secondary)
• Mobile-first, WCAG 2.2 AA accessibility floor
• Our stack: React + TypeScript + shadcn/ui + Tailwind + TanStack Query, Geist font, azure primary
• Our internal AI workflow: prompt the design and frontend AI assistants, evaluate their output, and own the final call

Strong design opinions backed by reasoning (not just taste - articulated taste) Native or near-native Azerbaijani (you’ll write production AZ UI copy) Fluent English (team + tech docs) Figma fluency (expert level not required - fundamentals + learnability is enough) A portfolio that shows judgment - 2-3 case studies with problem framing * alternative explorations * final outcome * what you’d do differently. Pretty screenshots without reasoning don’t pass our bar. Care about edge cases - empty states, loading states, error states. Happy-path designers don’t ship at JL Tech. Demonstrated AI-tool usage in your design work (or a strong demonstrable interest if you haven’t yet), * Prior fintech / ERP / accounting / banking product work

• Ability to read code (tsx + Tailwind) - helps you collaborate tightly with the frontend team
• Familiarity with Anthropic’s Claude API or design-system-as-code patterns

• Full-time, indefinite contract
• 3-month probation per AZ Labor Code
• Baku office
• 5% flat PIT - HTP-resident-company benefit (Tax Code Art. 101.7.2). Your take-home is materially better than at non-park employers at the same gross.
• Annual leave: minimum 21 calendar days, possibly augmented per policy
• Compensation: competitive AZ tech-park range for 1-3 year experience, exact number at offer

We’re building FISCAL, the leading fintech / ERP platform in Azerbaijan. We’re 14 people, High-Tech Park residents, flat structure. We don’t optimize for headcount - we optimize for the quality of the people we work with.

The real question: can you argue with AI?

We use AI tools every day. Figma’s AI features. Claude (Claude.ai and Claude Code). Our own internal AI design and engineering assistants. Every layout, every microcopy variant, every component proposal has an AI in the loop.

We need a designer who can argue with what the AI produces.

• When Figma Make hands you a layout, you should be able to say: “The composition works because X, but the spacing is wrong because Y - fix it”
• When Claude proposes microcopy, you should say: “Mine reads better because the AZ tone is more formal here”
• When an AI design assistant returns a component, you should accept the parts that fit and reject the parts that don’t - with a reason

If your relationship with AI is “the AI told me to do this,” you’re not the right fit. If it’s “the AI is the fastest junior on my team - I take what’s useful, push back on the rest, own the result,” you are.