Joanne Xin

Worth a read. More or less mirrors my experience(s). https://lnkd.in/gvYRSFGC "Our research shows engineers can now work effectively across frontend, backend, databases, and infrastructure—areas where they may have previously lacked expertise—because AI fills in knowledge gaps while humans provide oversight and direction." #anthropic #claude

9

1 Comment

Building a platform like Yelp requires massive scale and speed! 🚀 My latest article unveils a cloud-native blueprint for designing systems handling millions of listings & 350+ queries/sec. Dive deep into the architecture: ✨ Data: Managed PostgreSQL for structured data, innovative sharding strategies. 🔍 Search: PostgreSQL's TSVECTOR/GIN & PostGIS with geohashing for lightning-fast text and precise geospatial queries. Dedicated search engines like Elasticsearch also explored. ⚡Real-time: Event-driven CDC (Kinesis/Kafka) and Serverless (Lambda) for idempotent review aggregation. 📈 Scale: Read replicas, intelligent Redis caching, Microservices, IaC (Terraform/CloudFormation), and robust cloud security. This is a practical guide for engineers architecting resilient, high-performance cloud applications. Ready to unravel the patterns? 👇 https://lnkd.in/gbYyEnVz #SystemDesign #CloudNative #AWS #PostgreSQL #Elasticsearch #Geospatial #Serverless #Microservices #TechRecruiter #SoftwareEngineering

4

🧩 Solving GraphQL Pagination in Matillion Custom Connector using Script Pagination Read it here: https://lnkd.in/gVTRBiEb GraphQL APIs are elegant, until you have to deal with pagination. In this article, I break down how we approached cursor-based pagination inside the Matillion Custom Connector framework, using script pagination to handle complex API responses and dynamic cursors. It covers: - The difference between GraphQL and REST pagination models - How to pass dynamic variables through queries - An example using a real API - How the approach scales across connectors in Matillion's Data Productivity Cloud If you've ever designed or debugged GraphQL integrations, you'll probably relate. Would love to hear how you've handled pagination challenges in your own pipelines 👇 #Matillion #GraphQL #DataEngineering #DataIntegration #CustomConnectors #ETL #API #Pagination #DataProductivity

18

AI is not changing what is valuable to a business, but it is changing your value as a software engineer. The new full stack is product + engineering, not frontend + backend. Full episode: https://lnkd.in/gCdurr4q

11

2 Comments

𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗙𝗔𝗔𝗡𝗚 (𝗟𝟰–𝗟𝟲) System Design interviews at FAANG companies aren’t about drawing boxes; they’re about making the right trade-offs at scale. This curated set of System Design Interview Questions for FAANG focuses on real-world problems interviewers ask for mid to senior-level roles. 𝗪𝗵𝗮𝘁 𝘆𝗼𝘂’𝗹𝗹 𝗽𝗿𝗲𝗽𝗮𝗿𝗲 𝗳𝗼𝗿: Designing scalable, fault-tolerant systems Handling high traffic and large datasets API design and data modeling Caching, sharding, and load balancing Consistency, availability, and reliability trade-offs Monitoring, observability, and failure handling 𝗣𝗲𝗿𝗳𝗲𝗰𝘁 𝗳𝗼𝗿: Engineers targeting FAANG L4–L6 roles Backend / Full-Stack / Frontend engineers Candidates preparing for on-site or virtual system design rounds #SystemDesign #FAANG #SystemDesignInterview #SoftwareEngineering #ScalableSystems

10

2 Comments

You are going to do a System Design interview ? You want to practice ? A fun prompt that I tested with Claude 4 Sonnet and is really interesting: # System Design Interview Simulation Act as a senior system design interviewer at **[COMPANY_NAME]**, a leading **[PRODUCT_TYPE]** company. You are conducting a 45-minute system design interview with a candidate for a **[POSITION_LEVEL]** position. ## Your Role: - Present realistic system design challenges relevant to **[DOMAIN/INDUSTRY]** - Ask clarifying questions about requirements, scale, and constraints - Probe deeper into technical decisions and trade-offs - Provide constructive feedback on architectural choices - Guide the conversation like a real interviewer would - Challenge assumptions and ask follow-up questions ## Interview Structure: 1. Present 3 system design topics (I'll choose one) 2. Start with requirement gathering (5-10 minutes) 3. High-level architecture design (15-20 minutes) 4. Deep dive into specific components (10-15 minutes) 5. Discuss scalability, reliability, and trade-offs (5-10 minutes) ## Your Interviewing Style: - Ask "Why did you choose X over Y?" frequently - Request specific numbers for scale estimates - Challenge me on potential bottlenecks - Ask about failure scenarios and monitoring - Probe about data consistency and security (especially important for **[DOMAIN_SPECIFIC_CONCERNS]**) - Give real-time feedback on my approach ## Possible Topics: Please present 3 system design challenges relevant to **[COMPANY_NAME]**'s domain, such as: - **[TOPIC_1]** - **[TOPIC_2]** - **[TOPIC_3]** ## Company Context: - **Scale:** **[COMPANY_SCALE]** (e.g., "10,000+ customers with varying sizes from 10 to 50,000 employees") - **Key Challenges:** **[DOMAIN_CHALLENGES]** (e.g., "compliance, data privacy, multi-tenant architecture") - **Integrations:** **[INTEGRATION_COMPLEXITY]** (e.g., "500+ third-party apps", "multiple payment providers") ## Evaluation Criteria: Rate my performance on: - Problem decomposition and requirement gathering - System architecture and component design - Scalability and performance considerations - Data modeling and storage decisions - **[DOMAIN_SPECIFIC_CRITERIA]** (e.g., "Security and compliance awareness") - Communication and thought process ## Example Interaction Flow: Interviewer: "Design a system for [SPECIFIC_FEATURE] at [COMPANY_NAME]. We have [SCALE_CONTEXT]." Candidate: "Let me start by understanding the requirements..." Interviewer: "Good approach. What specific questions do you have about [DOMAIN_PROCESS]?" Candidate: "What are the main steps in [PROCESS]? What integrations are needed?" Interviewer: "[TYPICAL_FLOW_DESCRIPTION]. We integrate with [INTEGRATION_DETAILS]. Now, what's your approach to handle this complexity?"

21

3 Comments

The state of California requires OS developers to ask for age verification or be subject to fines in 2027. https://lnkd.in/g_GbYrm6 This is a real blow to open source operating systems. For one thing, we don't want different "signals" per OS. We'd want a standard interface for browsers to query the OS and have it be portable. I don't think this is a reasonable ask for folks like me that do OS development as a hobby. I'm not microsoft or apple. There also seems to be a tie-in to app stores which might also require integration with package managers.

12

1 Comment