Data Science Career Vision and Professional Philosophy

My 60-Second Professional Pitch

My background is in mathematics, with a strong focus on probability, combinatorics, algorithms, and programming. Over time, I realized that what I enjoy most is not only abstract problem-solving but using quantitative tools to solve real-world problems. That’s why I’m interested in data science.

I enjoy programming, analyzing data, and turning ambiguous questions into structured analyses. Professionally, my goal is to become a very strong data scientist: someone rigorous technically, but also practical, communicative, and able to influence product decisions.

I’m hardworking and ambitious, but I define ambition as becoming genuinely excellent and useful. I’m looking for an environment with high standards, smart people, direct feedback, and challenging problems. That’s why Bending Spoons is especially attractive to me.

Core Motivation and Working Style

I want to grow as a data scientist by combining my mathematical background with programming and real-world problem-solving. I’m motivated by difficult analytical challenges, fast learning, and work that has practical impact. My working style is structured, persistent, and ownership-driven: I like clarifying the goal, breaking problems down, building solutions, and improving through direct feedback.

Professional Goals and Long-Term Vision

I want to become the kind of data scientist who is not only technically strong but also useful. I like math and programming, but what really motivates me is using them to solve real problems and make better decisions.

My main goal is to grow into a strong data scientist who can combine rigorous quantitative thinking with practical impact. I come from a mathematics background, so I’m naturally drawn to probability, algorithms, and structured problem-solving, but I’m especially interested in applying those tools to real products and real users.

In the short term, I want to become excellent at the full data science workflow: understanding the business problem, working with data, building models or analyses, communicating insights clearly, and helping teams make better decisions. In the long term, I’d like to become someone who can own complex analytical problems end-to-end and contribute to product and strategy through data.

Preferred Analytical Challenges

I enjoy problems where logic and creativity both matter. For example, in combinatorics or probability, you often need technical tools but also the right way of framing the problem. In data science, I find that similar: the model or calculation matters, but the most important step is often asking the right question and translating a real-world situation into something measurable.

Future Outlook: 3 to 5 Years

In 3 to 5 years, I’d like to be a highly reliable data scientist—someone who can take ambiguous problems, structure them, analyze them rigorously, and deliver recommendations that influence product decisions. I’d like to keep growing technically, especially in machine learning, experimentation, and causal/product analytics, but also develop stronger judgment about which problems are worth solving and how to communicate results to non-technical stakeholders.

The Appeal of Data Science

Data science sits at the intersection of several things I genuinely enjoy: mathematics, programming, uncertainty, and real-world decision-making. I like problems where there is no obvious answer, but where careful reasoning and good use of data can reveal structure.

My academic background gave me strong foundations in probability, algorithms, and combinatorics, and my internship exposed me to practical data work through SQL, ETL pipelines, and dashboards. Data science feels like the natural next step because it allows me to combine depth with impact.

I enjoyed academic mathematics and research because it trained me to think rigorously and persist through difficult problems. However, I realized that I’m more motivated when my work connects to real-world outcomes. I like seeing how an analysis, a model, or a piece of code can affect a product, a decision, or a user experience.

Professional Passions and Working Methodology

I’m passionate about solving difficult problems. I enjoy the process of taking something messy or ambiguous, finding structure, and turning it into something understandable and useful. That’s one reason I studied mathematics, and it’s also why I enjoy programming: both reward clarity, persistence, and precision.

I’m structured, persistent, and quite independent, but I also value feedback early. When I face a problem, I usually try to understand the objective first, then break it into smaller parts, identify assumptions, and work systematically. At the same time, I’ve learned that working in isolation for too long can be inefficient, so I try to share intermediate reasoning, ask for feedback, and make sure I’m solving the right problem.

Teamwork and Collaboration

For deep technical work, I like having focused time alone to think, code, or analyze. But I believe the best results usually come from teams, especially when people challenge each other’s assumptions and communicate clearly. My ideal setup is: align as a team on the goal, work independently with ownership, then come back together to test ideas and improve the solution.

Managing Pressure and Stress

I try to respond to pressure by becoming more structured, not more chaotic. I identify what matters most, what can be simplified, and what decision needs to be made. I’m used to pressure from exams, research deadlines, teaching, and competitive volleyball, so I know that staying calm is often more valuable than trying to do everything at once.

Ambition and Drive

Yes, I am ambitious, but I try to define ambition as becoming genuinely excellent, not just collecting titles. I want to work in an environment where the standards are high because that’s where I improve the fastest. I’m willing to work very hard, especially when I’m learning and when the work has real impact.

