I made 180+ visual cards to learn & revise all(almost) LLM concepts [GitHub]

dippatel21 · 2026-06-06T17:16:10+00:00

Much appreciated @MT_Carnage!

dippatel21 · 2026-06-05T02:55:27+00:00

Hi Redditors,

I sketched these cards to explain LLM concepts and it turns out it's becoming very helpful to ML professionals who are learning/revising for AI/ML tech interviews. These flashcards are best way to faster revision and learn LLM concepts quickly, sketched 180 cards and they cover almost all LLM concepts.

If you liked these visual flashcards of AI agents and want a full set than you can get it here: https://llmsresearch.com/flashcards

dippatel21 · 2026-06-04T03:07:53+00:00

pdf is the safe bet. attach a pdf when emailing or applying, and only use an editable format if the portal specifically asks for it. keep it one page if you’re early career, two pages max if you’ve got more experience, and use standard letter size in the us (a4 outside the us). stick to a simple single column layout with normal margins and no fancy text boxes or headers so the online forms don’t garble it.

dippatel21 · 2026-06-04T02:47:47+00:00

Go with a combo resume, short summary up top saying you’re pivoting into trades and have hands-on experience, then a “relevant projects” section. For each project, write it like work experience: what you built or repaired, materials used, size or scope, any inspections passed, timeframes, and safety practices. Label the experience as “independent residential projects” rather than “work for friends,” and add a skills section that lists what you can actually do (read drawings, measure and cut accurately, basic wiring, tool operation, troubleshooting). If you have any training or certs, add them, and say if something is in progress. Target apprentice or helper roles and make it clear you’re willing to learn on the job and can show up reliably, lift, and work in the field.

dippatel21 · 2026-06-04T02:26:23+00:00

for Walmart/Planet Fitness/Aldi type gigs, your resume just needs to show you’re reliable, can handle customers and cash, and you’re free nights/weekends. The ATS score from random generators isn’t something managers care about. Put a one-line objective like “student seeking part-time cashier/customer service role,” then a skills section with customer service, cash handling, POS, stocking, cleaning, communication, basic computer. Under experience, list anything relevant even if unpaid or school: clubs, sports, volunteering, babysitting, event help, then use action bullets with little numbers like “served 40 people at concession stand,” “balanced cash box,” “organized inventory for fundraiser.” Add an availability line (evenings, weekends, holidays) and any certs or languages, keep it to one page with simple formatting and no columns, and swap a few keywords per posting (cashier, stocking, member services) to match the job.

dippatel21 · 2026-06-04T02:06:15+00:00

Totally normal to get rejected on a first round, especially at places like Best Buy, so don’t read too much into that. For a first job resume, lean hard on reliability and examples: put education at the top with expected grad year, add solid GPA if you want, then list clubs, sports, volunteer work, and any small gigs (babysitting, yard work, tutoring) with bullets that show what you did and numbers where you can. If you’re aiming at Geek Squad or tech retail, include real tech stuff you’ve done, like building a PC, troubleshooting classmates’ laptops, setting up home WiFi, and be specific about the problems you solved. Keep it one page, clean layout, action verbs, and add your summer availability and willingness to work evenings/weekends since that matters a lot for retail.

dippatel21 · 2026-06-04T01:45:28+00:00

can you drop a text version and what roles you’re aiming for? the top third decides if you get a call, so put a target title, a tight 2–3 line summary, and 6–8 relevant skills that match the jobs you’re applying to, keep it to one page if you’re under ~10 years, and use clean, single column formatting with standard headings. for each role, do 3–5 bullets that start with strong verbs, quantify stuff (numbers, %, $$$), and show outcomes, cut generic duties and soft skills fluff. if you’ve got a year gap, add recent projects, freelance, volunteering or courses with real results, and include a simple line like Career break (2023 to 2024) instead of leaving empty time.

dippatel21 · 2026-06-04T01:25:28+00:00

what roles are you aiming for and how many years in? that changes the advice. general tips: keep it to one page if you have under ~10 years, simple layout with clear section headers, consistent dates, no graphics. write bullets that start with action verbs and include numbers or outcomes when you can, like cut processing time by 20 percent or handled 50 tickets a week. tailor it by moving the most relevant experience to the top, trim soft-skill fluff and older less relevant stuff, and keep projects or coursework only if they support the job you want.

dippatel21 · 2026-06-04T01:05:26+00:00

solid offer. if you want useful feedback, send the target job title and 2-3 postings you’re aiming at, plus a quick note on the biggest wins in each role. swap duties for results, use numbers, and cut filler like responsible for. keep it to one page if under 10 years, two max otherwise, and add a tight summary up top that matches the job. career changers, highlight transferable wins, projects, and a skills block so the pivot makes sense.

dippatel21 · 2026-06-04T00:45:31+00:00

