What Markdown is
A Markdown table is rows of pipe-separated cells with a dashed rule under the header. Alignment is set by placing colons in that rule.
README files, GitHub issues, documentation sites, Obsidian and Notion.
What Firebase is
JSON shaped for a Realtime Database import: an object keyed by record id rather than an array.
Firebase projects.
What changes when you convert Markdown to Firebase
Leading and trailing pipes are optional and both are handled. A pipe the author escaped with a backslash is read as data rather than a column break, which is the usual reason a hand-written table parses one column too wide.
Keys come from the first column. Firebase does not store arrays natively, so a keyed object is the correct shape for an import.
What carries over from Markdown to Firebase
Markdown records 2 things about a table that Firebase has no way to hold.
Firebase wants a type for each column, and Markdown does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.
Firebase has no header row. The column names are repeated as keys on every record instead, which is why the result is bigger on disk than the table it came from.
Anything visual in the Markdown - weight, alignment, colour, column widths - has no counterpart in Firebase and is dropped. The values are what survives.
The identifier 007 comes out of the Firebase as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a Firebase file goes wrong.
The quotes around Jonah "Jo" Pryce are escaped with a backslash in the Firebase.