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 Qlik is
A Qlik load script block using LOAD INLINE, which embeds the data in the script itself.
QlikView and Qlik Sense developers.
What changes when you convert Markdown to Qlik
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.
Suitable for small reference tables. For anything large, load from a file instead.
What carries over from Markdown to Qlik
One property of the Markdown has no home in Qlik, and it is worth knowing which before you convert.
Qlik 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.
Anything visual in the Markdown - weight, alignment, colour, column widths - has no counterpart in Qlik and is dropped. The values are what survives.
The identifier 007 comes out of the Qlik 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 Qlik file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the Qlik.