Sridhar

SWE Powered by caffeine and sarcasm.

[Ajeet ( opensox.ai ) @jackedAJ]

how to jobmaxxx.

https://t.co/txvlT0Wvts

[muskan sharma @muskaan___07]

Preparing for DSA interview, do these leetcode problems!

1. Sliding Window: 3, 76, 424, 904
2. Two Pointers: 11, 15, 167, 42
3. Binary Search: 33, 153, 875, 1011
4. Hashing + Prefix: 1, 49, 560, 128
5. Monotonic Stack: 739, 503, 84, 901
6. Heap (Top K): 215, 347, 973, 703
7. Intervals: 56, 435, 57, 252
8. BFS/DFS: 200, 994, 102, 133
9. Trees: 104, 236, 543, 124
10. DP basics: 70, 198, 322, 300

You need to solve 2-3 problems per pattern and that's enought to understand problem solving

[Asmit @coolcoder56]

Interview experience at Zepto for 48 LPA

Round 1

DSA + Problem Solving

Round 2

Low-Level Design + DB Schema + APIs

Both rounds were conducted on BarRaiser. Even though there were only two rounds, the discussions were intense and heavily technical.

Round 1 : DSA & Problem Solving Round

This round was entirely focused on coding. The interviewer clearly mentioned at the beginning that the expectation was: Solve 2 DSA questions within roughly 25 minutes each That immediately created pressure because both correctness and speed mattered heavily. The interviewer was collaborative but also closely evaluated: coding speed, optimization, communication, naming conventions and thought process.

One thing I noticed was that they were not interested in brute-force thinking. They expected optimized solutions almost immediately.

Problem 1 : Minimum Cost For Tickets (Leetcode)

The first problem asked was: Minimum Cost For Tickets This is actually considered a fairly difficult dynamic programming problem, especially under interview pressure.

The problem gives:

> a list of travel days
> ticket costs for:1-day pass
> 7-day pass
> 30-day pass

Example :

Input: days = [1,4,6,7,8,20], costs = [2,7,15]
Output: 11

The goal is: Find the minimum total cost required to cover all travel days. At first glance, the problem can feel confusing because there are multiple overlapping choices at every step. The interviewer mainly wanted to evaluate:
recursive thinking

dynamic programming optimization
state transition understanding

Problem 2 – Daily Temperatures (Leetcode)

The second question was Daily Temperatures. This problem is a classic stack-based problem and comparatively easier once you identify the pattern.

Given an array of temperatures, for every day we need to determine: How many days must pass before a warmer temperature appears If no warmer day exists, return 0 for that position.

Example:

Input:
[73,74,75,71,69,72,76,73]

Output:
[1,1,4,2,1,1,0,0]
The interviewer specifically mentioned that this was a variation of a standard monotonic stack problem.

The brute-force approach would compare every future temperature for every index, leading to O(N²) complexity. Instead, I used a monotonic decreasing stack.

The idea is:

maintain indices in decreasing order of temperatures
whenever a warmer temperature appears, resolve pending indices
This reduces complexity to O(N). I solved this problem in around 10 minutes because I had practiced similar stack problems before.

Round 2 : Low-Level Design + Database Schema + APIs
This round was much more backend engineering focused. The interviewer asked me to: Design a Chess Game

Initially, it sounded simple, but the discussion quickly became deep. The interviewer expected:

class structures
design patterns
APIs
database schema
move validation logic
extensibility discussions
This was not just a UML exercise. The interviewer wanted to understand how I think while designing real systems.

Chess Game LLD Discussion
I started by identifying the major entities: Player, Board, Piece, Move, Game and Position. Then I discussed how inheritance can be used for chess pieces. For example: King, Queen, Bishop, Knight, Rook and Pawn. Can inherit from a base Piece class.

I also discussed: encapsulation, abstraction and polymorphism. during the design.

Design Patterns Discussion
The interviewer specifically asked where design patterns could be useful.

I discussed:

Factory Pattern for piece creation
Strategy Pattern for move validation
Singleton Pattern for game manager (optional discussion)
The interviewer seemed more interested in my reasoning than memorized definitions.

Database Schema Design
The next discussion focused on schema design.

I designed tables for players, games, moves and match history. I also explained relationships between entities and why indexing would matter for querying ongoing games efficiently.

The interviewer asked follow-up questions around:

scalability
storing board state
move history optimization
which made the discussion feel very practical.

API Design
The interviewer then asked me to define APIs.

I designed APIs such as:

Start New Game
POST /games/start
Make Move
POST /games/{id}/move
Fetch Game State
GET /games/{id}
I also explained request payloads, responses, status codes and validation handling.

This part of the interview honestly felt very similar to real backend development discussions.

Overall Experience at Zepto
Technically, the interview process at Zepto was genuinely good. The interviewers were technically strong and the rounds tested:

