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 reStructuredText is
reStructuredText simple tables underline the header with equals signs and align columns with spaces.
Python documentation, Sphinx projects and anything on Read the Docs.
What changes when you convert Markdown to reStructuredText
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.
The equals-sign rule under the header is what tells Sphinx the first row is a header. Without it the table renders as data with no heading.
What carries over from Markdown to reStructuredText
reStructuredText can express everything Markdown holds about a table, so this conversion is about shape rather than loss.
Markdown and reStructuredText can express the same things about a table, so nothing is lost here - only rewritten. A pipe table is one row per line, so a line break inside a cell ends the row early. Grid tables are drawn with borders, and unlike most markup they can hold a cell with several lines in it.
That makes this a change of notation rather than of content: the same values, the same columns, the same order, written with the markers reStructuredText expects instead of the ones Markdown uses.
The identifier 007 comes out of the reStructuredText 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 reStructuredText file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the reStructuredText.