Figma designers wanted across India: build a real Energy Management System (EMS) UI installer + consumer
Mandatory bootcamp in South Goa then fully remote
We're building a production-grade Energy Management System (EMS): a mobile app + web platform that controls and monitors real energy devices in real homes and small businesses.
This is not a pretty UI screens project. It's a high-clarity, high-responsibility product where the UX must be:
- fast for installers (commissioning without support calls),
- simple for end-users (daily use without confusion),
- and safe (misconfigurations blocked unless verified).
If you enjoy designing flows where clarity beats creativity, and where guardrails reduce support tickets, you'll like this.
What we are building (context)
Our EMS ecosystem covers both installer mode and consumer mode, and supports multi-device setups like:
- inverters
- batteries
- smart switches
- meters (P1 / smart meter)
- EV chargers
The UI must handle real-world constraints:
- weak Wi-Fi, Bluetooth pairing issues, retries/timeouts
- wrong device scanned, wrong wiring, wrong upstream protection
- offline states, partial device availability, firmware mismatches
- this is dangerous settings that must be locked behind proof
What you will build in Figma (actual scope)
You will work on flows and screens such as:
- Device onboarding + commissioning
- QR/serial activation
- discovery/pairing
- Wi-Fi/Bluetooth connectivity logic and fallback paths
- commissioning steps that confirm correct installation
- Installer proof gates (guardrails)
- photo upload gates (labels, wiring, upstream protection)
- upstream confirmation and validation steps
- load-line validation logic (prevent incorrect setup)
- Monitoring dashboards
- solar production, battery charge/discharge, grid import/export, loads
- clear charts + clear summaries
- meaningful empty states when data is missing
- Controls
- operating modes, schedules, safety limits
- confirmations, warnings, what this does microcopy
- locked actions where needed
- Alerts, faults, logs, support handover
- faults with actionable guidance (what to check, what to upload)
- logs that support can use (not mystery codes only)
- Multi-device home UX
- device list, grouping, dependencies, and what is controlling what
- permissions and role-based access (installer vs end-user)
- Design system usage
- screens must use shared components/variants
- no one-off UI unless approved and then systemized
Work model (important)
Hiring: anywhere in India
Phase 1 Mandatory bootcamp in South Goa (on-site)
Why bootcamp exists: to create one shared delivery standard so output stays fast, clean, and buildable.
Bootcamp aligns everyone on:
- file structure + page structure
- naming conventions (screens, flows, components, variants)
- versioning rules (no final_final_v7)
- component usage rules + do not rules
- handoff format (interaction notes + acceptance criteria)
- QA checklist (states + edge cases)
Phase 2 Remote (from anywhere in India)
After bootcamp you deliver weekly targets with structured reviews.
Open roles (Figma only) choose one primary track
You can mention a secondary strength, but apply for one main track.
Track A Figma UI/UX Designer (Mobile App) (24 roles)
Mission: Make installers + end-users successful in seconds.
You'll build commissioning flows, safety gates, states, and handoff notes that engineering can implement without guessing.
Track B Figma UI/UX Designer (Web Platform) (12 roles)
Mission: Build portals that complement the app: device lists, alerts, logs, warranties/support views.
Expect table-heavy screens with filters/search and clear information architecture.
Track C Design System / UI Librarian (1 role)
Mission: Make delivery faster by making the system stricter.
Own tokens, components, variants, documentation inside Figma, audits, and cleanup.
Deliverable standard (non-negotiable)
We measure quality by buildability and clarity, not looks nice.
You must deliver:
- clean files, consistent pages, correct naming and structure
- full states: loading / empty / error / offline / disabled / permission denied
- edge cases included (failures, retries, timeouts, wrong device, no data)
- developer-ready handoff:
- interactions and logic notes
- component references (variants)
- acceptance criteria per screen/flow
- no messy components, no random spacing, no untracked changes
Contract / timeline
- 4+ months contract (extendable)
- Start ASAP (rolling start)
- Weekly measurable delivery cadence
- Long-term collaboration possible for strong performers
Portfolio requirement (mandatory)
To apply, your portfolio must show:
- 12 complete flows (not just UI screens)
- good component/system thinking (variants, reuse, consistency)
- real states + error handling
- short explanation of decisions (why the flow prevents confusion/mistakes)
If your portfolio is mostly marketing pages and not flows, this won't match.
Selection process
Portfolio screen 1525 min practical interview short paid trial task (where possible) offer + bootcamp scheduling.
How to apply (copy-paste exactly)
Subject: [Track A/B/C] [Name] [City] [Notice Period] [Monthly Rate INR]
Body:
- Primary track (A/B/C)
- Portfolio link (required)
- Availability date
- Bootcamp in South Goa (yes/no + earliest date)
- Monthly rate in INR (or day/hour rate)
- Tools you use daily (Figma/FigJam)
