How to Apply: Send your application to the email address or visit the application link provided on this page to submit your CV and cover letter.
Prove Your dbt and BigQuery Production Chops Before the First Interview
Data and analytics engineering roles at mission-driven organisations attract candidates who can talk about pipelines but freeze when asked to show a dbt model with tests. Food4Education needs someone who has owned the full stack in production, so your application must read like an engineer who has shipped, broken, fixed, and documented real data systems.
1. Lead with production ownership, not tool lists: Your CV should open with the number of production dbt models you have owned, the size of the BigQuery datasets you managed, and the migrations you delivered end to end. Hiring managers for this role will scan for phrases like 'owned dbt and BigQuery in production' and 'delivered data migrations' because the posting explicitly requires at least two years of that. Put those facts in your first three bullet points, not buried under a skills section.
2. Show a metric definition you implemented: Pick one KPI from a past role and describe how you translated a business definition into a dbt model with tests, a KPI dictionary entry, and a certified dataset. The posting asks for someone who can flag definitions that cannot be implemented as written, so mention a time you pushed back on a vague metric and worked with a business owner to close the gap at source. This proves you understand both the engineering and the stakeholder side.
3. Prepare for dimensional modelling questions: Expect deep questions on grain, conformed dimensions, slowly changing dimensions, and star schema design. Be ready to whiteboard a simple star schema for a source system like Google Sheets or an ERP, and explain how you would handle historisation and retention. The role designs a unified BigQuery model for multi-country expansion, so practice explaining how you would keep naming and governance consistent across countries.
4. Bring an orchestration story with failure handling: The posting names Apache Airflow, Dagster, Cloud Composer, and GitHub Actions, and asks for scheduling, dependency management, retries, and alerting. Prepare a specific example of a pipeline failure you diagnosed, how you used retries and backfills, and what you changed to prevent recurrence. Mention your alert response time if you have measured it, because the role targets pipeline uptime above 90% and alerts responded to within four hours.
5. Address data protection head-on: Food4Education handles personal data, and the role requires masking or hashing at the ETL layer plus row- and column-level access control. On your CV or in your cover letter, state which data protection controls you have implemented and how you ensured no model reintroduced personal data. If you have supported access reviews or worked with data protection requirements, name the framework or policy you followed.
6. Demonstrate documentation as a habit: The posting says the post-holder documents as a matter of course and builds systems others can operate. Share a redacted example of a data dictionary, runbook, or lineage document you created, or describe how you trained a BI team on data models and access patterns. Interviewers will probe whether you can hand over your work, so have a story about a system you built that ran without you for a period.
7. Connect to the mission without overclaiming: Food4Education is an NGO focused on school meals, and the data platform supports multi-country expansion and partner technical assistance. Show that you understand why reliable metrics matter for external submissions and finance close, especially if you have supported month-end financial close or reconciled figures where systems disagreed. Avoid generic passion statements; instead, explain how accurate data feeds directly into decisions that affect programme delivery.
8. Prepare for a small-team, full-stack conversation: The role sits in a two-person engineering team where each member leads one discipline and is fully capable in the other. Be ready to discuss how you prioritise when you are the only person available for a pipeline failure, how you review code with one peer, and how you keep CI/CD and version control disciplined in a small team. Mention any experience owning the full data stack, even in a startup or volunteer capacity, because that is exactly the operating model here.