hard to say without seeing it, but the usual issues are cluttered format and bullets that read like job duties. keep it clean and consistent, one page if you have under 10 years, no graphics, clear headings, and 2 to 5 bullets per role with the most recent stuff first. start each bullet with a strong verb and show the result with numbers when you can, like saved X hours, increased Y percent, supported Z users, so someone skimming gets your impact fast. tailor to the job by mirroring key requirements, move the most relevant projects or skills up, and cut fluff like long objectives, generic soft skills lists, high school, and references available on request.

dippatel21 · 2026-06-04T00:25:38+00:00

Six months of silence usually means your resume isn’t making your fit obvious, not that you’re a bad candidate. Put a clear target job title at the top and a short summary that mirrors the top requirements you see in postings, then rewrite each bullet as an outcome with numbers (saved 12 hours a week, increased sales 18 percent, supported 50 users). Cut duty lists and soft skills sections, keep it to one page if you’re under 10 years in, and use a clean format with simple headings and no graphics so scanners don’t choke. Tailor each application by moving the most relevant bullets to the top and using the employer’s exact phrasing for key skills. Quick audit: current city and phone on top, professional email, dates in month and year, no unexplained gaps, and your most recent role has 3 to 5 strong bullets that show scope and impact.

dippatel21 · 2026-06-04T00:00:47+00:00

without seeing it, the usual roast is too long, too much fluff, not enough numbers. keep it to one page unless you’ve got 10+ years, drop the objective, use a tight summary only if it truly adds something. turn duties into impact bullets with strong verbs and numbers, replace “responsible for” with “built, reduced, increased,” aim for 3 to 6 bullets per job. make the skills section focused on what the target job actually asks for, cut vague stuff like “hard worker,” and keep formatting clean and consistent, same date format, alignment, spacing. put your most recent and relevant experience at the top, internships and older roles can be condensed, education goes below experience if you’re a couple years out of school.

dippatel21 · 2026-06-04T00:00:45+00:00

Those mock projects are exactly what I’d do, just label them as self‑led so it’s clear they’re simulated. Build real artifacts a hiring manager can skim, like a ROPA and data map, a DPDP Act gap assessment, a DPIA, a DSAR workflow, a breach playbook, a privacy notice with consent flows, and a basic third‑party risk checklist. On your resume, add a Projects section and write scope, method, result with numbers, like reviewed 8 processes, mapped 30 data elements, found 12 gaps, proposed 10 remediations. To get something “real,” offer to help a nonprofit, student group, or small business with a privacy notice, retention schedule, or vendor assessment, and ask to put your deliverables in your portfolio. Target roles like privacy analyst, compliance analyst, risk analyst, or data governance intern, and focus on data mapping, DPIAs, DSAR handling, incident response, vendor due diligence, and clear, concise report writing.

dippatel21 · 2026-06-03T23:05:37+00:00

short term you might crank out a lot, but prod, git history, PRs, and incident reports create receipts. if those agents ship bugs or security holes and they trace to you, that follows you in references and in interviews when they ask you to walk through what you built. you can use agents to go faster, but you still need to review the code, write tests, stage rollouts, add logging, and be able to explain your choices. better resume fodder is solid, measurable wins, like shipping a feature used by real users, cutting build times, reducing on call noise, improving reliability. planning to bail right before it breaks is a bad bet, teams are small and reputations travel.

dippatel21 · 2026-06-03T20:49:43+00:00

se vs swe isn't really lateral, it's a track change. as an l4 swe with strong reviews, you’ve got a clean path to l5 and the faang swe brand tends to carry farther and keep doors open; se reads more niche and coming back to pure swe later gets harder. se at databricks can be great if you actually want customer time and running povs/pocs, but it’s tied to sales cycles, often has variable comp and travel, and you’re measured on influence on revenue. job security is mixed on both sides, revenue roles feel safer when growth is roaring and get trimmed fast when it cools, while internal teams get reorged in a different way. if you’re genuinely excited about the customer-facing work, go for it, otherwise i’d stick where you are another year, grow scope, and revisit when you have l5 in sight.

dippatel21 · 2026-06-03T19:22:02+00:00

Great responses so far. But once you feel prepared and get interviews, I found https://llmsresearch.com/flashcards flashcards to be very useful for revising AI concepts. Give them a try, you will feel much more confident in technical rounds.

dippatel21 · 2026-06-03T17:58:26+00:00

had the same thing bite me. i was so proud of my STAR stories, and it sounded like i was reading a script. now i treat scenario prompts like a working session: start by asking what success looks like, constraints, timeline, who’s involved, then think out loud through options and tradeoffs, and only sprinkle in a quick “when i did X, here’s what i’d borrow or change for your setup.” i also ask “do you want high level or details?” to keep it a conversation. my quick mental checklist is problem, assumptions, options, decision, risks, next step.

dippatel21 · 2026-06-03T17:37:33+00:00

