People Eric Weber - Data Scientist
Eric is a passionate data scientist and an inspiration to aspiring and practicing data scientists. He shares his thoughts on LinkedIn and Substack.
Search for a command to run...
Eric is a passionate data scientist and an inspiration to aspiring and practicing data scientists. He shares his thoughts on LinkedIn and Substack.
No comments yet. Be the first to comment.
Pivotree provides services focused on the design, implementation, management, and maintenance of complex ecommerce solutions for large enterprises.
This is a technical hands-on role that is focused on key security technologies used across all of Apple.
Master data is the non-transactional data that uniquely defines your business; core business entities (customer, product), transaction descriptors...

Join a team that is changing millions of lives. Transforming smiles, changing lives At Align Technology, we believe a great smile can transform a person’s life, so we create technology that gives people the confidence to take on whatever’s next....
Senior Business Analyst Apply for this position Salary Benchmark* Location Career Level Industry Visible for Experteer Members Sunnyvale, CA - United States Senior Specialist / Project Manager Minimal-Invasive Surgery and Intervention Company Descrip...
Eric is a passionate data scientist and an inspiration to aspiring and practicing data scientists. Many of his thoughts and advise are 100% applicable in many other areas, including MDM, ERP, CRM and BI.
https://www.linkedin.com/in/eric-weber-060397b7/
You can subscribe to his newsletter at Substack. I like his thoughts on data as a product.
https://ericdataproduct.substack.com/
Here is a example from May 04, 2022 post on LinkedIn
The data space has no shortage of brilliant people. What is harder to find are those people who are truly able to operate within an organization to get things done. Working with and influencing people is hard stuff.
Most of the hard organizational problems aren't purely about data science or machine learning. They are about organizing people and teams around problems that unlock value for the business. That takes persistence, patience and more than technical skill.
Building data products is hard because it isn't just about the building, it is about being a product evangelist and motivating people to behave in new ways around data. Creativity is key here.
In a new space like data product (at least for most companies), there is a lot of ambiguity in the role and outcome. Ambiguity won't go away quickly and someone's ability to work within it is critical to success.
This point is probably more selfish, but I get a lot of energy out of working with those who are unafraid and excited by a tough path forward, full of challenges in user adoption and supporting organizational growth.
Feeling stuck or unsure what comes next in your data career? Focus on engaging people - not developing more technical skills.
Career movement and changes require people, not algorithms. An algorithm can’t tell you what comes next or give you feedback.
Talk to people around you. It’s ready isolating to try to solve your career alone. Others have really good input and stories.
It’s hard to lean on others when you’re struggling. But if you can start with 1 person to confide in, the relief you feel is palpable.
Check out LinkedIn and find some career switchers that show a path you could take. Reach out to them to talk! You’ll be surprised at the response.
Spend time doing reflection. A big change doesn’t happen overnight usually. It’s the accumulation of lots of little habits like reflection.
I can’t wait to see what your next step is. Keep moving forward 😊
The basics in data aren't easy.
Here are 10 fundamentals I think about all the time:
Never thinking you've got it all down. Review the basics.
What are your "basics"?
Ask good questions and improving on them. If you don't define the question clearly, no method or approach has any hope of giving you the results you need, rigorous or not.
Determine the quality of the data (or lack thereof) and get better monthly. Understand your lower and upper bound for quality of results. Decide if rigor is even plausible.
Decide how exact you need to be. If the decision is high leverage, high impact, being relentless about rigor makes sense. If it isn't, decide if more directional estimates are plausible.
Make sure you understand what kind of decision stakeholders need and engage with them about it. Do they need a go/no-go decision, or are they simply trying to learn more?
Make clear how rigorous what you've done is and why it was necessary. Simply saying "we used stats" makes everything the same. Help others understand the limitations of your work.
What else would you advise? Any tips?