DSA fundamentals
optimization skills
object-oriented design
backend engineering thinking
API design capability
The main challenge was speed, time pressure and implementation clarity.

[Archie Sengupta @archiexzzz]

i’m in hyd right now, and my bangalore brain can’t comprehend that i traveled 12 km in 30 minutes. in blr, 30 minutes is more like 1 km. the infrastructure is really good.

[Vaidehi @Ai_Vaidehi]

𝟯𝟬 𝗕𝗹𝗼𝗴𝘀 𝘁𝗼 𝗟𝗲𝗮𝗿𝗻 𝟯𝟬 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀:

1. APIs: https://t.co/7fL4F9XGef
2. API Gateways: https://t.co/D4j6P6CYDr
3. JWTs: https://t.co/OKiOvlj8Fq
4. Webhooks: https://t.co/nvgjOsKOas
5. REST vs GraphQL: https://t.co/Kipxik9t7B
6. Load Balancing: https://t.co/34mFEh55xv
7. Proxy vs Reverse Proxy: https://t.co/IDslD2PJcL
8. Scalability: https://t.co/ohmTKQxPZZ
9. Availability: https://t.co/GkquXXNylU
10. SPOF: https://t.co/GQ8WR0E8RP
11. CAP Theorem: https://t.co/5bu4SkN9lJ
12. SQL vs NoSQL: https://t.co/4aMsfVsZbD
13. ACID Transactions: https://t.co/52MERICrzU
14. Database Indexes: https://t.co/BBoa8EMX2r
15. Database Sharding: https://t.co/rZ2ZxQS11P
16. Consistent Hashing: https://t.co/qKWIFOXKql
17. CDC: https://t.co/kBldaWUZzb
18. Caching: https://t.co/lMkqrsputO
19. Caching Strategies: https://t.co/pXru61Cfvr
20. Cache Eviction Policies: https://t.co/EoeeW1FFRy
21. CDN: https://t.co/0PcOUhdNXp
22. Rate Limiting Algorithms: https://t.co/4ocDZggbho
23. Message Queues: https://t.co/FTPz4XpgqG
24. Bloom Filters: https://t.co/ym7I98Aboj
25. Idempotency: https://t.co/itqXVPe4zT
26. Concurrency vs Parallelism: https://t.co/CbjqqzYKIx
27. Long Polling vs WebSockets: https://t.co/L1Tr4MeN5A
28. Stateful vs. Stateless Architecture: https://t.co/0AVkCh9fm1
29. Batch vs Stream Processing: https://t.co/wMWEf8IGFY
30. Geohashing: https://t.co/emPySzIVP8

🔁 Repost to help a friend.
📌 Save this post for later.

[Abhi Varde @varde_abhi]

Going through a tough time. Actively looking for work.

Last 6 months:
→ Merged PRs in @better_auth @appwrite @mintlify @umami_software
→ 150+ GitHub stars, 4K+ npm downloads
→ Shipped 10+ products app

Frontend & Product Engineer. 3+ yrs. Available now.

DM or retweet. 🙏

[Sridhar @Sridhar__05]

@nalinrajput23 1Password Notes.

[Shub @shub0414]

If I had 6 months to become an AI Engineer. I’d do this.

Stage 1 - Python Basics
Syntax, loops, functions, OOP, NumPy, Pandas.
Stage 2 - Math for Al
Linear algebra, statistics, probability, basic calculus.
Stage 3 - Machine Learning
Regression, classification, clustering, metrics (scikit-learn).
Stage 4 - Deep Learning Basics
Neural networks, CNNs, RNNs, training fundamentals (PyTorch/TensorFlow).
Stage 5 - Modern AI (LLMs)
Prompt engineering, embeddings, RAG, fine-tuning small models.
Stage 6 - Build Al Projects
Chatbots, classifiers, NLP apps, image models.
Stage 7 - GenAl Tools
LangChain, HuggingFace, vector databases (FAISS, Pinecone).
Stage 8 - MLOps Essentials
FastAPI/Flask, Docker, GitHub, cloud deployment basics.
Stage 9 - Full Projects
End-to-end ML pipeline, deployed Al apps.
Stage 10 - Portfolio
5-7 polished projects with README + demo videos.
Stage 11 - Job Prep
LeetCode basics, system design basics, ML/Al interviews.
Stage 12 - Apply
Al Engineer, ML Engineer, Data/Al roles, GenAl developer.

[Yoshik @AskYoshik]

If I had 6 months to become a DevOps/SRE Engineer, I'd do this.

Stage 1 - Linux Fundamentals
Shell, processes, file systems, basic networking.

Stage 2 - Scripting
Bash and Python for automation, cron jobs, small utilities.

Stage 3 - Networking Basics
HTTP, DNS, TCP/IP, load balancing, how requests actually move.

