Tushar Vaghela @tv1981

Hiring advice for freshers who have been job hunting for 6-12 months. Almost every day, I get 10+ DMs. From friends. Family. Someone's brother. Someone's cousin. All asking the same question: "Can you help me get a fresher role?" And every single time, it hurts to say no. Not because I don't want to help. But because most of the companies I work with are funded startups that are scaling. Most of them don't have the bandwidth to hire and train fresh graduates. So if you've been applying for months without any success, Here's my advice: Take an internship. I know it doesn't sound exciting. You spent four years earning your engineering degree. Your family invested a lot in your education. An internship probably feels like settling. But waiting another six months for the "perfect" full-time role is a much bigger risk. Right now, your priority should be getting your foot in the door. Once you're inside, everything changes. You'll work on real products. You'll learn from experienced engineers. You'll build credibility. And you'll significantly improve your chances of landing a full-time role. Yes, there will always be someone who landed a 35 LPA package straight out of college. That's great. But this advice isn't for the exceptions. It's for the thousands of graduates from Tier 2 and Tier 3 colleges who are still trying to get their first break. Start somewhere. Tech rewards people who keep learning. Your first opportunity won't define your career. It will simply begin it. Start somewhere. If you're a fresher who's still looking for your first role, how long has your job search been? I'd genuinely like to know.

＿＿＿＿＿＿ | We’re hiring | |＿＿＿＿＿＿| \ (•◡•) / \ / —— | | |_ |_ Open roles: → AI Applications Engineer → AI Conversation Designer, Customer Support → CX Knowledge Architect → Customer Success Manager → Software Engineer, AI Workflows → Model Behavior Engineer → Business Operations & Strategy Lead → Data Engineer, People Analytics → Engineering Manager, Mobile AI → Accounts Payable Manager → Lifecycle Marketing Manager → Field Marketing Manager → Startup Program & Experience Lead → Employee Experience Program Manager → Head of Technical Recruiting → Technical Recruiter → Product Designer → Product Manager, Workspaces → Head of GTM Operations → Enterprise Customer Success Manager → Solutions Consultant → Sales Development Representative → Enterprise Sales Leader → Account Executive, Mid-Market → Application Security Engineer, AI Security → User Researcher, AI Evaluations & more.

“You have thousands of moments ahead of you. The important thing isn’t to get them all right; it’s to find a way to keep moving forward.” Sundar Pichai, MS ’95, CEO of Google and Alphabet, addressed the Class of 2026 at Stanford’s 135th Commencement ceremony. Watch the full speech at the link: stanford.io/4e8weWd

So on Everest Day, celebrate the climbers, but also the surveyors, Sherpas, porters, families, and silent believers behind every “solo” win. ❤️🏔️ #EverestDay

1921 explored the northern approaches, 1950-51 made the workable south-side path clear, and on 29 May 1953 Tenzing Norgay and Edmund Hillary made the first confirmed summit. 🙌

Mount Everest is the highest point on Earth. But its greatest lesson may be deeply human: the journey is what stretches our limits, softens our ego, and shows us who we become on the way up. 🏔️✨ #InternationalEverestDay #MountEverest

There’s a very small window right now where tiny teams can build things that look unfair. We’re in that window. Hiring AI Engineers - Mumbai •⁠ ⁠freshers •⁠ ⁠interns If you care about product, speed, and building AI-native experiences instead of AI gimmicks — DM me

I knew someone who always had the next big thing. Every time we met: - New idea. - New plan. - New life blueprint. And honestly? They sounded convincing every single time.

come by if you can! i'll be showing off my brand new personal agent - karinda - and talking about why elixir is the right choice for making agents. luma.com/i30gi72t?local…

A lot of very good engineers secretly feel they’re already behind on AI coding tools. Not because they haven’t tried Claude Code, Cursor, or Codex… but because everywhere they look, there’s some mysterious combo of rules, hooks, skills and “best practices” they’re supposed to know. So everyone does the same thing in isolation: - Rewriting AGENTS.md, CLAUDE.md, .cursor/rules in each repo - Learning the same painful lessons on security, git and testing - And quietly wondering if they’re “using these tools wrong” I wanted to fix a small but real part of that. Over the last days I pulled together a set of opinionated, battle-tested rule files for: - Claude Code → CLAUDE.md - Codex → AGENTS.md - Cursor → .cursor/rules/*.mdc They focus on the stuff that actually changes how your agents behave: 🔒 Clear security boundaries (what the agent must NEVER do) 🧠 Code style that encodes real architectural decisions, not generic lint rules 🧪 Testing philosophy (when not to add tests, and why) 🔀 Git & workflow rules that stop agents from doing surprising repo-wide edits No threads. No PDFs. No “comment Interested to get the link”. The GitHub repo link is in the replies so you can just open → copy → adapt → ship.

1/ Most people “prepare for interviews”. If you’re aiming for top spots like @Rippling , @databricks , @stripe , @nvidia , @Razorpay , @JioHotstar etc, you may need to rebuild yourself for that bar. Here’s the PLAYBOOK for 0–5 YOE folks in India. Save this. 🔖

@sunnykgupta Hello 🙏🏻

Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

Daniel Hnyk @hnykda

3 months ago

LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below

307 2K 9K 5.9M 3K