Defining Professional Success

Success means becoming very good at work that matters. I want to keep improving technically but also develop judgment, reliability, and the ability to create impact with others. For me, success is when people trust me with hard problems because they know I will approach them seriously, learn fast, and deliver.

Work Ethic and Dedication

I’m very hardworking, especially when I care about the goal. I’ve always combined demanding academic work with other commitments, and I’m comfortable putting in sustained effort. That said, I don’t think hard work means just spending more hours blindly. I think the best version is intensity plus reflection: working hard, but also checking whether the effort is going in the right direction.

Learning from Past Failures

During some technical or academic projects, I’ve sometimes underestimated how important communication is compared with the technical solution itself. I might understand the logic internally, but if I don’t explain assumptions and results clearly, the work loses value. Teaching mathematics helped me improve this a lot because it forces you to translate complex ideas into something understandable for others.

Core Strengths and Unique Value

My main strengths are analytical rigor, persistence, and learning speed.

Analytical rigor comes from my mathematics background: I’m used to working carefully with assumptions and logic. Persistence comes from spending time on difficult problems that don’t have immediate solutions. And learning speed is something I’ve developed by moving between mathematics, programming, data analysis, and teaching.

I think my strongest differentiator is the combination of mathematical depth and practical motivation. I have a strong foundation in probability, combinatorics, algorithms, and programming, but I’m not interested in theory for its own sake only. I want to use that background to build useful analyses, solve product problems, and make better decisions with data.

Why I Am the Right Candidate

Because I bring strong quantitative foundations, genuine motivation for data science, and a working style based on persistence and ownership. I’m comfortable with abstract reasoning, but I also enjoy programming and practical problem-solving. I learn fast, I’m ambitious, and I’m looking for a place with a high bar where I can contribute and grow quickly.

Addressing Professional Weaknesses

One area I’ve had to work on is avoiding over-investment in finding the most elegant solution. Coming from mathematics, I sometimes naturally look for the cleanest or most complete approach. In practical data work, I’ve learned that it’s often better to build a simple first version, test whether it answers the real question, and then improve it. I’m still detail-oriented, but I’ve become more conscious of balancing rigor with speed and usefulness.

Why Bending Spoons?

I’m interested in Bending Spoons because it seems to combine a very high talent bar with real product impact. From what I’ve read, the company puts a lot of emphasis on rigorous hiring, strong people, ownership, and direct feedback. That appeals to me because I’m looking for an environment where I can grow quickly and be challenged.

I also like that the work is connected to digital products at scale. For data science, that’s attractive because the analysis is not abstract: it can influence real users, product decisions, and business outcomes.

Expectations for the Next Role

I’m looking for a role where I can grow fast, work on difficult analytical problems, and be surrounded by people with high standards. I want to be given ownership, receive direct feedback, and contribute to real decisions. I don’t need the work to be easy; I care more about learning, impact, and being part of a serious team.

Ideal Work Environment

I do my best work in environments with high standards, clear goals, autonomy, and honest feedback. I like knowing what outcome matters, having enough ownership to think deeply, and working with people who are direct but constructive.

Should be Good at 

  • I enjoy solving difficult problems.
  • I like learning new things quickly.
  • I take ownership of my work.
  • I am comfortable receiving direct feedback.
  • I work hard to achieve ambitious goals.
  • I enjoy analytical thinking.
  • I like programming/building things.
  • I can work independently.
  • I care about the quality of my work.
  • I stay calm under pressure.
  • I enjoy working with smart and demanding people.
  • I am comfortable with ambiguity.


Historia 1: investigación matemática

Sirve para: hard problem, persistence, analytical rigor, ambiguity.

Situation: research in combinatorial probability.
Task: understand/derive estimates or verify combinatorial models.
Action: broke down the problem, studied assumptions, simulated in Python, compared theory and empirical behavior.
Result: contributed to research, improved ability to combine theory and computation.

Historia 2: data analyst intern

Sirve para: practical impact, programming, real-world data, communication.

Situation: internship at InOrbis Analytics.
Task: maintain ETL pipelines, dashboards, SQL queries.
Action: understood data flow, improved queries/pipelines, translated data into operational dashboards.
Result: learned that useful data work requires reliability, clarity, and business context.

Historia 3: docencia o volleyball

Sirve para: communication, pressure, teamwork, feedback.

Teaching version: explicar cálculo/álgebra a estudiantes de economía te obligó a simplificar ideas complejas.
Volleyball version: presión competitiva, equipo, resiliencia, feedback rápido.