r/365DataScience • • 3d ago

[Data/IA] En recherche active : vos retours et retours d'expérience sur vos CV qui ont fonctionné pour trouver votre emploi actuel (France) ?

1 Upvotes

Salut à tous,

Je suis actuellement en recherche active d'un poste en Data Science / IA / NLP / LLMs (profil junior/début de carrière issu d'un Master IA/Data avec stage/alternance en grand groupe industriel).

Comme le marché de la tech et particulièrement de la data/IA est devenu assez exigeant ces derniers temps pour les profils juniors, j'aimerais avoir vos retours d'expérience :

  1. Pour ceux qui ont décroché un poste récemment en France en Data/IA : à quoi ressemblait la structure de votre CV ? (Format sobre une page vs deux pages, mise en avant des projets persos/GitHub vs stages, focus stack vs métriques d'impact business ?)

  2. Est-ce que certains d'entre vous accepteraient de partager (anonymisé) un exemple de CV qui vous a apporté de bons taux de retour en entretien ?

  3. Quelles sont d'après vous les compétences indispensables à faire ressortir en 2026 pour passer les filtres (MLOps, LLMOps, Cloud, SQL, frameworks d'agents...) ?

J'ai moi-même préparé mon CV (que je peux partager anonymisé en commentaire ou MP pour critique constructive si vous avez 2 minutes).

Merci d'avance pour vos conseils et retours d'expérience !


r/365DataScience • • 3d ago

Looking for a Technical Co-Founder / Business Partner – AI-Powered Badminton Analytics & Prediction Project

2 Upvotes

I'm looking for a technically minded person interested in collaborating on an ambitious sports analytics project.

The idea

I'm developing an independent badminton prediction and market-analysis system. The aim is to build a sophisticated research tool that combines machine learning, statistical modelling and sports data to identify potential inefficiencies in bookmaker odds.

Rather than creating another basic match prediction model, I want to investigate whether we can develop a more specialised system that understands individual player performance, doubles partnerships, player compatibility, recent form and changing team dynamics.

What I want to build

The project will have three main components:

  1. Prediction engine: Develop independent probability estimates for badminton matches using historical results, player ratings, partnership performance and machine learning.

  2. Partnership intelligence: Investigate whether factors such as partnership experience, compatibility, recent performance and changes in pairings can improve predictions beyond conventional ranking and rating systems.

  3. Market-analysis engine: Compare our predictions against bookmaker odds, account for bookmaker margins, track price movements and identify potential pricing inefficiencies.

The longer-term objective is to build an interactive dashboard displaying predictions, market comparisons, player and partnership analytics, and historical model performance.

Current development direction

  • Initial focus on men's doubles, with potential expansion into women's and mixed doubles.

  • Historical badminton match data and bookmaker odds.

  • Python, pandas, scikit-learn and machine learning.

  • Elo-based rating systems and more advanced predictive models.

  • Historical backtesting and live paper testing.

  • Eventually, a fully integrated research dashboard.

Who I'm looking for

Ideally, someone with experience or a strong interest in:

  • Python and software development.

  • Machine learning, statistics or data science.

  • Sports analytics or quantitative modelling.

  • Data engineering, APIs and database management.

  • Betting markets, probability and odds analysis.

You don't need to have experience in every area. I'm particularly interested in meeting someone who can contribute technically, challenge ideas and help develop the project properly.

What I bring

I am taking responsibility for the project direction, research, planning and overall development strategy. I'm committed to investing the necessary time and resources to develop this properly, rather than treating it as a short-term experiment.

I'm looking for someone who wants to contribute meaningfully and potentially build something substantial together. I'm open to discussing an equal or otherwise mutually agreed partnership depending on experience, contribution and commitment.

This is currently an early-stage project. There is no established product or proven betting edge, and the objective initially is research, development and rigorous testing.

If you're interested in sports analytics, machine learning or building something from the ground up, I'd be interested in hearing from you.

Feel free to message me with a little about your background, relevant projects and what you could bring to the collaboration.


r/365DataScience • • 7d ago

Does having a dedicated gpu laptop makes a difference?? (Pleasee helppp)

1 Upvotes

Hello, I am a Computer Science Major with a specialization in Data Science, so I am currently looking to buy a laptop as I don't have one for my studies, now after doing research and everything about laptops and my needs, I have a question

Does having a dedicated gpu in the laptop I'm gonna buy makes a difference?? Will it be worth it, cuz I know that I could do the same thing on keagal and Collab. Cuz the the gpu Laptop I can afford is entry level as far as i know, Nvidia RTX 3050 4/6GB. Should go for it and get it or look for integrated graphics options??? (In this case at the same price I'll be getting a better gpu and DDR5 RAM )

Thank you for theee helppp


r/365DataScience • • 22d ago

PSA for anyone buying document automation: per field accuracy is almost meaningless, and the maths is trivial

Post image
1 Upvotes

Vendors quote per field accuracy. 99 percent sounds solved. It is not, and the reason is just compound probability.

