Tech Director is for someone who wants to build real systems that solve real problems. You will not only build projects for practice; you will build tools and workflows that people in Resala actually use.
The Step of System
Tech Director
Builds systems, automations, dashboards, forms, and workflows that make Resala easier to manage.
Can you notice a messy process that everyone accepts as normal and build a simple system that makes people's work easier, clearer, and more reliable?
Choose one messy Resala process and design a practical system for it: users, flow, tools, data, risks, and how people would adopt it.
Role requirements
Read this as a checklist
Leadership requirement
Lead through systems, not only code. Make sure people can use, understand, and continue the tools you build.
Ownership requirement
Watch for repeated manual work, messy data, and unclear workflows. Take initiative to simplify them before people accept the mess as normal.
Skills requirement
- Systems thinking.
- Automation and AI tools.
- Basic understanding of digital tools, APIs, or how systems connect.
- No-code or coding ability.
- Problem-solving.
- Documentation.
- Ability to explain technical ideas simply.
- Initiative to solve problems before being asked.
Preferred experiences or passions
- You enjoy tools, automation, dashboards, forms, or coding.
- You notice broken processes quickly.
- You want proof of work with real users and real impact.
Actual work
What your week-to-week responsibility can include
- 01
Build or improve systems that make Resala's work easier.
- 02
Create automations, forms, dashboards, trackers, or platforms.
- 03
Support recruitment, interviews, volunteers, data, and internal workflows.
- 04
Notice repeated problems and suggest tech-based solutions.
- 05
Document systems so others can use and continue them.
- 06
Help other committees understand how tech can support their work.