Career quiz — which work actually fits you?

When starting a new project, what excites you most?

Exploring the possibilities and discovering what could be built. Diving in and building something tangible as quickly as possible. Understanding the data, constraints, and requirements before doing anything. Talking to people to understand what they actually need.

How do you prefer to spend a typical Friday afternoon?

Experimenting with a new tool, language, or idea I have been curious about. Finishing a feature or fixing something that has been bothering me all week. Reviewing data, dashboards, or results from the week. Catching up with colleagues and planning what comes next.

Which of these sounds most like a perfect work day?

Jumping between conversations, ideas, and prototypes — never the same twice. Getting into flow state and shipping a complete feature from start to finish. Running an analysis and finding the answer to a business question nobody else could. A mix of building and reviewing — some code, some numbers, some people.

When you hit a problem you cannot immediately solve, what do you do?

Look up related ideas and explore tangential solutions — the detour is interesting. Try different approaches systematically until something works. Break it into smaller parts, identify the root cause, and work backwards. Ask someone else who might know — why reinvent the wheel?

How do you feel about documentation and process?

Tolerate it — I know it is necessary but I would rather be doing things. It is part of shipping — good documentation is part of good engineering. I enjoy it — well-documented decisions and data pipelines make everything better. I do it when it helps me think, not as a formality.

Which tool or environment makes you feel most at home?

A Notion page or whiteboard — ideating and mapping out possibilities. A code editor with a clean codebase and fast tests. A Jupyter notebook or SQL editor — data at my fingertips. A dashboard showing the current state of a system or metric.

What kind of feedback energises you most?

"That is a really creative idea — I had not thought of that angle." "This is really well built — it works exactly as expected." "Your analysis completely changed how we thought about this problem." "You always know how to bring the right people and ideas together."

When learning something new, which approach feels most natural?

Browsing broadly — articles, talks, examples — to get a feel for the space. Building a small project to understand how it actually works. Reading documentation carefully and understanding the theory first. A structured course with exercises and clear milestones.

What bothers you most in a team setting?

Being stuck on one thing for too long — I need variety and momentum. Unclear specs or constantly changing requirements that break what I built. Decisions made without data or clear reasoning. Poor communication and siloed working styles.

How do you measure the success of your work?

By the quality of ideas generated and the conversations started. By what shipped, deployed, and works reliably in production. By the measurable improvement in a metric or the quality of a decision. By the impact on the people or product I was working with.

How do you feel about ambiguity at work?

Energised — ambiguity is where creativity lives. Manageable if I can still define a clear deliverable for myself. Uncomfortable — I need to define the problem clearly before moving forward. Fine as long as I can ask questions and align with the team.

Which project sounds most appealing to you?

Researching an emerging technology and presenting a proposal on how to use it. Rebuilding a slow, buggy system so it is clean, fast, and maintainable. Investigating why a key business metric dropped and presenting the findings. Running workshops to help a team work better together.

When you finish a project, what do you feel most proud of?

The novel approach I took that nobody had tried before. How well it was built and how little technical debt I left behind. The clarity and rigour of my analysis or reasoning. The relationships and trust I built while doing it.

What role do you usually take in group projects?

The one bringing in new ideas and connecting the dots between different areas. The one making things work — building, coding, or executing. The one checking assumptions, reviewing the data, and catching errors. The one keeping the team aligned and communication flowing.

How do you feel about working with numbers and statistics?

Interesting when they tell a story — but I prefer ideas and context. Useful for measuring what I build — I care about metrics. This is where I come alive — patterns, distributions, and models. Fine in moderation — data should support decisions, not replace them.

Which of these statements feels most true about you?

"I get bored doing the same thing twice." "I am not satisfied until it actually works properly." "I want to understand why before I do anything." "I care most about the people affected by my work."

What would your ideal team look like?

Small, cross-functional, always trying new things. Technically excellent, focused on quality, with clear ownership. Evidence-driven, structured, with high standards for rigour. Collaborative, high-trust, with strong communication norms.

What do you find most satisfying about your best career moments?

I discovered or connected something nobody else had put together. I built something that still works well and people depend on. I found a pattern in the data that changed a real decision. I helped someone else grow, succeed, or feel supported.

How do you approach a problem you have never seen before?

Embrace it — novelty is the most interesting part. Break it into familiar components and build up from there. Research first, understand the landscape, then form a hypothesis. Talk to people who have dealt with similar problems before.

What does career success look like to you in five years?

Being known as someone who always brings a fresh perspective and sharp ideas. Being the technical expert people turn to when things need to get built properly. Being the person who sees what the data really means before anyone else does. Leading a team that does great work and trusts each other completely.

Let's find what actually fits you

Fale connosco