Mary Floren

Catching this talk between Lloyd Blankfein and David Solomon. Regardless of the industry, there is a lot to learn from how these leaders define "partnership."

1

🚀 We’re partnering with top software engineers in New York’s early-stage startup scene. Talent is moving fast, but our clients are listening and adapting as engineers face real challenges: Interview fatigue is real. Engineers are burned out from marathon processes, long take-homes, and ghosting feedback. “We don’t get to see the product”. Companies aren’t demoing or explaining the product early on, and it’s a big turn-off. The best candidates want to believe in what they’re building. Show, don’t just tell. Tech rounds are moving up. More companies are front-loading the technical interviews to avoid time wasted later, and it’s working for both sides. Remote is shrinking. We’re seeing a definite tilt back toward onsite or hybrid. Not everyone loves it, but the shift is happening. It’s less about a coding language, more about product. Hiring managers are becoming less rigid about specific stacks, and more focused on alignment with product vision, user impact, and client collaboration. 📩 Reach out for more insights: george.wilson@stottandmay.com #Hiring #SoftwareEngineering #TechRecruiting

22

1 Comment

Today, as I await another $NVDA earnings call, my mind drifted back to a cold night in Philly in 2018. A friend and I were deep in the trenches preparing for FAANG interviews. Back then, if you wanted the NYC tech community to notice you, you lived and breathed Kaggle. Somewhere in downtown Philly, mid-walk, we arrived at a blunt conclusion: “Model koi bhi ho… chalega to sirf AMD aur NVDA pe hi.” (Whatever the model or framework, it ultimately runs on AMD or NVIDIA silicon.) At the time, it wasn’t an investment thesis. It was a systems realization. Frameworks change. Models change. Research trends change. But compute compounds. The real bottleneck wasn’t PyTorch vs TensorFlow. It was silicon. That layer-of-the-stack insight shaped how we thought about technology, and yes, eventually how we chose to put our own skin in the game. Over time, it contributed meaningfully to our financial independence. The biggest opportunities often sit one layer below the hype cycle. #NVDA

19

3 Comments

I brought the heartbeat of New York City to life with this real-time, interactive subway map. Built as a birthday gift for my fiancée, Sarajane Sullivan, the NYC Subway Visualization was designed to help her to feel connected to the city she loves from over a thousand miles away. The map uses nearly 500 LEDs to represent trains as they arrive and depart the stations, lighting up in the correct line colors. The result is a living, breathing visualization of the entire subway network. This project involved several fun technical challenges: ❗Challenge: Processing the MTA’s complex GTFS-RT Protobuf feed on a small device. ✅Solution: A Python server (Flask) handles the parsing, offloading the heavy work from the ESP32. ❗Challenge: Displaying updates instantly without network lag. ✅Solution: Implemented WebSockets for persistent, low-latency communication, a significant improvement over traditional HTTP polling. ❗Challenge: Physically wiring and then digitally mapping nearly 500 individual LEDs to the correct MTA station IDs. ✅Solution: Developed a python script to generate station_map.h file to act as a crucial link between the physical hardware layout and the software, ensuring data for a specific station lights up the correct LED every time. The project, inspired by a MoMA design, is fully open-source. You can find all the code, build instructions, and documentation on my GitHub. Github: https://lnkd.in/eWH2G_7F MoMA: https://lnkd.in/ePCCa_iM

15

1 Comment

With AI being more and more present in the SWE world, I see an alarmingly high number of so-called software developers posting regurgitations of artificially produced content with 0 human oversight, most of which is either incomplete, incorrect or both. I feel that this can be highly detrimental for junior coders, who do not yet have the broad spectrum of knowledge required to make an informed opinion on the matters presented. I do understand that it is up to the consumer to responsibly digest information, but could we not at least partially limit the flow of junk? Take the stackexchange platforms, where there is a downvote option for the answers provided. I can see this as potentially discouraging for individuals who do not aim to share information/enrich others, but instead treat this platform as a ramp for their visibility and only chase exposure. LinkedIn , don't you think that uncontrolled debile content damages the credibility of your platform? Or perhaps you are, indeed, only aiming for quantity? People, what are your thoughts on the flood of dirt you see daily? Can we (or should we) do anything about this?

10

2 Comments

Software engineers fear the AI that will take their job while the real danger I see should be in companies and solution owners themselves. Products that you spent years and tons of dollars for buildng selling it for whatever the number of subscriptions is can now be easily cloned and it costs nothing but the Gen AI subscription and some small resources. I am really curious of how the scene will look like after maybe Q2 of 2026. The development that business owners needs to follow “not to fail in the common nokia example” is now talking days not years like all used before!! #ArtificialIntelligence #GenerativeAI #SaaS #StartupLife #ProductManagement  #SoftwareEngineering #TechTrends #DigitalTransformation  #Innovation #FutureOfWork #Entrepreneurship  

5

2 Comments

45+ LPA for Engineers with Just 1 Year of Experience?! Yes — Coinbase is offering one of the highest-paying remote engineering roles in the industry right now. But getting in? That’s a different game altogether. Here’s a complete breakdown of the Coinbase Software Engineer interview process (and what they actually look for 👇): --- 🔹 Round 1 – Online Assessment (CodeSignal) A 90-minute challenge with 4 medium-level DSA problems. Solve at least 3/4 and you’re likely through. 💡 Tip: Focus on clean logic and efficiency — partial correctness matters. 🔹 Round 2 – Recruiter Screening A short call discussing your experience, tech stack, and role expectations. They also guide you with preparation resources and timelines. 🔹 Round 3 – Technical Interview 1 (Machine Coding + DSA) Build something real. Example: a transaction management system. They test how modular, readable, and extensible your code is — not just syntax. 🔹 Round 4 – Technical Interview 2 (OOP & Execution) Deep dive into OOP design and iterators. Focus: class relationships, clean abstractions, and handling edge cases. 🔹 Round 5 – System Design (HLD) Design a payment processing system. Expect discussions on APIs, data flow, microservices, scalability, and fault tolerance. 🔹 Round 6 – HR / Behavioral Cultural fit and motivation. Sample Qs: What drives you to do your best work? Example of creativity in problem-solving Long-term vision with the company --- 🧠 Coinbase cares more about your clarity of thought, design mindset, and coding discipline — not just perfect syntax. This process is intense — but also one of the best real-world learning experiences in system design, machine coding, and large-scale thinking. --- 🚀 Takeaway: If you’re preparing for top-tier product interviews, study how Coinbase evaluates scalability, design clarity, and engineering depth — that’s where real growth happens. #TechInterviews #Coinbase #SoftwareEngineering #SystemDesign #DSA #CareerGrowth #RemoteJobs #EngineeringExcellence

806

33 Comments