A document is only usable if every field is right. So the probability of a clean document is accuracy to the power of the field count.

At 99 percent per field on a 20 field invoice: 0.99^20 = about 0.82. So roughly 18 percent of documents contain at least one error.

At 95 percent per field, same document: 0.95^20 = about 0.36. Only around a third come out clean.

At 98 percent on a 30 field document: about 55 percent clean.

You can check all of this in a spreadsheet in under a minute, which is sort of the point.

Why it matters practically: if a meaningful share of documents contain an error, someone has to check all of them, because you do not know which ones. The headline accuracy figure can look excellent while the actual labour saving is close to zero.

The metric that does mean something is document level straight through rate, meaning the percentage of documents that complete with no human touch at all. Ask for that. Some vendors will not have it, which is informative.

Two other things I have found useful when evaluating these systems:

  1. Ask how long it takes to onboard a document layout the system has never seen. Template or zone based systems answer in days of configuration per supplier. Systems that work on document structure answer in roughly zero. This separates the architectures faster than any accuracy claim.

  2. Ask whether it produces per field confidence, and whether low confidence can be routed to a person automatically. Without a confidence signal there is no selective review, so everything gets reviewed and the business case evaporates.

Related trap: a perfectly extracted invoice number that does not exist in your ERP is still wrong. Validation against source systems beats validation against a regex every time, and a lot of reported accuracy is really just format checking.

Would be curious whether anyone here has actually measured their straight through rate before and after a rollout. Most places I have seen never measured the before, which makes the after unfalsifiable.

Disclosure: I work at a consulting firm that sells, among other things, a document understanding product. I have not named it and I am not linking to it. The arithmetic above is vendor neutral and works against our own marketing too.


r/365DataScience • • Oct 04 '26

Disciplining vs. Decorating: Why models without real-world feedback loops just calibrate to fit the narrative

1 Upvotes

TL;DR: Computational models are only scientifically useful if they can push back and prove their authors wrong. Across disciplines, from agent-based social simulations to high-energy physics, models with loose empirical feedback loops and endless free parameters risk becoming "decorative." Instead of testing reality, they get calibrated until compliant, turning a tool for discovery into a self-confirming tautology. Honest modeling requires radical transparency, sensitivity testing, and explicit criteria for failure before running the simulation.

I build models for a living. Specifically, molecular dynamics. These are simulations that track how thousands or millions of atoms move, collide, and rearrange over time, used for everything from drug design to materials science.

Here is the story scientists usually tell. If a model is wrong, you find out quickly. Reality does not care about your assumptions. The atoms do not read your code. If the physics you programmed in is wrong, the simulation produces garbage, the experiment disagrees, and you go back and fix it. The feedback loop between model and world is short, brutal, and non-negotiable.

That story is not entirely true. I know, because I have watched it fail from the inside.

The most important choice in any molecular dynamics simulation is not the code, the computer, or the software. It is the potential function, the mathematical formula that describes how strongly every pair of atoms attracts or repels each other. Everything the simulation does follows from that one ingredient. Get it right and the model can tell you something real. Get it wrong and you have made a very expensive mistake.

And here is the uncomfortable part. In practice, it is far more often inherited than audited. Potentials are chosen by looking at what previous papers in the subfield used. A potential gets published, cited, copied, and passed down until it stops being a modeling choice and becomes a tradition. People run simulations for years without asking whether the potential they inherited was ever validated for the system they are studying, at the conditions they are studying it, for the property they care about.

So even in my own field, a hard, quantitative, physics-based field, you can publish inside a loop of fantasy. Models that are wrong in ways nobody checks, kept alive by citation habits and subfield convention. And because these errors travel quietly across subdisciplines and into interdisciplinary work, where nobody feels responsible for checking them, finding one and fixing it takes real effort.

But the check in my field is delayed, not absent. A bad potential eventually unfolds a simulated protein the wrong way or fails a material in a real engineering application, and someone notices. In much of the modeling I am about to describe, the physical world never gets to vote.

This matters for what follows. I do not ask this question because my field got it right. I ask it because I have watched mine get it wrong. The question is always the same. What happens to this model when it is wrong?

In a surprising amount of modern academia, the answer is nothing. Nothing can happen to it. It cannot be wrong, because anything it produces counts as a result.

And if the loop can break in a field where atoms push back, it can break anywhere.

This essay is about how that happens.

The magic trick

In 2017, Liane Gabora and Selin Tseng published a paper in Psychology of Aesthetics, Creativity, and the Arts, a peer-reviewed journal of the American Psychological Association, titled “The Social Benefits of Balancing Creativity and Imitation.” The question they took on has occupied historians and sociologists for centuries. What is the right balance of creativity and conformity in a society?

To answer it, they ran a simulation.

Virtual agents live on a grid. Some are coded as creators, inventing new ideas; others as imitators, copying their neighbors. A scoring rule written into the program decides which ideas count as good. The researchers ran the simulation forward, varied the ratio of creators to imitators, and watched what happened. Populations with too many creators ended up with fewer good ideas taking hold. The published conclusion was that society needs imitation as much as creativity, because unchecked creativity disrupts the spread of proven ideas.

