How a Freelancer's Problem Became HintCraft
I built the first version of HintCraft because every new contract search brought back several jobs at once. Find opportunities, speak to people, adapt applications, prepare for interviews and remember who needed a reply. Meanwhile, the useful work from my previous search was scattered across notes and memory.
The difficult part was keeping all of this moving while waiting for decisions I could not control. An application sent today might produce a conversation weeks later. By then, I could be preparing for something else entirely. After more than a decade of contracting, with assignments lasting three months to a year and sometimes less, I had plenty of opportunities to notice the repetition.
Each round left me with something worth keeping: a clearer answer, a useful contact, a story I could explain better. I am an engineer. When I find myself improving the same process by hand for the fourth time, I want somewhere to store what I have learned. HintCraft began as that place, then grew to support the applications, conversations and follow-ups around the preparation.
I wrote the first version about ten years ago in Angular, for myself. Each interview cycle, I added whatever I had discovered I needed. A library of stories I could return to instead of reconstructing them under pressure. A list of companies worth exploring and the people I knew inside them. An application tracker so I could remember where things stood. A playbook of recurring questions and answers I had refined through use.
I also had someone to discuss the process with. Kate had spent years recruiting and hiring in tech. We talked about interviews the way other couples talk about renovation projects: frequently, and with strong opinions. She described candidates whose answers sounded scripted or stayed too vague to reveal their contribution. Having sat on hiring panels myself, I recognized the pattern.
Doing the work and explaining the work are different skills. An interview asks you to demonstrate both, often with very little time to find the right example.
What Our Friends Kept Asking Us
For years, friends and colleagues had been asking us similar questions. "I have an interview next week, can you help me prepare?" "How do I answer 'tell me about yourself' without sounding rehearsed?" "What do interviewers look for?"
Kate and I kept returning to the same frameworks and examples. At some point we started wondering whether we could make that guidance available without having the whole conversation again, one person at a time.
Interviewing can have a considerable effect on your career, yet you may go years without practising it. Then a contract ends or an opportunity appears, and you need the skill immediately. It is an awkward time to discover that you remember the project but cannot explain your part in it.
I already had a tool I had been refining for years. The next step seemed straightforward: modernize the stack and let other people use it. So I showed it to Kate.
What I Built Was a Mirror
I was proud of the answers the system produced. They drew on my projects, used familiar phrasing and reflected my tendency to explain things through analogies. I expected Kate to recognize something useful.
She went through the questions patiently. For many of the answers, her response was the same: "This does not sound like me at all. I would never say it this way. This is your way of thinking, not mine."
She was right. I had built around my own communication style without noticing how many assumptions I had made. I tend to lead with systems and parallels. Kate pays more attention to people and the context of the conversation. An answer that felt natural to me could feel completely foreign to her.
That was a useful product test. My preference had quietly become the default.
An answer can be accurate and well structured, yet still use words you would never say. Read it aloud before deciding it is ready.
That evening we added the personality assessment. It gave us another way to discuss differences in how people approach work and communication. Today, the assessment is optional. It supplies suggestions for areas such as strengths, values and working style, which you can review against your experience and edit.
It is one source of context. Your work history, stories and communication preferences matter too. When you prepare an interview answer, the available context options let you shape what the AI draws on. My Voice gives you a place to describe how you want to sound.
The useful work happens when you review the draft. If it understates your contribution, add the decision you made and what followed. If it takes too long to reach the point, shorten it. The tool can help you revise, but you know whether the account is true and whether you would say it that way.
Some of the Interview Is Outside Your Control
You rarely see the whole hiring decision. A budget may change. An internal candidate may be under consideration. The team may need experience another candidate has. Even a useful conversation can end without an offer.
I cannot put a percentage on how much preparation controls. I can point to work worth doing: understanding the role, researching the company, choosing relevant examples and preparing questions that help you decide whether you want the job.
You cannot pick the weather on the day of your wedding. You can check whether the tent has poles.
When hiring, I have spoken with candidates whose contribution remained unclear because the example was too vague. I have also seen interviews where the candidate had little to ask about the work. Those are gaps preparation can address. They do not explain every rejection, and a rejection on its own tells you little about what happened.
After an interview, separate what you know from what you are guessing. Record the feedback you received, the questions you struggled with and anything you want to explain more clearly next time.
After a conversation, I want to keep something more useful than my impression of how it went. Which question was difficult? Which example needed more detail? What did I learn about the role? Those notes give me something specific to improve.
In HintCraft, that means recording the conversation in the application, updating the relevant story or answer, and noting the next commitment. The next opportunity benefits from work I have already done.
"Be Yourself" Is Incomplete Advice
"Just be yourself" is advice people give with good intentions. It has roughly the same practical value as telling someone to "just be funny." You still need to know what to do when the conversation starts.
Preparation gives you something concrete to work with. Choose a few examples, understand the company beyond its homepage and practise describing a difficult decision. You can then spend more attention on the question being asked, because you have already thought through the experience behind your answer.
A stand-up comic can prepare carefully and still sound like themselves. The same principle is useful here: know your material well enough to respond to the room. Memorizing every sentence can make that harder when the interviewer asks a different question.
I have heard candidates describe a project accurately but spend so long on its history that we barely reached their contribution. They knew the work. What needed practice was choosing the part that mattered to this conversation. That is something you can improve without adopting someone else's personality.
Interviewers Are People With Constraints Too
An interviewer may be fitting the conversation between meetings, trying to assess several candidates or working with an incomplete brief. Some are well prepared. Some are learning how to interview while doing it. You cannot know all of that from the calendar invitation.
What you can do is pay attention. Answer the question, ask for clarification when you need it and show interest in the work they describe. If there is room for a lighter exchange, take it naturally. You do not need to become an entertainer to have a useful conversation.
I have had interviews where a good exchange mattered more than I expected. I have also left conversations knowing that my answers were technically correct but that I had spent too little time listening. Getting through my prepared material was not the same as understanding what the other person needed to know.
An interview is also a chance for both people to understand how working together might feel. Listen for the problems the team is trying to solve, and give them enough detail to understand how you would approach the work.
Preparation, your own way of speaking and interest in the other person can support each other. You can be nervous and still do all three. Trying to perform confidence adds another task to an already demanding conversation.
What I Learned About Careers Along the Way
Freelancing, hiring and being hired left me with a set of beliefs about career decisions. Some shaped specific HintCraft features. Others guide how I use the tools. They come from my experience, and their usefulness depends on your circumstances.
Have a direction you can act on
What do you want the next role to make possible? Better pay, a different kind of work, more stability, something you want to learn? Those questions help you judge an opportunity before investing hours in it.
You may also need a job now. A longer-term direction has to coexist with that reality. I find it useful to distinguish what I need from the next role from what I would like to build towards over several moves.
In HintCraft, My Profile holds your preferences and desired role, while the Dashboard lets you set daily application and networking targets. You can start with an opportunity already in front of you and refine those preferences as you learn. There is no need to finish planning your career before replying to someone today.
Keep in touch beyond your immediate circle
Sociologist Mark Granovetter's research on the strength of weak ties explains how acquaintances can connect you to information outside your usual circle. A former colleague or someone you worked with briefly may hear about opportunities your closest contacts do not.
I got a contract at Tesla because a CTO from a startup I had worked at years earlier remembered me. When he became a Software Engineering Director at Tesla, he reached out directly. We had not spoken in years. Our previous work together still mattered.
I had over 2,000 LinkedIn connections, but the number told me little about which relationships I was maintaining. Many were recruiters I had spoken to once or colleagues from jobs I had left years before. I could remember a useful conversation and still lose track of when to get back in touch.
That is why contact management belongs in HintCraft. Keep notes about the people, record conversations and schedule a next contact when there is a reason to do so. The value comes from the relationship you maintain, not from adding another name to a list.
Learn or earn, ideally both
Some roles taught me something valuable. Others paid well. The ones that did both were easier decisions.
A lower-paying job can be a good investment if it develops experience that opens later opportunities. That happened in my career: work I accepted for what I could learn helped me qualify for better-paid roles afterwards. But the tradeoff depends on your finances, responsibilities and what the role will let you learn. A higher salary is a reasonable priority when you need it.
I try to make that choice explicitly. A promise of learning deserves the same scrutiny as a promise of progression: what work will you do, with whom, and what will you know afterwards that you do not know now?
Recognizable companies can open doors
When I got my first contract at Zalando in Berlin, I noticed a difference in the conversations available to me. A recognizable company gave people a reference point for experience I had previously needed to explain in more detail.
I cannot turn that observation into a reliable hiring multiplier. A company name may help someone place your experience, but it does not explain your contribution. You still need to describe the work, and a less familiar employer can offer excellent experience.
HintCraft lets you research companies and keep a list of those you want to explore. The company directory is another starting point where available. Reputation can be one consideration alongside the work, conditions, compensation and people you would join.
Look beyond the advertised job title
I applied to Grid Dynamics as a senior developer and ended up building their frontend team. I applied to SoftwareOne for a senior frontend position. The work turned out to involve architecting the frontend stack for a new platform backed by tens of millions in investment.
Neither outcome was clear from the job description. Conversations revealed needs I could contribute to. If I had judged both opportunities by title alone, I would have missed something useful.
HintCraft keeps company research alongside applications linked to that company. You can track a specific role while investigating the wider organization and asking where your experience might fit. The conversation may confirm the advertised scope, or reveal something different worth considering.
Practise between opportunities
An interview gives you material for the next round of preparation. A question you struggled with can reveal a missing example. A follow-up can show that your original answer skipped something important.
Think of interviewing as you would a musical instrument. Preparing for a particular performance helps, and practice between performances gives you more to draw on when the next one arrives.
Interview Questions gives you a place to keep and refine answers outside a specific application. You can work on telling your story, prepare examples for behavioral questions and revise the wording until you sound like yourself. Then practise aloud. Saving a draft and being able to explain it in a conversation are different points in the preparation.
You do not need an active application to begin. Finishing a difficult project is a good moment to capture what happened, what you decided and what changed because of your work. Months later, those details are harder to reconstruct.
The same applies to relationships. Stay in touch when there is something worth discussing. Keep your CV current when your responsibilities change. These are small pieces of preparation you can maintain while employed, so a future search starts with material and relationships you have already developed.
What HintCraft Became
HintCraft became a place where the different parts of a search can inform each other. Your profile records your experience and priorities. Stories provide examples. A specific opportunity gives you a reason to select the relevant evidence, adapt your CV and prepare questions.
Conversations add information the job description did not contain. Applications and Contacts hold the activity and next commitments. The Dashboard brings scheduled work together so you can see what needs attention.
Some connections happen inside the product, such as using saved context for an answer draft. Others depend on you: sending the message, practising aloud, checking a claim or updating a story after an interview. The system supports those actions and keeps their results available.
That explains why HintCraft has several parts. You can begin with the task in front of you and use the others as they become relevant. An interview tomorrow deserves preparation today; you can develop your wider search alongside it.
The Tool I Wished I Had
We built HintCraft because we kept seeing useful experience become difficult to communicate, preparation get lost between searches and conversations lose momentum without a follow-up. Those were problems we could work on.
The system cannot decide who gets hired. It can give you a place to prepare, pursue opportunities and retain what you learn. Choose one piece of work you need now, whether that is an application, an interview answer or a recent achievement worth recording.
HintCraft is the tool I wished I had when I started freelancing, rebuilt to make room for people who think differently from me.