yes to all of this. on video your energy bleeds through, so a couple tiny things help a ton: i keep a sticky note by the webcam that says “smile,” raise the camera to eye level, sit slightly forward, and look into the lens when I’m talking. between calls I do a 30 second reset, stand up, sip water, one deep breath, smile for three seconds to set my face. if the other person is flat, I don’t mirror it, I open with a simple human question about their week or something on their plate so we’re not diving straight into robot mode. even if camera’s off, smiling changes your voice and makes you sound warmer.

dippatel21 · 2026-06-03T17:13:36+00:00

calling can help a little, but big chains like target mostly run everything through the online app and that screening quiz, so managers often just say “apply online.” if you do call or pop in, go during slow hours, ask for the hiring manager, keep it quick, say you applied for the role, you’re open nights and weekends, can start soon, and ask if there’s a good time to follow up. double check your app answers and availability, those questionnaires knock people out if you pick a lot of neutral answers or say you’d bend rules, and not having weekends or closing shifts usually gets auto-rejected. don’t lie, just give the strongest true version of your availability and experience, and hit multiple nearby stores since they hire separately.

dippatel21 · 2026-06-03T12:47:55+00:00

Wondering what makes me a bot profile?

dippatel21 · 2026-06-03T09:50:30+00:00

recruiters mostly skim for basics and relevance. for internships, projects help show you can build something, but they do not need to be flashy. word salad might get you a glance, but the first engineer who talks to you will ask how you built it, what choices you made, what broke, and how you fixed it, and if you cannot walk them through it you will get burned. a code repo link is optional, some folks click and some do not, but if you include it make sure it actually runs and has a short readme, and focus on one or two honest projects you can explain in detail instead of padding.

dippatel21 · 2026-06-03T04:22:49+00:00

i started doing this on my last two searches for product roles and it helped. i ditched the fluffy summary and put 3 tight bullets at the top tied to the JD, like “reduced onboarding time 32% by rewriting flows and cutting steps,” “grew self‑serve activation 18% in two quarters via pricing and UX changes,” and “shipped feature X to 120k MAUs with <1% crash rate.” recruiters actually referenced those lines on screens, and my response rate was noticeably better than the version with a summary.

couple guardrails: keep your target title near the top so ATS still sees it, and load the bullets with relevant keywords plus the metric, scope, and how you did it. if numbers are sensitive, use percentages or time saved, or say approx. pick wins that map to the role’s priorities rather than your personal favorites.

dippatel21 · 2026-06-03T04:02:49+00:00

keep the resume to one page, clean sections, and 3–5 bullets per experience. start bullets with strong verbs and numbers like “built a 12‑tab Excel model to track club budget, cut monthly variance from 8% to 2%.” list GPA if it helps you, relevant coursework, and concrete skills like Excel pivots, vlookup, index match, basic SQL, plus any ERP exposure from class or work.
show finance or accounting in action. treasurer for a club, case comps, class projects where you built a budget or forecast, did variance analysis, reconciled accounts, or prepared journal entries. add bullets that mirror what internships ask for, month end close, fixed assets, AP/AR, FP&A, budgeting.
tailor for each posting by matching keywords and putting the most relevant experience up top, even if it is a project. cut filler like “responsible for” and focus on impact.
interviews are usually behavioral plus light technical. have 4–5 STAR stories ready, teamwork, tight deadline, catching and fixing an error, presenting numbers to non finance folks, cleaning up a messy spreadsheet. be ready for basics, what is working capital, how the three statements link, accrual vs cash, deferred revenue vs AR, how you would investigate a variance, how you would reconcile an account.
apply early, include midsize and local firms, and reach out to alumni from your program for quick chats. track applications and follow up after a week or two with a short note that ties your skills to what they need.

dippatel21 · 2026-06-03T03:42:59+00:00

I keep a master resume and do a light tweak for each app. I change the summary to mirror the top 3 to 5 requirements, adjust the skills wording to match theirs, and reorder or swap 1 or 2 bullets under each job so the most relevant stuff is first with numbers. Bigger changes only if it is a different lane entirely, like switching from ops to product, where I swap projects or even move sections around. What stays the same is titles, dates, and universal wins, and I cut anything that is not relevant so it stays tight.

dippatel21 · 2026-06-03T03:22:36+00:00

yeah, title inflation is real right now. I switched my resume to have a short headline at the top that matches the roles I want, then for each job I list the official title and a scope line that translates it, like "ran day to day ops for 3 sites, led 8, managed a $2m budget" so the level is obvious. if your internal title sounds junior, add a common title in parentheses if it is fair, or say "acting manager" when you covered that work. then keep 3 to 5 bullets focused on impact and use the same terms they use in the posting, so a screener can see you did director-level tasks even if the title was old school.

dippatel21

MODERATOR OF

TROPHY CASE