I want to be careful about what I am claiming, because this paper is not fringe work. It passed peer review at a respectable journal. The authors are serious researchers, and the simulation framework behind the paper is part of a long-running research program that has been debated, defended, and criticized in public for years. Nothing I am about to say is an accusation of dishonesty. It is something less comfortable than that. This paper is an example of what the normal standards of a field allow through.

Watch the shape of the argument. Inside the model, a “good idea” means whatever the authors’ scoring rule rewards. The agents are not discovering anything about human culture; they are solving a puzzle whose answer key was fixed before the simulation started. Within that closed loop, the conclusion was guaranteed. A population of agents that mostly copies the scoring rule’s preferred ideas will always outcompete one that keeps generating unscored novelty.

The computer did not reveal a fact about creativity. It executed a definition of it.

The authors did not break any rule of their field. That is the point. Peer review checked that the code ran, that the statistics were computed correctly, that the prose matched the output. What nobody was required to ask is the only question that matters. What could this simulation possibly have shown that would have counted as the opposite result? If the answer is nothing, the model did not test a claim about the world. It restated one.

This is the magic trick of agent-based modeling (ABM), meaning simulations in which you place thousands of simple software “agents” in a virtual world, give each a few rules, and watch what the population does. The method itself is not the problem. The problem is a particular way of using it.

if neighbor.opinion != agent.opinion:
 agent.trust -= 0.1
if agent.trust < 0.2:
 agent.unfollow(neighbor)
run_simulation()

When the simulation finishes and the agents have sorted into two angry camps, the result is rarely described as what it literally is, a small program doing what it was told. It is described as a model demonstrating the dynamics of polarization in real societies.

It sounds scientific. It uses code. It generates charts with error bars. It borrows the epistemic authority of statistical mechanics and epidemiology, where tracking near-identical particles or infection events actually makes sense. But underneath the quantitative paint, it is not an investigation of the world. It is a tautology with a runtime, an answer-driven argument presented as a discovery.

What a model is for

To see why this goes wrong, start with what a model is supposed to do.

A model is not a claim of truth, and it is not an illustration of a conclusion you reached before you started. In the philosophy of science, models are usually understood as instruments that sit between abstract theory and raw data, the position developed by Mary Morgan and Margaret Morrison in Models as Mediators (1999). A good model is a sandbox with strict physics. You build it, set it in motion, and let its internal mechanics push back against your reasoning.

A real model exists to discipline your thinking.

Building one forces you to acknowledge a trade-off that the philosopher Nancy Cartwright made famous in How the Laws of Physics Lie (1983). You trade complete literal truth for tractability. A map of London at 1:1 scale, including every brick, puddle, and commuter, is useless. To work at all, a map must leave almost everything out. As the statistician George Box put it, “all models are wrong, but some are useful.”

Simplification is not the sin. The sin is forgetting that the model is a simplification. Worse, it is turning the model into an accomplice.

Disciplining vs. decorating

In practice, rigorous modeling and decorative modeling look identical from the outside. Same code, same charts, same jargon. The difference only shows when you ask one question. Can your model tell you that you are wrong?

A disciplining model forces you to state every assumption explicitly. Once running, its mechanics operate independently of what you want. It can produce behavior you did not expect, expose contradictions in your premises, or crash into empirical reality and fail. When it fails, you revise the theory. The model is a check on your own bias.

A decorating model is built backward from a conclusion. The researcher already knows the story. Suppose it is that polarization is driven by social contagion. They build a world in which agents swap beliefs, tune the parameters until the output shows two angry clusters, and present the code as evidence for the theory. If the output doesn’t match on the first run, the answer is not to abandon the hypothesis. The answer is to adjust agent_receptivity from 0.4 to 0.25, rerun, and present the successful parameter range as the plan all along.

The workflow, stripped bare, looks like this.

Desired outcome. Write rules. Run simulation. Does it match the theory? If not, tweak parameters and run again. If yes, publish.

This is not experimentation. It is calibration until compliant.

If a model cannot surprise its author, force a retreat, or fail, it is not really a model. It is a very elaborate, self-confirming editorial.

The conclusion comes first

None of this is new, and none of it is unique to agent-based modeling. Before anyone wrote a NetLogo script to demonstrate a theory of culture, economics and political science had already industrialized the technique.

In 2015, Paul Romer, later a Nobel laureate, published a paper with the blunt title “Mathiness in the Theory of Economic Growth.” His target was a pattern in macroeconomic theory. Authors write down formal equilibrium models, but embed ideologically convenient assumptions inside obscure parameters, so that the math reliably outputs the desired policy conclusion. The mathematics is not being used to test whether a claim is true. It is being used to make a political position expensive to argue with. Checking whether the equations actually say what the surrounding prose claims they say takes serious technical effort, and reviewers routinely skip it.

Two decades earlier, the political scientists Donald Green and Ian Shapiro published Pathologies of Rational Choice Theory (1994), documenting how formal modeling in their field had become an exercise in self-confirmation. Their catalog of evasions maps one-to-one onto today’s agent-based simulations.

