Tech Content Lead: Filling CMS and Bug Tracking (500+ positions)

Content Management 500 USD
Job 28 of 33
Comprehensive work on filling the "Real Wellness" application. Transformation of "raw" data from Excel into the structure of a mobile application. QA testing of the admin panel, compiling bug reports, finding technical solutions (workarounds) during system failures.

Full project description:
Product: Application for mindful eating and health (Healthy Alert / Real Wellness). Specificity: Critical importance of data accuracy (allergens, measurements, nutritional values). An error in the numbers is unacceptable.

TASK: Transfer a database of 578 unique recipes and 200 ingredients from unstructured Excel tables into a custom CMS (admin panel) of the application.

COMPLEXITY (Why this is not just "copy-paste"):

Complex data architecture: Each recipe is a multi-level object. It was necessary not just to insert text but to link entities: "Ingredient" + "Weight Measure" (cup/tbsp/grams) + "Processing Type" + "Tags" + "Allergens".

Software instability: The admin panel was in active development (Beta). Saving cards regularly "crashed," and there were validation errors in fields.

High responsibility: This application is about health. Confusing "peanut" (allergen) with "cashew" or "tsp" with "tbsp" means putting the client at risk of a lawsuit.

MY SOLUTION AND PROCESS:

1. Data Management:

Conducted an analysis of the source tables, structured the data for streaming input.

Implemented manual transfer of 578 cards with cross-checking of each field.

Configured the logic of tags (Breakfast, Snack, Vegan, etc.) for the correct functioning of filters in the application.

2. QA & Bug Reporting:

During the work process, acted as a QA tester. Upon discovering bugs (for example, a failure when saving a long description), did not stop working but documented the error.

Prepared professional bug reports in Jira/Task tracker: (Reproduction steps, Screenshots, Logs, Expected result).

Found "workarounds": when the admin panel did not save data directly, I found a way to input them in parts or by editing the element's code to meet the deadline while programmers fixed the bug.

RESULT:

The database is 100% filled and validated (578 recipes).

Developers received detailed error reports, which accelerated bug fixes in the admin panel.

The client received ready-to-release content without delays, despite technical software issues.

Why this is beneficial for the client (My principles):
1. Autonomy in emergencies: If your software "glitches," I do not sit idly by waiting for it to "fix itself." I look for a way to complete the task despite the bugs or provide clear technical instructions to the programmer on how to fix it.

2. Accuracy of "pharmaceutical" level: I understand the difference between just text and data. In working with numbers, prices, recipes, or articles, I use triple verification.

3. Understanding of development: I speak the same language as programmers. My bug reports help them work faster, not irritate them.