The keywords that matter for a software engineer are the ones in the posting you are about to answer, in the order that posting gives them, and not the forty-technology lists a search turns up. A generic list cannot tell you whether this team cares more about Terraform than about TypeScript, and that difference decides what your first three bullets should say.
Where the keywords are in a posting
Engineering postings are unusually structured: a list of responsibilities and a list of requirements, usually separated, often repeating the same technology in both. Read them as two different signals. The requirements list is what the screening step looks for. The responsibilities list is what the hiring manager wants done, and it is where the seniority language lives — "own", "lead", "design", "review", "mentor". A term that appears in both is a term worth a bullet of its own.
Words that repeat
Mark every technology, practice and domain word that appears more than once.…