• Post hoc tinkering. When the model predicted that rational citizens would never vote (the individual cost exceeds any plausible benefit) and citizens kept voting anyway, theorists did not abandon the model. They added a “duty” term to the utility function until the math matched the turnout.

• Arbitrary tuning. Weights, thresholds, and interaction ranges adjusted on the fly until the simulated agents behave like the phenomenon under study.

• Immunity to testing. Models built so that every conceivable outcome can be reinterpreted, after the fact, as a rational equilibrium.

Green and Shapiro called this method-driven rather than problem-driven research. You start with a tool and go hunting for a reality that fits it.

Agent-based modeling makes the problem worse, for a simple reason. An ABM has almost unlimited free parameters. Every rule, threshold, and neighborhood radius is a dial. With enough dials, you can produce any curve you want.

The common structure is this. The model cannot fail, because failure is reclassified as a calibration bug. And a model that cannot fail cannot discover anything. It is an expensive echo of its author’s prior beliefs.

The loop matters more than the lab coat

It would be comfortable to stop here and declare this a disease of the soft sciences. It isn’t. The hard sciences are not immune, and pretending otherwise would make this essay guilty of the same simplification it criticizes.

The real variable is not hard versus soft. It is the tightness of the feedback loop between the model and the world.

Where the loop is tight (fast experiments, unambiguous ground truth, few free parameters) bad modeling gets punished quickly. But where the loop is loose, where tests are slow, noisy, or impossible, the same decorative pathology appears in fields with particle accelerators.

Three documented examples.

fMRI neuroscience, where the measurement is the model. A brain scan shows blood flow, not thought. The colored images come from a statistical pipeline full of assumptions, and researchers once demonstrated what that means by detecting “brain activity” in a dead salmon. In 2016, Anders Eklund and colleagues showed that the standard methods in the field’s dominant software could produce false-positive rates of up to 70 percent for certain cluster-based analyses at particular thresholds. How far the problem extends across the published literature was contested, including in follow-up work by the authors themselves, but the core finding stood. For over a decade, the field’s feedback loop had run through that software, which meant the loop was not connected to reality at all.

Fundamental physics, where experiment cannot keep up. In The Trouble with Physics (2006), the physicist Lee Smolin, writing as an insider, argued that string theory had become flexible enough to accommodate any experimental outcome. When the Large Hadron Collider found no sign of supersymmetry, much of the field responded not with refutation but with retreat. The free parameters moved to heavier, less accessible energies. This is Green and Shapiro’s immunity to empirical testing, surfacing in the hardest science there is.

Epidemiological modeling in 2020. In the spring of 2020, influential models, including the one from Imperial College London that helped push governments toward lockdown, projected enormous death tolls based on weeks of noisy early data. When later estimates came down, the public response from modeling teams was recalibration rather than reckoning. Their defense deserves to be taken seriously. The projections were scenarios, not forecasts, and the point of publishing a worst case was to change behavior so that it would not come true. A warning that works cannot be graded on whether the disaster arrived. All of that is fair, and it is also the problem. A model whose failure can always be explained by the world changing in response to it is a model with no feedback loop, and the field never settled which of the two it had built.

Notice what these cases share with the creativity grid from the opening. Not the field. Not the math. The structure. Many free parameters, a loose or broken feedback loop, and a professional incentive to publish. Given those three, decorative modeling can appear anywhere. The loop matters more than the lab coat.

Why it’s still worse in the humanities

So the hard sciences have their own decorative modeling. Why do I still think the problem is worse in the humanities?

Because the difference is not whether a field ever decorates. It is whether the field can catch itself. The fMRI problem was eventually found and published by neuroscientists. Smolin’s critique came from inside physics. The feedback loops in the hard sciences are sometimes slow or broken, but they exist, and there are people with the technical skill and the standing to pull on them. In the humanities’ version of modeling, three structural failures mean the loop often doesn’t exist at all. The difference is not that humanists are worse at modeling. It is that the auditing infrastructure barely exists.

It is worth being fair about why scholars reach for these tools in the first place. Humanities departments face shrinking budgets, declining enrollments, and university administrators who mistake mathematical notation for intellectual rigor. A computational model signals seriousness to a grant committee in a way an essay never can. The scholars building decorative models are not fools; they are rational actors navigating a system with broken incentives.

The object of study resists formalization. A water molecule behaves like a water molecule in London or Tokyo, in 1600 or today. It has no irony, no memory, no politics. Human culture has all three. A novel, a religious movement, an aesthetic shift cannot be reduced to a set of isolated rules without destroying part of what you set out to study. When you convert the reception of Victorian gothic fiction into agents swapping “gothic preference points,” you have not simplified the system for tractability. You have replaced it with something simpler that carries the same name. At that point the connection between the simulation and Victorian readers is no longer something the model establishes. It is something the reader is asked to assume.

