Jie Chen

I didn’t stay and grow at Amazon for 5 years just because I could write good code. Plenty of smart engineers can do that every single day. Writing clean code was just the entry ticket. What truly set me apart was taking ownership, even when it wasn’t asked. If I was assigned a bug to fix, I could’ve stopped after the code review. But I would follow it to production, sit with support teams, talk to impacted customers, and make sure the bug was truly gone, and people felt the difference. If I was asked to build a new API, I could’ve stopped after passing the unit tests. But I’d stress-test it with real traffic, set up alerting, write docs, and hop on calls with downstream teams to make sure their integration was smooth. If I noticed on-call alerts going off every night, I could’ve shrugged and marked them as “infra issues.” But I dug into root causes, ran post-mortems, and sometimes pulled late nights re-architecting fragile parts, so the next person on call wouldn’t have to lose sleep. If I wrapped up my sprint tasks ahead of schedule, I could’ve clocked out early. But I’d sit with teammates struggling with blockers, offer code reviews, and even pick up “thankless” chores like improving internal tools or onboarding docs. Ownership isn’t about heroics or working 14-hour days. It’s about caring enough to see things through, to fix the root, not just the symptoms. To ask, “What else could go wrong?” and, “How can I make this easier for the next person?” That’s how you get noticed. That’s how you build trust. That’s how you grow. Don’t just be the engineer who writes code. Be the one who owns the outcome, end to end. That’s what really sets you apart.

297

10 Comments

Excited to announce Ray on Anyscale is now available on CoreWeave to further deliver on our multi-cloud support. This gives users access to CoreWeave’s purpose-built AI infrastructure, optimized for distributed AI at scale with low latency, fast startup times, and high performance GPUs. It's a powerful combination for teams building and scaling production AI workloads. Read more from CoreWeave: https://lnkd.in/dN9AjA3s

83

1 Comment

My Interview Experience with Intuit – Senior Software Engineer (Frontend). Hi Everyone, Last year i had the opportunity to interview with Intuit for a Senior Software Engineer (Frontend) role. It was a challenging yet rewarding experience, and I wanted to share my journey The Interview Process Round 1: Phone Screening A mix of JavaScript fundamentals and a coding challenge to implement a polypill for Promise.all(). Round 2: Craft Demonstration I was given a task to build an E-commerce checkout flow in React, focusing on: Product selection from an API, Address,Price calculation with discounts, A single-page experience (no multiple routes), Data persistence across steps. After the demo, I had an in-depth discussion on my design choices, edge cases, and testing Round 3: Technical Interview(45 mins) Covered JavaScript & React concepts, followed by implementing an object comparator function. Round 4: Technical interview(Team member) I don't remember this round this was also around frontend concepts. Round 4: Hiring Manager Discussion(30 mins) Focused on behavioral and managerial aspects—team collaboration, problem-solving approach, and culture fit. Outcome: Got the Offer! Key Takeaways Strong fundamentals matter—JavaScript & React knowledge is crucial. Explain your thought process—it’s not just about writing code but understanding why. Write clean, scalable, and testable code—it makes a difference. Even though I ultimately didn’t join Intuit, I found the overall process well-structured and engaging. The only part that felt excessive was the craft demo, as it required a lot of work and effort just for an interview. I will be sharing more interview experiences that I attended, so stay tuned.   #InterviewExperience #FrontendDevelopment #ReactJS #SoftwareEngineering #CareerGrowth #Hiring #Intuit

322

6 Comments

Some exciting updates are coming to POS UI extensions 🚀 This summer, we introduced new capabilities: Direct API access, Storage API and new targets on the cart line item details screen. I'm excited to preview even more exciting things coming in 2025-10 and beyond. 🎨 Polaris We're lowering the barrier to making great POS UI extensions by bringing Shopify's single UI framework, Polaris, to POS. Write highly-performant, HTML-like code that works with any framework for any app and any extension surface, including Shopify POS. Preview components and examples in the release candidate documentation: https://lnkd.in/gwciA7CT We understand this is a big change if you've previously been writing your UI code with React. Get ready with our upgrade guide: https://lnkd.in/gjQAY-pf 🗺️ Navigation Extensions can present native detail screens. Present product details, product variant details, customer details, order details, and staff details without retail staff leaving your extension and workflow. Documentation: https://lnkd.in/gvmd6etq 🛒 Cart API We're adding support for subscriptions and making tweaks to how we provide your extension with updates from the cart. Documentation: https://lnkd.in/g3FCe-kX 📚 Documentation improvements We have added a new targets overview page that provides a great overview of available targets with improved descriptions and visuals: https://lnkd.in/g6nDZmu8 🛠️ Developer Experience We're making improvements to the developer experience with better in-app extension development tools, better debugging tools, and hot reloading. Keep an eye on upcoming versions of Shopify POS as we'll be rolling out these improvements into January. 🔮 Next-gen developer platform Shopify has launched a new Dev Dashboard, and we've transitioned apps and dev stores from the Partner Dashboard. Make sure to update to the latest version of Shopify's CLI and check out the latest news: https://lnkd.in/gkGvn7Tz

84

8 Comments