How to Research a Company’s Tech Stack Before You Apply

Order of research: blog, then postings, then cases

Job postings list what a team wants. Engineering blogs describe what it actually runs and why. Read the blog first, then use the postings to fill gaps.

This site tracks engineering blogs from 33 companies: 16 in Korea, 8 in the United States, and 9 in Japan. Posts are confirmed for 14 of them. For companies without collected posts, the official blog and conference talks are the starting point.

Check how the stack changed over time

A single snapshot can make an old technology look current. List a company’s posts in date order and mark each technology as adopted, migrated, removed, or only mentioned. A migration story like this one gives you a baseline for everything that comes after it.

A removal is just as informative. If a company dropped a technology, ask why before you assume it still uses it.

Match the blog against job postings

Copy the technology keywords from the posting into a table. For each keyword, record whether the blog shows it as adopted, migrated, removed, or only mentioned. Keywords with no evidence go into a list of questions for the interview. Testing and CI are a good example of a topic that is often mentioned in postings but rarely explained in depth.

Keep a record

Keep one page per company with the post title, the link, the approach, and any scale figure the post gives. Mark items without a scale figure as “scale not stated” so you do not treat them as strong evidence.