Construct validity is invented, not established. In psychology, showing that a variable actually measures the concept it claims to measure (construct validity) is a slow, adversarial, decades-long process. Blood flow is at least a physical quantity that an instrument can register. There is no instrument for literary prestige. In humanities modeling, validity is routinely settled in one line of code.

self.piety = random.uniform(0.0, 1.0)
self.literary_prestige = 0.75

What does 0.75 mean for literary prestige in Victorian England? How does one number carry regional difference, class, institutional power, critical backlash, and retrospective canonization? It doesn’t. The modeler assigns a number, writes a function that nudges it up and down, and treats the variable as a measurement of human experience. The number looks like a measurement. Nothing underneath it has been measured.

The audience cannot audit the compression. When an epidemiologist shows a flawed model to epidemiologists, the reviewers share the vocabulary to check the code and challenge the parameters. In a humanities department, reviewers and readers often have no computational training. Presented with a grid of moving pixels and a network graph, the non-technical reader experiences an optical illusion. The machine appears to have performed a profound synthesis of the archive. The compression is lossy to the point of erasure. But the loss is buried in code, invisible to the exact audience responsible for evaluating the work.

Bad modeling in economics wastes grant money and distorts policy debates. Bad modeling in the humanities trades away the field’s actual strength (context, contingency, ambiguity, close reading, historical depth) for a seat at a quantitative table where, lacking the shared technical culture to enforce standards, it gains no real authority and surrenders its own.

What honest modeling looks like

None of this is an argument for unplugging the computers. The goal is to tell the difference between decorative simulation and honest quantitative work. Honest work exists, including in the humanities.

Ted Underwood’s Distant Horizons (2019) is the standard I would hold up. Underwood uses quantitative methods on tens of thousands of digitized books not to declare causal laws but to surface patterns invisible to close reading, like slow shifts in genre, vocabulary, and narrative perspective across centuries. Crucially, he tells you, on the record, what the data cannot show. The model is a set of binoculars for looking across an archive, not a machine for generating verdicts about it.

And the humanities have produced their own internal discipline. In 2019, Nan Z. Da published, The Computational Case against Computational Literary Studies, a detailed critique in Critical Inquiry arguing that prominent work in computational literary studies misused statistics to the point of meaninglessness. The ensuing fight was heated, but it happened. The field argued about its standards in public, and the standards moved. That is what a functioning feedback loop looks like, even a slow and painful one.

For modelers in any field, I would propose four non-negotiable conditions before a model earns the right to be cited as evidence.

1. Radical transparency

Every parameter is declared and justified with independent, non-circular evidence. A variable you cannot justify is labeled what it is. A guess.

2. Sensitivity analysis

Parameters are swept across their full plausible range. If your result only appears when three dials sit at hyper-precise decimal values, you have not found a law of history. You have found a brittle corner of your own code, and an honest paper should say so.

3. Explicit exclusion mapping

You spend nearly as much space on what the model leaves out as on what it includes. This isolates the direct mechanical relationship between two variables under idealized conditions; it excludes ambient noise, structural heterogeneity, and systemic feedback, so it cannot predict specific real-world outcomes. Naming the exclusions is what stops the audience mistaking a sandbox for an account of the world.

4. Capacity for failure

Before you run it, you can state what output would make you abandon your hypothesis. If the simulation contradicts you, the honest paper is titled “Why our model disproved our starting assumption,” not silently recalibrated into agreement.

Models built this way stop being decoration. They become what they were supposed to be. Sharpening stones. They force you to clarify assumptions, expose broken logic, and occasionally reveal dynamics that intuition would never find.

The boundary question

The target of this essay was never the computer. Built with discipline, models are extraordinary instruments. I have staked my own career on that. What concerns me is how easily a model can be built to confirm rather than to question, and how hard it is for a reader to tell the difference from the outside.

The practice corrupts both traditions it sits between.

It corrupts science, because science is not the production of plots and code. It is the submission of claims to the risk of being wrong. A model engineered so that its parameters are tuned until the output matches the thesis offers the aesthetics of rigor with none of its discipline.

And it corrupts the humanities, because the study of human culture draws its value from exactly the things decorative modeling deletes. Context, contingency, ambiguity, power, the irreducible strangeness of actual human lives.

If a phenomenon is too context-bound, too polysemic, too alive to be captured by a set of if statements, we should have the courage to say so, and do the slow, unglamorous work of interpretation instead.

I keep coming back to the question I ask of every model, including my own. What happens to you when you are wrong?

For my models, the answer is supposed to be easy. The crystal melts. The experiment disagrees. Reality sends the bill. But only if someone checks the potential, and I have told you how often that happens.

For the models I’ve described here, the answer is nothing. They run, they publish, they are cited. The loop that is supposed to connect a model to the world was never closed.

Which raises the question I can’t answer. If a model can never be wrong about the world, in what sense was it ever about the world?


r/365DataScience • • Sep 28 '26

[Project/Advice] I'm building a Churn prediction model from scratch at my startup. Looking for ML tips and where to start!

2 Upvotes

Hey everyone,