Stage 4 - Cloud Basics
Pick one cloud. Compute, storage, IAM, networking.

Stage 5 - Containers
Docker, images, volumes, networking, debugging containers.

Stage 6 - Kubernetes
Pods, deployments, services, ingress, troubleshooting clusters.

Stage 7 - Infrastructure as Code
Terraform basics, state management, reusable modules.

Stage 8 - CI/CD
GitHub Actions or GitLab CI, building reliable pipelines.

Stage 9 - Observability
Logs, metrics, traces, alerting, understanding system behavior.

Stage 10 - System Design Basics
Scaling, caching, queues, retries, handling failures.

Stage 11 - Real Projects
Deploy applications, break them, fix them, handle real traffic.

Stage 12 - Portfolio + Jobs
3–5 solid projects, proper documentation, start applying to DevOps and SRE roles

[Ajeet ( opensox.ai ) @jackedAJ]

this read by @naval has completely changed my perspective on "saturation" and "competition".

there's always a space for you if you're authentic.

10/10 recommended.

[Yoshik @AskYoshik]

Don't overthink it.
- Build a CI/CD pipeline that deploys a simple app
- Build a Dockerized app with proper networking + volumes
- Build a Kubernetes cluster and deploy a real service
- Build a monitoring stack with Prometheus + Grafana
- Build a logging pipeline with ELK / Loki
- Build infra using Terraform (VPC, EC2, DB)
- Build a load-balanced app with autoscaling
- Build a system with cache (Redis) + DB fallback
- Build failure scenarios (kill pods, simulate outages)

The best way to learn DevOps?
Systems. Not tutorials

[Dileep Reddy @DileepReddy125]

Snow falls on the outer ring road, hyderabad.

[anand mahindra @anandmahindra]

Apparently, this is one of the earliest known photographs of the sacred Kedarnath Dham, taken in 1882.

Couldn’t take my eyes off it.

No roads. No railheads. No helicopters.

Just the abode of Lord Shiva, cradled by the Himalayas

Back then, the yatra demanded time, endurance, & faith. The journey wasn’t incidental; it WAS the pilgrimage.

Today, access is easier. And that’s a good thing because it opens the experience to many more.

But perhaps something still needs preserving?

The ability to slow down & savour the experience of traveling.

Because journeys are about who we become along the way.

#SundayWanderer

(Photo courtesy @LostTemple7 )

[Revathi @revathitweets]

There is PR and then there is THIS!

Frustrated for being stalled on the roads for about an hour, Hyderabadis decided to honk so that someone listens to their plight 🙏🏽

Today, in scorching heat, vehicles were stopped at Puppalguda Tollgate, ORR for over an hour because CM was passing.

Angry citizens were seen questioning the police for making citizens’ life miserable for CM’s convoy.

A policeman was seen saying - “you at least sit in cars with ACs on, imagine our state”.

CM Revanth Reddy should probably not devote 12hours of his busy “18 work nonstop working” schedule…attending weddings, birthdays, cradle ceremonies, half saree functions, engagement parties, film events and what not. There should be a rationalization as to how many such events a CM attends.

Also, as he doesn’t live in the official CM residence but in one of the busy Jubilee hills area, every time his convoy hits the streets, people are caused major discomfort.

Remember when he became a CM, there was this whole clamouring around how he is a simple man & this praja paalana?? There were videos and special PR activities about how he asked police to not stop public for his convoys to go.

Reality seldom matches PR histrionics.

A humble request from common citizenry of Telangana, especially Hyderabad, kindly keep in mind the scorching heat and spare us this torture, at least in peak summers 🙏🏽

[Kirill @kirillk_web3]

> be Andrej Karpathy
> builds neural nets before anyone calls them AI
> joins OpenAI. helps train GPT.
> becomes head of AI at Tesla
> teaches the world how LLMs actually work. for free.
> leaves Tesla. starts making YouTube videos
> 1M subscribers. still free.
> posts a casual observation about LLM coding habits
> names 4 problems nobody was talking about
> one developer turns it into a single CLAUDE.md file
> 84,000 stars in days
> zero dependencies. zero cost.
> Karpathy didn't even write the repo
> just told the truth
> the person who understands the problem
> doesn't always need to build the solution
> sometimes one tweet is enough

[Khushi @khushiirl]

everyone cares about user experience,
no one cares about the developer's experience. 💔

[Anand Ranganathan @ARanganathan72]

Live visuals of the ED team on its way to raid Raghav Chadha.

[Sridhar @Sridhar__05]

@rambuilds_ Sell 😅

[Sridhar @Sridhar__05]

@0xPrajwal_ It is a trade off b/w security and resources consumption imo:

Sessions are safer: In the sense that, server has more control + so resource intensive.

JWTs: since they are stateless, they scale well.

a hybrid approach is used in most general use cases - JWTs + Refresh Tokens