Tech Team 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 Team
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?
No task to prepare. The interview is this committee's own questions and a conversation about the answers you wrote.
Pick your head
This committee has 6 heads — you apply to one
Each head owns a different piece of the work. Read all of them before you decide which one is yours.
The Navigator
Project Lead
Takes full ownership of tech projects, ensures everything is according to the system set in place and makes sure deadlines are met.
The Scout
Solutions Researcher
Evaluates incoming requests and starts researching all possible pros and cons of each possible solution, weighs all solutions and shows it to the committee.
The Builder
Developer
Turns the project plan into working software or systems. Focuses on writing clear, documented code that others can easily understand, and proactively communicates both progress and technical setbacks.
The Verifier
Quality Tester
Tests the built solution strictly against the client's actual success criteria, rather than just checking if it runs. Acts as the final quality checkpoint to ensure the product genuinely solves the problem before delivery.
The Closer
Deployment Specialist
Manages the project handover by delivering the solution, training non-technical clients, and writing clear documentation. Conducts scheduled check-ins to ensure the client is entirely self-sufficient.
The Firefighter
On-Call Responder
Acts as a rapid first responder to fix unexpected breakages in previously deployed systems. Works well under pressure to resolve urgent requests so the rest of the team isn't pulled away from ongoing projects.
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.