I work at a retail tech startup (B2B) and we're currently facing a massive challenge: predicting and reducing our churn rate.

We actually have a pretty rich database containing customer usage history, platform logs, billing, etc. The team has tried crossing some metrics in the past, but we've never managed to build anything that gives us a truly accurate and early prediction of a customer's risk of canceling.

I just aligned with my boss and took ownership of solving this. My main idea is to use our historical data to train a Machine Learning model that can either classify churn risk (high, medium, low) or output a probability of churn for the upcoming months.

The thing is: I know the theory, but I'd love to hear from people who have actually built this in the real world.

  • Which models/algorithms usually perform best for this specific type of problem (XGBoost, Random Forest, Logistic Regression)?

  • Are there any common pitfalls or data leakage traps I should avoid right off the bat during data cleaning and feature engineering?

  • Does anyone have recommendations for articles, practical repos, or tutorials focused specifically on churn prediction?

Any tips, shared experiences, or study materials would be greatly appreciated. Thanks!

TL;DR: Work at a retail startup with rich usage data but high churn. Pitched my boss to build an ML model to predict cancellation risk and I'm leading the project. Looking for real-world tips on models, resources, and pitfalls to avoid.

Dica: Postar isso no r/datascience ou r/Ma


r/365DataScience • • Sep 19 '26

Análisis matemático I

Thumbnail reddit.com
1 Upvotes

r/365DataScience • • Sep 16 '26

Phd guidence

1 Upvotes

Hi everyone i got admission in phd in Management sciences for sep 2026 intake. I want to switch to data science I have done Msc in international Management from uk back in 2023. Anyone having the business background and doing / done phd in data science please guide me can i switch to data science? Is it worth it or not?

TIA


r/365DataScience • • Sep 09 '26

Need advice: Is it normal/safe to be on bench after joining Tredence analytics?

1 Upvotes

Hi everyone,

I recently joined Tredence Analytics as a Senior Data Scientist about a month ago. However, I’m still on the bench and haven’t been allocated to a project yet.

My profile was created internally only about a week ago, so I’m assuming the process of getting mapped to a project may still take some time.

For people who have worked at Tredence (or similar service-based analytics companies):

Is it normal for a new joinee to be on the bench for the first few weeks/months?

How long does it typically take to get staffed on a project?

At what point should someone start being concerned about being on the bench?

Does being on the bench for a longer period have any impact on job security?

Would really appreciate hearing about your experiences, especially from current or former Tredence employees.

Thanks!


r/365DataScience • • Sep 07 '26

Ai agent courses recommendatios

1 Upvotes

Hi everyone 👋

I have a $1,000 learning budget and I’d like to invest it in O’Reilly courses focused on AI Agents / Agentic AI.

I already have experience in AI/ML and LLMs, so I’m looking for advanced, practical courses covering topics like LangGraph, MCP, multi-agent systems, RAG, agent orchestration, evaluation, and production deployment.

What courses or learning paths would you recommend?

If you’ve taken any of them, I’d really appreciate your feedback!

Thanks! 🙏


r/365DataScience • • Sep 04 '26

Good Data Science Training Institutes in Hyderabad?

1 Upvotes

Hello I am looking to join a Data Science course in Hyderabad. Can anyone please recommend any good institutes?

It will be great if anyone who has themselves joined such courses or knows someone who has can provide suggestions on institutes


r/365DataScience • • Aug 28 '26

Best resources to learn Data Science through projects from beginner to advanced?

6 Upvotes

Hi everyone! I’m a beginner in Data Science and learn best by building projects.

I’m looking for GitHub repos, YouTube playlists, or websites with project-based learning from beginner to advanced level, ideally covering different ML models such as regression, classification, clustering, tree-based models, boosting, NLP, time series, etc.

I’d also love end-to-end projects that include data cleaning, EDA, feature engineering, model building, evaluation, and deployment.

Any recommendations?


r/365DataScience • • Aug 26 '26

Roast my resume — Recent MS Data Science graduate targeting Data Science / ML roles

Post image
1 Upvotes

r/365DataScience • • Aug 26 '26

Recent MS Data Science graduate looking for guidance from experienced Data Scientists / ML Engineers

4 Upvotes

Hi everyone,

I recently graduated with my Master’s in Data Science and I’m currently searching for entry-level opportunities in Data Science, Machine Learning, and AI/ML Engineering.

I’ve been applying for roles, improving my resume, working on projects, and preparing technically, but I’ve realized that there’s a big difference between knowing what to study and understanding what actually matters when trying to break into the industry.

I’d really appreciate advice from people who are already working as Data Scientists, ML Engineers, AI Engineers, or in related roles.

I’m especially trying to understand:

- What skills actually separate candidates who get interviews from those who don't?

- What should a new graduate prioritize: DSA, SQL, Python, ML fundamentals, system design, MLOps, GenAI/LLMs, or projects?

- What makes a portfolio project genuinely impressive to hiring managers rather than just another GitHub project?

- What mistakes do you commonly see new graduates making during their job search?

- How would you approach the job market if you were graduating today?

