Got rejected in a final round because of how I answered "how do you use AI?" What do you actually say to that question?

Some background first. I'm a software engineer from Lahore, Pakistan, with 5+ years of experience, all of it with Australian and US startups. For the last 3 years I was with an Australian startup and things were fine. Then about six months ago they shut down the Lahore office. Their reasoning was that they'd rather train their team in Australia, AI is doing a lot of the work now, and they couldn't train us too. So all of us got laid off. None of us were ready for what the market looks like right now.

In the last six months I've applied to 2,000+ jobs and got around 12-13 interviews. I couldn't convert any of them.

Money-wise I'm okay for now, with some savings and small freelance work.

I've been using this time to learn and build. I pay for two Claude Code subscriptions and one Cursor subscription, and I keep building side projects as if they were startups. I took some courses too. Two things I'm proud of: an open source repo with 1,000+ stars on GitHub and 100k+ downloads a month, and an AI app I put on the Play Store that got 8,000+ downloads in three months with zero marketing. I had to shut the app down because I couldn't keep paying the AI API costs. Recently I also started making Instagram reels. I'm terrible at video editing, so I vibe coded my own editing skills with Claude Code, and honestly they edit my videos more professionally than I ever could. That's the direction I'm trying to keep going in.

Now the reason I'm posting.

A friend referred me to a company here in Lahore, and that's how I got called to their recruitment drive. I spent about a week preparing day and night for it. The technical interview went 10/10, and I answered every single question. The coding test was basic and went well too. The last round was the managerial round with the CEO, the CTO and a manager. The manager has 15+ years in the industry.

He started with a few technical questions and things were going fine. I mentioned my open source repo, 1,000+ stars on GitHub and 100k+ downloads a month.

He asked what my biggest strength is. I said I'm a good learner, especially in tech. Even before AI, whenever something new came out or was trending on GitHub, I'd explore it and try it, and if it helped, I'd keep using it day to day. I told him I still do that, but with AI there's something new every single day, and it's really hard to keep up with the pace.

Then he asked how I use AI.

I told him I have my whole workflow set up: my own skills, my own MCP servers. When I work on a feature or a problem, I first prompt for a plan and ask the AI to ask me 10 questions about it, because that makes it really easy to catch hallucinations. I also gave my video editing tool as an example of how I use AI. I was bad at editing, I hate editing, so I built my own tool with AI and now I edit my own videos. My point was that AI can do a lot right now, and I use it to build things that solve my own problems.

Then he asked: if a person uses AI and has good analytical thinking, can he be a good engineer?

I said yes, he can be a good engineer. That's when I noticed he didn't agree with me. I could tell he wanted to hear something more, but I couldn't figure out what. He asked a few more AI questions after that.

Since I've been vibe coding a lot in the last six months, building fun projects and learning, I ended up talking a lot about that side of things. In my last role I was the one who unofficially got a Cursor subscription first and started doing things with AI before most people around me. Most of my friends weren't using it at that pace. A lot of my code was written by AI and I kept building my own solutions on top, but AI moves so fast that I can't match it either.

Looking back, maybe I should have answered differently. Something like: programming is one thing and AI is another, and a programmer should be able to debug an issue, plan, and review the system design before implementing anything. That's actually what we were doing in my last role six months ago. But AI has changed so much in those six months that I'm not sure what the industry expects anymore.

They rejected me. When I asked for feedback, all they said was "the panel rejected you." That's it.

The reason I'm taking this seriously is that this isn't the first time. I've been asked "how do you use AI?" in screening calls and technical interviews too. So I'm genuinely confused about what the right answer is right now. Is it me? Am I doing something wrong, or am I actually fine and this is just the market?

So my questions:

  1. When someone asks you how you use AI in your day to day work, what do you answer?
  2. For the hiring managers here: what are you actually trying to hear with that question, and what makes you reject someone?
  3. Based on all this, is it me? What am I doing wrong?
  4. Anything else that could help me survive this market. I'm happy to listen, even if it's harsh.

Thanks for reading this far.

reddit.com
u/ustype — 13 days ago
▲ 1 r/VideoEditingTips+1 crossposts

I hated editing my own videos so much that I spent three weeks automating it

Two hours of editing for every twenty minutes of recording. Cutting retakes, timing captions, screenshotting the repo I mentioned so I could show it on screen. Every week.

I finally gave up and built the thing. It's a Claude Code skill: drop raw takes in a folder, ask it to edit, get a finished vertical video back.

The interesting problem wasn't automation, it was taste. Software will happily produce a technically correct edit that any human can tell was made by a machine. So every time I rejected a version I wrote down why, and those notes became the actual product. Forty-ish rules, each one naming the mistake it prevents.

My favourite is the one that cost me a whole evening: a sound effect can play, not clip, and still be completely inaudible, because the loud part of the file falls outside the window you played. Every automated check passed. I just couldn't hear it.

Free and runs locally. https://github.com/ranahaani/i-hate-editing

Would genuinely like feedback from people who make short-form video, especially if you record differently to me.

u/ustype — 1 month ago

Every news-reading agent I built refetched the same articles forever. Here is the memory layer I settled on.

Every agent I built that touched news had the same hole in it. It calls a news source, gets a set of articles, uses them, forgets. Next run it refetches, gets a slightly different set back, and has no idea it already saw two thirds of them. There was never a "what have I already read about this company" and that turned out to be the thing I actually wanted.