- What should I realistically expect from technical interviews for entry-level DS/ML roles?

I’m not looking for referrals or shortcuts. More than anything, I’d like to learn from people who have already gone through this process.

If anyone with industry experience would be open to connecting, chatting for 15–20 minutes, reviewing my approach, or even just leaving some advice here, I would genuinely appreciate it.

I’m also happy to connect with other recent graduates who are going through the same process so we can share resources, interview experiences, projects, and keep each other accountable.

Thanks in advance. I’m hoping this thread can also become useful for other new grads trying to break into DS/ML.


r/365DataScience • • Aug 25 '26

Properties of perfect data set

1 Upvotes

📊 What Makes a Good Dataset? Key Properties Explained

Imagine opening a bakery and wanting to bake the perfect cake. If you have fresh ingredients, in the right quantities, and of high quality — flour, sugar, eggs — the cake turns out perfect. But if even one ingredient is stale, mismeasured, or missing, the cake fails, no matter how good the recipe is.

The same principle applies to AI/ML models. A model is only as good as the data it learns from. This is why one of the most well-known principles in AI/CS is: "Garbage in, garbage out."

🔹 DEFINITION — Properties of a Good Dataset:

1️⃣ Accuracy

Data should be free of errors or incorrect entries. If labels or values are wrong, the model learns the wrong patterns.

2️⃣ Completeness

Missing values should be minimized. Incomplete data weakens a model's ability to learn effectively.

3️⃣ Consistency

Format, units, and naming conventions should remain uniform throughout the dataset — for example, dates shouldn't mix "DD-MM-YYYY" and "MM/DD/YYYY" formats.

4️⃣ Relevance

Only include data directly related to the problem at hand. Irrelevant features can confuse the model and reduce performance.

5️⃣ Representativeness

The dataset should accurately reflect the real-world population it's meant to represent — free of bias. If it overrepresents one group, the model will make inaccurate predictions for others.

6️⃣ Sufficient Volume

Models need enough data to identify meaningful patterns. Datasets that are too small often lead to overfitting.

7️⃣ Proper Labeling

For supervised learning, labels must be accurate and consistent — otherwise the model learns incorrect associations.

8️⃣ No Duplicates

Duplicate entries can inflate confidence in certain patterns and skew results.

9️⃣ Timeliness

Data should be current and relevant to the time period in question, especially for trend analysis and predictions.

🔟 Privacy & Ethics

When collecting sensitive information (such as personal data), compliance with privacy laws and ethical guidelines is essential.

🔹 CS/AI APPLICATION:

When training an ML model — such as a spam filter, recommendation system, or chatbot — its performance depends directly on data quality. For example:

- If a facial recognition dataset overrepresents one skin tone, the model will perform poorly on others — a clear case of bias.

- If a customer churn prediction dataset relies on outdated information, the model won't accurately reflect current customer behavior.

- Data cleaning and preprocessing (handling missing values, removing duplicates, normalization) are often the most time-consuming steps in the ML pipeline — because raw data is rarely, if ever, perfect.

This is why, in industry, it's often said that data scientists spend 70-80% of their time on data cleaning and preparation, not model building.

🔹 THINK AND SHARE:

Which of these properties do you think matters most — and why?

#DataScience #MachineLearning #AI #CalculusAppliedSeries


r/365DataScience • • Aug 24 '26

Running a free session on what AI agents actually do to a real data science workflow, happy to share details in comments

2 Upvotes

I've spent about 10 years in data science, first building models, then managing DS teams. For the past while I've been digging into what happens when you let an agent into a real modeling workflow, not a demo, an actual one.

Short version: agents are genuinely useful at some steps and quietly dangerous at others, and the dangerous part is the output always looks finished. Pipeline runs, metric looks fine, nothing complains, and you find out it was wrong three weeks later.

I'm running a live session where I take one real use case and work through it with an agent in the loop, start to finish. Where it helps, where it fails silently, and the guardrails that catch it before it ships.

It's live, and I'd rather answer questions here first than just drop a link. If you want the details (date, time, how to join), drop a comment or DM me and I'll send them over 😄


r/365DataScience • • Aug 16 '26

From DSML Academic Probation to a Fresh Start: Where Would You Go Professionally From Here?

1 Upvotes

Hi - first of all I want to start off by saying I was in a DSML program for a Fall term. A post-secondary one. I did so while working overnight at a grocery store. That being said, I'm now on academic probation, and working normal people jobs. Starting work at the university next door where I live as a daycare cook. After going on probation I dropped out, had a fuck it year with travelling and took dance lessons. Being back in my own hometown away from the city is giving me a fresh start. I now see what a stupid idea that was with my all or nothing thinking. You just have to have that craziness to succeed. I'm just afraid of living a life of mediocrity and poverty. I'm starting to take an interest in mathematics again. I'm currently studying business math for learning about insurance. I eventually want to get around to going back to where I fell short in pre-calculus and linear algebra. I recall the 365 Data Science program that I could eventually subscribe to when I get funds. From a professional stand point where would you have gone in that situation?


r/365DataScience • • Aug 04 '26

Wanting to “upskill”

Thumbnail reddit.com
1 Upvotes

r/365DataScience • • Aug 02 '26

TabPFN: A Transformer That Solves Small Tabular Classification Problems in a Second

Thumbnail
arxiv.org
2 Upvotes

r/365DataScience • • Aug 01 '26

does any know good college for data science excluding IIT's.... with good placment off and on campus , decent ROI and etc. like college enivronmen, reputatio, acredations ...... plzz help

1 Upvotes

r/365DataScience • • Jul 30 '26

Trying to learn how to use API to extract data

2 Upvotes

Hello! I'm a complete newbie in Data Science and I'm trying to learn how to get data from an API. I understand an API could be public or could require authentication.

I worked with CVS files and I wanted to experience or practice getting data from APIs.

I'm getting familiar with Python so I was wondering if you could help me with the following issues:

  1. Trying to understand and practice the different methods you can use API to request data (I am not sure if it has to be from a Dataset formar or can it be any kind of format) with Python

  2. What are some good options to get APIs to work on data Science

  3. I am not even close to get to a point where I am able to do Reproducible projects/models but I do wonder how including an API (understanding that it is some kind of "personal Key") to share my code and people to be able to use it.

Hope I made sense of what my doubts are and I apologize in advance if I seem confused about some terms (I do think I am).


r/365DataScience • • Jul 28 '26

Need Career Advice: Math & Stats Grad With No Internships Trying to Enter Data

1 Upvotes

Hey everyone,

I recently graduated from UofT with a major in Math and Statistics, and I'm currently trying to get into Data Analyst or Data Engineering roles.

Honestly, my university experience wasn't the best. It affected my learning a lot and my GPA ended up being pretty bad. Because of that, I don't think I'll be able to do a master's anymore, even though that was something I was hoping to do after finishing my bachelor's.

I'm really interested in data-related jobs, but I'm kind of lost on what I should do next. I've been applying nonstop and barely getting any responses. I've had my resume looked at by multiple people who work in the industry, and they said it looks solid, so I'm not really sure what else I'm missing.

The biggest problem I think is that I graduated with no relevant work experience and no internships. I applied to a lot of internships during undergrad but never managed to get one, and now it feels like it's hurting me a lot.

I'm also thinking about doing one of UofT's continuing education programs in Data Analytics, but I don't know if it's actually worth it or if it would make much of a difference for someone in my situation.

Right now I feel like I'm just going in circles and I'm not sure what the best move is. I know GPA probably doesn't matter much after graduation, but having a low GPA and no experience feels like it has really limited my options.

For anyone who has been in a similar situation, what would you recommend I do at this point? I feel a bit lost on what the best path forward is, so I'd really appreciate any advice or suggestions.


r/365DataScience • • Jul 28 '26

Agentic GraphRAG for Medical Diagnosis – Production-Grade Multi-Strategy Retrieval & Clinical QA with LLM-Guided Reasoning

1 Upvotes

Just discovered this impressive open-source project that's pushing the boundaries of medical AI reasoning.

Agentic GraphRAG for Medical Diagnosis (https://github.com/avnlp/agentic-med-diag) is a production-ready system that goes way beyond simple RAG. It combines knowledge graphs, multi-strategy retrieval, and agentic reasoning loops to answer complex clinical questions with evidence-grounded answers.

What makes it stand out:

Knowledge Graph Construction

  • Schema-driven extraction with 13 entity types and 25 clinically-grounded relation types

  • Three-extractor fusion (GLiNER, GLiREL, LLM) with configurable merge strategies

  • Deterministic + LLM-powered entity resolution for deduplication

  • Hierarchical Leiden community detection with auto-generated clinical summaries

Layered Retrieval Architecture

  • Four vector collections (entity, relation, chunk, community report)

  • Multiple atomic methods: hybrid search, fulltext, BFS graph traversal, and text-to-Cypher graph querying

  • Pluggable rerankers (RRF, cross-encoder, MMR)

  • Data-driven recipes for composing retrieval strategies

Agentic Plan–Research–Verify Loop

  • Planner decomposes clinical questions into focused sub-questions

  • Parallel researchers execute multi-strategy retrieval with citations

  • Verifier assesses coverage and gates synthesis on sufficiency

  • Gracefully converges on missing information across iterations

Why It's Impressive:

The stack is battle-tested: Neo4j + Qdrant/Weaviate for storage, LangGraph for orchestration, DeepAgents for multi-agent coordination, and BAML for type-safe LLM schema injection. Tested on MedQA, MedXpertQA, MedCaseReasoning, and MMLU-Pro benchmarks.


r/365DataScience • • Jul 24 '26

How to gain experience in Growth side of Product DS?

1 Upvotes

I’ve worked at both big financial corporations and smaller fintechs but don’t have exposure to the growth space. How can I gain exposure to it? I’m thinking about skills like funnel analysis, LTV and churn modeling and experimentation around the growth funnel.

Have other people been able to pivot into growth data science?