So I built the memory layer instead of writing that glue for a fifth time. The design decisions were less obvious than I expected, so here they are in case anyone else is stuck on the same thing.

Dedup is the entire problem. Google News hands back four or five URL variants for one article. Matching on URL fails on all of them. What worked was hashing the normalised title together with the normalised publisher. Note that Reuters and BBC covering the same event stay as two separate rows on purpose. Two outlets carrying a story is information, and collapsing them throws it away. Title normalisation also has to handle unicode apostrophe variants or you get "duplicates" that look identical to a human and different to a hash.

Store the embedding model on every row. Learned this the annoying way. Swap your embedding model six months in and the old vectors are silently in a different space, and retrieval just gets quietly worse with no error anywhere. Now every row carries the model name and dimension, so a mismatch fails loudly instead.

Recency belongs in ranking, not filtering. First version filtered to the last N days, which meant an agent asking about a company could not see the thing from five weeks ago that explained everything happening now. Now similarity gets blended with an exponential decay on age, three day half life. Old but very relevant still surfaces.

Same operations everywhere. ingest, search, timeline, brief, sentiment, stats, all exposed identically through a Python API, a CLI, and an MCP server. The MCP part changed my usage more than any prompt engineering did. Handing Claude a news memory it can query across sessions is a different experience from pasting articles into context every time.

The thing I have not solved: article revisions. Publishers rewrite headlines and bodies within the first hour, and my store keeps whatever version it caught first with no record that anything changed. Someone pointed this out to me last week and I have not found a clean answer for agent memory specifically. If you have handled it, I would like to hear how.

Storage is SQLite plus a vector store, all local. The LLM steps are optional and point at whatever provider you want including Ollama, so the memory itself runs with no keys at all.

It is open source. Putting the link in the comments per rule 3.

reddit.com
u/ustype — 2 months ago
▲ 5 r/madeinpython+1 crossposts

Open-source news-memory tool I built for pulling + persisting ticker news

A while back I posted here when my GNews package crossed 1000+ stars, and a few of you were using it to pull news around tickers. I've since built a persistence and query layer on top of it, and wanted to share that here with a caveat first: this is data plumbing, not alpha. Raw news sentiment is noisy and mostly already priced in. I'm not going to pretend otherwise.

What it actually gives you is threefold. You can pull news for a symbol or company from the Google News graph and get it deduped across the pile of URL variants Google returns for the same article. You can persist it locally in SQLite plus a vector store, so you're building a history instead of re-fetching, and query it semantically or as a timeline. And there's an optional LLM brief/sentiment step that's useful as a feature input or for research context, not as a trade trigger. If you don't want anything leaving your machine, that step runs on local Ollama.

gnews-agent ingest "NVDA" --method get_news
gnews-agent timeline "NVDA" --days 30
gnews-agent sentiment "NVDA" --days 14 --timeline

Fetch, search, and timeline are keyless. MIT, v0.1.0.

If you've tried news features in a model before, I'd honestly like to hear what survived out-of-sample and where a tool like this falls short for your workflow. Repo: https://github.com/ranahaani/gnews-agent. PRs welcome.

u/ustype — 2 months ago
▲ 4 r/Lahore

Looking for a good dermatologist in Lahore for recurring fingertip skin problem

Hi everyone,

25 F here, I've been dealing with a recurring skin problem on my fingertips for around 4 months. I've attached photos. The skin becomes red, dry, flaky/peeling and sometimes cracked. It improves with treatment but then comes back again. previously visited a doctor who prescribed antibiotics and a cream. It improved temporarily, but the problem keeps returning. lalso stopped doing things that I thought might be causing it, such as washing household items and cutting fruits/vegetables, but it hasn't completely recovered. actually had a similar issue last year, which eventually went away, but now it has returned and is lasting much longer. l'm looking for recommendations for a good dermatologist in Lahore, preferably someone experienced with recurring hand/ fingertip eczema, contact dermatitis, or fungal infections.

Thanks.

u/ustype — 2 months ago

I built an MCP server that gives Claude a persistent, searchable news memory (built on GNews, ~106k monthly downloads)

I maintain [GNews](https://github.com/ranahaani/GNews), a Python package for pulling Google News articles. It's up to around 106k downloads a month now. For a while I kept seeing people bolt it onto agents by hand: fetch articles, stuff them in a prompt, repeat on the next call. No memory, no dedup, no citations. So I built the layer that was missing and put it behind MCP. It's called gnews-agent.

Inside Claude it gives you five tools: `search_news`, `get_brief`, `get_sentiment`, `get_timeline`, and `monitor_topic`. It pulls published reporting (Reuters, BBC, AP, TechCrunch, the wider Google News graph), dedups it, embeds it, and keeps it around. So you can ask "what actually changed this week on X" and get a cited answer instead of re-fetching everything each time. There's also a `/gnews` Claude Code skill if you'd rather go that route.

One line to add it:

claude mcp add gnews-agent -- gnews-agent serve --transport stdio

Then something like: "Use gnews-agent to ingest the latest reporting on OpenAI, then give me a cited brief on what changed this week."

The search/ingest/timeline path needs no API key, since GNews itself is free. brief and sentiment call whatever LLM provider you point them at: Anthropic, OpenAI, Groq, Gemini, or a local Ollama model.

It's early, v0.1.0, MIT, with 83 unit and 24 integration tests passing. I'd really like feedback on the tool design, and on the dedup approach in particular, and I'm happy to take PRs.

Repo: https://github.com/ranahaani/gnews-agent

u/ustype — 2 months ago