# ClearHire — full content index > Career tools, a resume builder, and verified employment history. Build it, prove it, get hired. Last updated: 2026-09-29 Short index: https://clearhire.aoneahsan.com/llms.txt Pricing: https://clearhire.aoneahsan.com/pricing.md This file carries the readable content of every indexed public page, generated from the same source the pages themselves render. 92 pages, 92 of them with body copy. ## Build it. Prove it. Get hired. https://clearhire.aoneahsan.com/ Career tools, a resume builder, and employment history a named company can confirm — in one place, and most of it with no account. ClearHire is three things: a catalogue of small career tools, a resume builder that exports real PDF and DOCX files, and employment history a named company can confirm. The third is the reason the other two are here. A resume is a document you wrote about yourself, so the true parts get discounted along with the invented ones. ClearHire asks the company, records the answer, and shows it beside the line. A countersigned record proves the company, the job title and the dates, as that company records them, plus who confirmed it and when. It is not a background check, not a reference, and not an identity guarantee — and if nobody answers within seven days it expires as unconfirmed, never as rejected. Most tools work with no account. Nothing about you is public unless you publish it, and a declined claim is never published at all. ## About ClearHire https://clearhire.aoneahsan.com/about ClearHire is career tools, a resume builder, and employment history a named company can confirm — built and maintained by the ClearHire team. ClearHire is three things: about fifty-three small career tools, a resume builder that exports real PDF and DOCX files, and employment history a named company can confirm. The third is the reason the other two exist here rather than somewhere else. It is not a background-check service, not a reference, not a job board and not an identity guarantee. Those four boundaries are on the about page in as much detail as the four things it is, because preventing the wrong expectation is the more expensive mistake. The ClearHire team builds and maintains everything here. There is no support team, no sales team and no privacy department — when you email, a person reads it. ## Apps https://clearhire.aoneahsan.com/apps ClearHire runs on the web and as an Android app — no iOS app and no browser extension. This page also lists the other apps built by the same team. ClearHire is a website and an Android app. Everything except buying a plan works identically in both places. There is no iOS app and no browser extension, and neither is promised. The ClearHire team builds a number of other apps too, and those are the only promotions ClearHire carries. They are first-party: there is no advertising network in this product and nothing you do here is measured against an advertising profile. ## Writing https://clearhire.aoneahsan.com/blog Notes on hiring, resumes and verified employment — written when there is something worth saying, not on a schedule. The ClearHire writing index collects posts about hiring, resumes, interviews and employment verification. Posts are published when there is something worth saying rather than to a schedule. Nothing here is sponsored and nothing links out for a fee. Where a post describes what ClearHire does, it says so plainly rather than pretending to be neutral about it. ## Career mentors https://clearhire.aoneahsan.com/career/mentors A mentor is somebody a few years further along who will read your work, answer the questions you cannot ask your manager, and tell you when an offer is worse than it looks. ClearHire is building that, one match at a time, from people whose employment records companies have actually confirmed. A mentor is somebody a few years further along who will read your work, answer the questions you cannot ask your manager, and tell you when an offer is worse than it looks. ClearHire is building that, one match at a time, from people whose employment records companies have actually confirmed. There is no list of mentors on this page, and there is not one anywhere else either — because we have not matched anybody yet and printing names we do not have would be the easiest lie in this product to tell. What exists today is the register below, on both sides. When there are enough people on each side of it in the same field, we open matching there first and email the people who registered for it, in the order they registered. Small, slow and specific. Three of these are deliberate limits rather than a first version we intend to grow out of. All of it, in advance, including the parts that are inconvenient. Most of what people want a mentor for is one of three things, and all three work now. ## Learning resources https://clearhire.aoneahsan.com/career/resources Courses, certifications and tutorials worth the time, and how to tell which ones an employer will recognise. The career resources hub is the entry point for the most common career-decision questions: choosing a role, planning skills development, preparing for promotions, navigating layoffs, deciding between offers, switching fields. Resources are organized by career stage (early, mid, senior, leadership) and decision type (planning, executing, deciding) so you can navigate to the relevant tool or guide quickly. New tools and guides land monthly; existing resources are reviewed quarterly for currency. The hub is a navigation layer, not a content hub on its own — every link goes to a specific tool or guide that addresses the question directly. Picking the next career move. Mid-career stage + decision type "deciding" surfaces the career quiz, skills-gap analyzer, and offer comparator. Three tools that together cover most "what next?" questions for someone with 5–15 years of experience. Planning a 90-day learning sprint. Any career stage + "planning" surfaces skills-gap, learning-path, and career-roadmap tools. Together they produce a focused plan with visible milestones rather than scattered intent. Navigating an unexpected layoff. Mid / senior stage + "executing" surfaces salary calculator, negotiation scripts, and offer comparator — the tools you need on a tight timeline. Also surfaces the resume + ATS chain for fast re-tailoring. Using this hub when the question is not yet a question. Sometimes the useful step is to name the discomfort rather than to plan. If you cannot say what you want next, the productive move is not a roadmap — it is a short list of what you no longer want, which is almost always easier to write and narrows the field just as effectively. Coming back to a plan you abandoned. An abandoned plan is data, not failure. Look at where it stopped: an over-ambitious weekly commitment, a goal that turned out not to be wanted, or an external change. Each of those implies a different restart, and rewriting the same plan without diagnosing which one it was is how the second attempt ends the same way. Pick your career stage. Early (under 3 years), mid (3–10), senior (10–20), leadership (20+). Resources differ by stage; pick the closest fit. Pick the decision type. Planning (preparing for the next move), executing (actively making the move), deciding (choosing between options). Each surfaces different tools. Open the 2–3 surfaced resources. Resources are curated for the stage + decision combination. Two or three tools cover most situations; more than that becomes overwhelming. Bookmark the resources you use repeatedly. Some resources you will use once; others repeatedly across years. Bookmarking the repeated ones saves the navigation step on future visits. A senior engineer planning a path to staff Senior + planning surfaces skills-gap, learning-path, career-roadmap. Engineer uses all three across the next 3 months. Promoted at month 9 — the curated path saved the time of figuring out which tools to use. Someone six weeks into an unplanned search with no shortlist They stopped reading and wrote down the three things they no longer wanted, which ruled out two of the four directions immediately. The remaining two were answerable with a fortnight of conversations rather than another month of reading. Stage + decision type usually narrows to 2–3 relevant tools — start there. Bookmark tools you use repeatedly; the navigation step compounds. New resources land monthly; revisit periodically to see what is new. Different from /resources/ which organizes by interview stage rather than career-decision context. Check a certification by searching for it in real adverts for your target role — ten minutes, and more reliable than any ranking. Pick the weekly hours you would still manage in a bad week; anything above that is a bonus, not the plan. Where should I start if I do not know what my next move is? Start with the decision type rather than the destination. Most career questions are one of a small number of shapes — choosing between offers, planning skills, recovering from a layoff, changing field — and each has a different first step. Naming which one you are in narrows the reading enormously, and it is usually easier to identify than the answer is. How do I tell whether a course or certification is worth the time? Look for it by name in adverts for the role you want. A certification that appears repeatedly in the postings you are targeting is recognised; one that appears in the provider's marketing and nowhere else is not. That single check takes ten minutes and is more reliable than any ranking, because it measures the only audience that matters. Is a certification worth more than a project? It depends on which one the field uses as a filter. Some domains screen on specific certifications and a project will not get you past the screen; in others a finished, explainable piece of work is worth far more than any course. Read five adverts for your target role — if a certification is a hard requirement it will say so, and if it is not, build the thing instead. How much time should I put into learning while working full time? Enough that it survives a bad week, which for most people is a few hours rather than an ambitious evening schedule. A plan that assumes ten uninterrupted hours collapses the first time work runs late and takes the habit with it. Pick a number you would still hit in your worst week, and treat anything above it as a bonus. What do I do when I have been laid off? Handle the immediate practicalities first, then treat the search as the job. The order matters — money, notice terms, health cover and references are time-sensitive and get harder to sort out later. Once those are settled, a layoff is a search with more hours available and the same mechanics as any other, and framing it that way is what stops the first fortnight disappearing. How often should I revisit a career plan? Quarterly for the next steps, yearly for the destination. Plans go stale in two different ways: the tasks stop matching what you are actually doing, and the goal stops being what you want. The first needs a small correction every few months; the second needs an honest annual conversation with yourself, and it is the one people skip. ## Career roadmap https://clearhire.aoneahsan.com/career/roadmap How roles progress in practice — the steps between titles, and what usually has to be true before each one. A career roadmap is a 1–3 year written plan that names the role you are aiming for, the skills you need to get there, the projects that build evidence, and the checkpoints where you reassess. Roadmaps beat goals because they tell you what to do next week, not just where to end up. Most career stalls happen because people set vague goals ("get promoted", "switch fields") without a written plan to make the next 30 days unambiguous. The roadmap closes that gap. Keep the next month detailed; sketch the next quarter; treat year 2–3 as a hypothesis you will revise as you learn. Planning the path to a senior or staff promotion. List the gap between your current scope and the target level. Map projects that build evidence at each tier. Schedule monthly check-ins with your manager. Most engineering / PM / design promotions follow this pattern — explicit plans land them; implicit hopes do not. Mapping a career change with bridge work. For larger transitions (engineering → PM, finance → data science), the roadmap covers 6–12 months of focused bridge work plus the actual job-search phase. Visible artifacts at each milestone make the change legible to recruiters when you start applying. Recovering from a stalled career trajectory. When growth has stalled 12+ months, the roadmap forces a decision: stay and engineer the next move internally, or switch companies. Both can work. Drift — neither — is what loses years. Writing the version you will actually re-read. A roadmap nobody opens again is a document, not a plan. Keep it to one page, put the next thirty days at the top where you will see them, and give it a standing date in the calendar. The format matters less than whether the next action is visible without scrolling. Name the target role specifically. Title, level, industry, and 2–3 example companies. "Staff PM at a mid-stage SaaS company" is a target. "Something more strategic" is not. List the gap honestly. What does the target role expect that you do not yet demonstrate? Skills, scope of ownership, mentorship range, public visibility. Be specific; vague gaps produce vague plans. Schedule the next 30 days unambiguously. Pin three specific actions in the next month — a project to scope, a course to start, a person to ask for a 15-minute conversation. The 30-day plan is the part that has to be unambiguous. Sketch the next quarter loosely. Outcomes you expect from the 30-day plan, what they unlock, the next set of actions. Sketch — do not over-engineer. Quarterly plans always need adjustment. Treat year 2–3 as a hypothesis to revise. Long-horizon plans are useful as direction, not commitment. Review monthly; rewrite quarterly; full reassessment annually. Plans that survive contact with reality are the ones that get rewritten as reality changes. A senior engineer planning a path to staff Identifies gap: cross-team scope, mentorship, public visibility. 6-month plan: own one cross-team initiative, mentor two juniors, write three internal blog posts. Promoted at month 9 with clear evidence at each gap area. A teacher planning a career change to instructional design 12-month roadmap: 4 months bridge work (course, capstone curriculum, LMS certification), 4 months portfolio building, 4 months active search. Lands first instructional-design role at month 11; comp drops 10% but trajectory is steeper. Pin the target specifically — vague targets produce wandering plans. The next 30 days must be unambiguous; everything beyond can be sketched. Review monthly; rewrite quarterly; full reassessment annually. A plan that never changes is a plan you stopped updating, not a perfect plan. Drift is the enemy. A wrong plan you adjust beats no plan you stick with. If you cannot find five current adverts for your target role, the target is a category and not yet a role. Checkpoints need evidence somebody else can see — a shipped thing, a review comment, a changed description of you. How far ahead should a roadmap actually plan? Precisely for thirty days, loosely for a quarter, and as a hypothesis beyond that. Detail past a quarter is usually fiction — the market moves, the role changes, and what you want changes with it. The value of the year-two line is that it makes this quarter's choice legible, not that it will turn out to be right. What makes a target role specific enough? You should be able to find five current job adverts for it. If you cannot, the target is a category rather than a role, and every step you derive from it will be vague in the same way. Naming the level as well as the title is part of this — the gap to senior and the gap to staff are different gaps. What do I do when the roadmap and the day job disagree? Change one of them deliberately rather than letting the conflict run. Either the roadmap is aimed somewhere your current role cannot get you — in which case the move is the plan — or the day job could support it with a different project, which is a conversation with your manager. Quietly doing both is the option that reliably fails. How do I know a checkpoint has been met? By something outside your own judgement: a shipped thing, a review comment, a conversation where someone senior described you differently. Self-assessment drifts, usually downward when you are tired and upward when you are not, and a checkpoint that only you can evaluate stops being a checkpoint within a month. My trajectory has stalled. Where do I start? Find out whether it is a visibility problem or a scope problem, because the fixes are opposite. If people cannot see what you do, the answer is to report outcomes where decisions get made; if you genuinely are not doing work at the next level, no amount of reporting fixes it and you need different work. Asking someone senior which one it is usually gets a straight answer. Should a career change roadmap look different? Yes — it needs bridge work in the middle. Moving fields directly is hard because your evidence is in the old domain, so the useful roadmap names an intermediate role that uses what you have and touches what you want. The bridge is the part people leave out, and it is the part that makes the change happen in eighteen months rather than never. ## Skills gap analysis https://clearhire.aoneahsan.com/career/skills-gap Work out which skills your target role expects that your current one does not, and which of them matter most. A skills gap is the distance between what you can do today and what the role you want expects. This page is the framework for closing one — how to find the gaps that matter, how many to take on at once, how to build evidence while you close them, and how to tell when one is actually closed. It is a guide and not an analyser: ClearHire does not scan job listings or rank your gaps for you, and a page that implied it did would be describing a product that does not exist. The ranking you need comes from reading five adverts for the role you want and writing down what appears in most of them, which takes about twenty minutes and is more honest than any score. Building a focused 90-day learning plan. Pick the top 3 gaps from the analyzer. Sequence them — usually 1 hard skill, 1 tooling skill, 1 process skill. 60–90 days of focused practice with one shipped artifact per gap closes more career distance than a year of scattered course-watching. Deciding whether a gap is realistic to close. Some gaps are 3-month closes (a new framework). Some are 12+ month closes (a new programming paradigm, a new domain). Be honest about the time cost before committing. Underestimating closes you cannot afford to make is the most common career-change failure mode. Knowing when a gap is actually closed. When you can ship a small but real project using the skill end-to-end without help, and explain the tradeoffs you made out loud. If you cannot teach it, the gap is not yet closed — you have just been exposed to it. Read five adverts and write down what repeats. Not one advert — five, for the role you actually want, at companies you would actually join. What appears in three or more of them is the market speaking. What appears once is one hiring manager's preference. Mark each one honestly: have it, half of it, none of it. Half is the interesting column. Those are the gaps that close in weeks rather than quarters, and they are the ones people skip because admitting to half feels worse than admitting to none. Pick three, not ten. Usually one hard skill, one tool, one way of working. Above three, depth suffers and none of them reaches the point where you could be questioned about it. Pair each gap with something you finish. A course gets you to working knowledge; a finished thing gets you to something you can be asked about. A certificate on its own answers a question nobody asked. Close it in public, and check it before moving on. A repository, a write-up, a talk — something a stranger can look at. The test for closed is whether you could explain the trade-offs you made out loud, not whether you feel more confident. An engineer closing a systems-design gap 90 days: book + course + 5 paper designs + 1 production-grade side project. Public blog post explaining tradeoffs. Lands senior systems-design interviews at month 4; the visible artifact moved the conversation from "do you know systems design?" to "let's discuss your approach". A career changer underestimating a domain shift Initial plan: 90 days from finance to ML engineering. Realistic plan: 12 months. The honest re-estimation early prevents 6 months of disappointment when the original timeline cannot hold. This is a framework, not an analyser. Nothing here scans listings or scores you. Three gaps, not ten. Focus produces something you can be questioned about; breadth produces a list. Pair every gap with something finished. Course completion on its own rarely moves a conversation. Public evidence compounds; private learning is invisible to everyone but you. The threshold is "could I explain the trade-offs out loud", not "do I feel productive". Some gaps close in a month and some take a year. Being wrong about which is which is the expensive mistake, not being slow. How do I find which gaps actually matter? Read five current adverts for the role you want and write down what repeats. A skill named once is one company's preference; a skill named in four of five is what the market means by that role. This takes an hour and it replaces guessing with counting, which is the whole method. How many gaps should I take on at once? Three. A list of ten is a way of not starting, and progress on ten simultaneous fronts is invisible on all of them. Three is small enough to finish and large enough that finishing changes what you can apply for, which is the point. Does ClearHire analyse my skills gap for me? No. This is a guide, not an analyser — ClearHire holds no dataset of skills by role and does not rank gaps by frequency in live listings. The reading exercise above is the manual version of that, and it has the advantage that you see the adverts yourself rather than trusting a summary of them. How do I know when a gap is closed? When you have finished something with it that someone else can look at. A course completion certificate says you attended; a working thing says you can do it, and it is also what you will talk about in the interview. If you cannot point at an artefact, the gap is narrower than it was and not yet closed. What if a gap is not realistic to close? Decide that explicitly and adjust the target, rather than leaving it on the list. Some gaps need years, a different job, or a credential you are not going to pursue — and a plan carrying an item nobody intends to do quietly discredits the rest of it. Either the target changes or the timescale does, and saying which is the useful outcome. Should I close gaps in public? Where you can, yes, because it does two jobs at once. Working in the open — a repository, a write-up, a talk — creates the evidence you would otherwise have to assert, and it tends to raise the standard you hold yourself to. The exception is anything involving an employer's work, which needs permission first. ## Challenges https://clearhire.aoneahsan.com/challenges Small nudges toward the things that actually make a job search work — a finished profile, a role a company has confirmed, an answer someone else could use. Levels unlock features in ClearHire. They unlock nothing outside it. Small nudges toward the things that actually make a job search work — a finished profile, a role a company has confirmed, an answer someone else could use. Levels unlock features in ClearHire. They unlock nothing outside it. It does not make a record more verified, it does not move you up anyone's list, and it is not shown on your public profile unless you turn on the one line at level 6. Verification is a company answering a question about you — nothing on this page can substitute for that, and if it ever looks like it can, this feature is doing harm. Six rungs. Everything unlocked is a feature inside ClearHire — a slot, a limit, a link. None of it is a signal to an employer. Five, not fifty. Each one is a thing worth doing even if this page did not exist, which is the only test a challenge has to pass here. {{earned}} earned of {{total}}. Every badge states its requirement whether or not you have it. ## Leaderboard https://clearhire.aoneahsan.com/challenges/leaderboard Off unless you switch it on. Nobody is listed by default and nobody is counted by default, which is why the totals below are smaller than the number of people using ClearHire. Off unless you switch it on. Nobody is listed by default and nobody is counted by default, which is why the totals below are smaller than the number of people using ClearHire. You can turn this off at any time and you disappear immediately — from the list and from the totals. It does not make a record more verified, it does not move you up anyone's list, and it is not shown on your public profile unless you turn on the one line at level 6. Verification is a company answering a question about you — nothing on this page can substitute for that, and if it ever looks like it can, this feature is doing harm. ## Company directory https://clearhire.aoneahsan.com/companies Companies on ClearHire, each marked with one checkable fact: whether it answers when somebody asks it to confirm a role from its own employment records. A company directory is usually a list of logos. This one records one extra fact, and it is the only fact ClearHire can actually observe: whether the company answers when somebody asks it to confirm a role from its own records. Not whether it is a good employer. Not whether it pays well. Not a rating. Companies that have never been asked sit here too, marked as never asked, because a company nobody has approached has done nothing wrong. There is no star rating on a company card and there will not be one. A number that averages a workplace tells you less than one honest sentence about it, and it invites the gaming that makes every review site useless. Sort order is a sort order. Nothing on this page is a recommendation, a shortlist, or a paid position — companies cannot buy placement, and no company has been asked for money to appear. A company appears here the first time somebody claims a role at it — the claim creates the profile, and the company can take it over afterwards. Nothing is listed by scraping. ## Contact ClearHire https://clearhire.aoneahsan.com/contact One inbox, read by the team. Bug reports, corrections, verification questions and data requests — usually answered within a few days. Everything sent to ClearHire reaches one inbox. The ClearHire team reads it. There is no support desk and no ticket number, which is slower than a help centre and rather more useful. Bug reports, corrections to any page on this site, questions about a verification, and data or privacy requests all go to the same place: aoneahsan@gmail.com, or +92 304 6619706. Several questions are answered faster by a page than by an email — what a verified record asserts, what is stored in your browser, and how to delete an account yourself. ## Cookies and browser storage https://clearhire.aoneahsan.com/cookies Every key and cookie in your browser, listed with what it holds and who wrote it — ClearHire, or one of the four analytics providers. The page reads your browser back to you so you can check it. ClearHire stores its own appearance preferences and your pinned tools in the browser’s localStorage, under keys prefixed clearhire:, and writes no cookie for any of them. The analytics providers it loads do write cookies, four of them on this domain, and clause 10 names every one. The difference matters: a cookie is sent to the server with every request and can be set by a third party embedded in a page, which is how cross-site tracking works at all. A localStorage entry never leaves the browser unless a script on the same site reads it. Every key is listed with what it holds and what it changes, and the page reads your own browser back to you so the list can be checked in about thirty seconds rather than believed. ## Which shape of cover letter you need https://clearhire.aoneahsan.com/cover-letter-templates There are four situations and they want four different opening moves. Picking the shape first is most of the work — the generator does the rest. Most cover letter advice is about tone, and tone is the last thing to worry about. The first thing is shape: a letter answering a posted advert, a letter arriving with nobody expecting it, a letter that leads with the name of the person who suggested it, and a letter that has to address a change of field before the reader supplies their own explanation. Those four open differently, ask differently and close differently, and picking the wrong one produces a letter that is well-written and slightly beside the point. This page is about choosing between them. There is no template gallery here and there is not meant to be: the shipped version of ClearHire had two template catalogues that disagreed with each other, which is worse than none, so there is one generator and this is the page that tells you what to ask it for. You are answering an advert. The most common case and the simplest. The reader knows why you are writing, so the opening does not have to justify itself — it has to be specific quickly. Nobody advertised anything. A speculative letter has to acknowledge that it may be badly timed, because pretending otherwise reads as not having checked. Saying so costs nothing and buys the reader's attention. Somebody suggested you write. The referrer's name belongs in the first line, where it does its work. Halfway down the second paragraph it is a detail; at the top it is the reason the letter is being read at all. You are changing field. Address it early and plainly. A reader who notices the gap before you mention it spends the rest of the letter building their own explanation, and it is rarely the generous one. Writing the one nobody asked for. An unsolicited letter has a harder job than any other kind: it must justify its own existence in the first line. What works is specificity about them rather than about you — something they are doing, a problem you can see, a reason it is this company and not forty others. Anything that reads as a template will be treated as one. Pick the shape before you write a word. Advert, speculative, referral, or change of field. Everything else follows from this, and it is the one decision that cannot be fixed by editing. Decide the one thing you want remembered. A letter is remembered as a single claim, so choose it deliberately rather than letting the reader pick. Something with a number in it if you have one, written the way you would say it out loud. Say whether you know anything real about the company. If you have something specific and true, one sentence is enough. If you do not, leave it out entirely — a generated compliment reads as generated, and every reader has seen a hundred of them. Keep it to three or four paragraphs. Greeting, why you are writing, the thing you want remembered, and a close. A fifth paragraph is almost always the one that repeats the resume. Read it aloud before you send it. Anything that sounds unlike you probably is. The letter's job is to make a conversation likely, and a voice the reader cannot match to the person in the interview works against that. A speculative letter that opened like an advert reply It read as though a posting had been missed, which made the writer look careless rather than enterprising. Naming the situation in the first sentence — no advert, may be badly timed, happy to be told so — turned the same letter into a reasonable approach. A referral buried in paragraph three The person who suggested the letter was the reason it would be read, and their name arrived after the reader had already decided how much attention to give it. Moving it to the first line changed nothing else about the letter. Leaving the company name out is a real choice, not an unfinished letter. The result addresses the team rather than pretending to know one. One claim, not four. A letter listing everything you have done is a resume with worse formatting. The close should be easy to say yes to. "Happy to talk whenever suits" asks for less than "I look forward to discussing how I can add value". Never let a generator invent a company fact, an achievement or a reason you admire someone's work. Everything specific should be something you typed. A cover letter cannot rescue a resume the reader has already discounted. If the resume is the problem, fix that first. There is one generator and one set of shapes, deliberately. Two catalogues that disagree is how the previous version of this product ended up giving two different answers to the same question. How do I choose which shape of letter to write? By how the reader came to have it. A letter answering an advert, a letter nobody asked for, a letter following a referral and a letter explaining a change of field are four different documents, and the opening move differs in each. Getting the shape right is most of the work; tone is the smallest part and the part most advice is about. Does anyone actually read cover letters? Some readers do and some never will, and you cannot tell which in advance. That asymmetry is the whole argument for writing a short one: it costs you fifteen minutes and it is the only place you get to explain something a resume cannot carry — a change of direction, a gap, a specific reason for this role. How long should it be? Short enough to read in under a minute — three or four short paragraphs. A letter that restates the resume at length gets skimmed to nothing, and the parts worth reading are lost in it. If you cannot say the useful thing in four paragraphs, the useful thing has not been identified yet. What should the first sentence do? Give the reader the reason this letter exists. For a referral that means the name, immediately, because it changes who is reading; for an advert it means the specific thing about the role that made you write. What it must not do is announce that you are writing to apply, which the reader already knows. Should I mention salary or availability? Only if they asked. An unrequested salary expectation anchors a conversation that has not started, and availability belongs in the reply to the first email rather than in the letter. If the advert explicitly asks for either, answer it plainly and briefly — ignoring a direct instruction is a worse signal than any number. Is it worth writing one for a field change? It is the case where it matters most. A resume in a different domain gives a reader nothing to connect, and the letter is the only place you can say what transfers and why the move is deliberate rather than a retreat. Without it, the reader constructs their own explanation, and it is usually less generous than yours. ## Delete your account https://clearhire.aoneahsan.com/data-deletion Immediate, permanent, and yours to trigger. Three different fates for your data — and the two record types that survive are named before you start. Deleting a ClearHire account happens immediately: no support ticket, no waiting period and no recovery window. Data has three fates rather than one. Most of it is deleted outright from the database and from file storage. Forum posts and comments are anonymised rather than removed, because deleting a post strands every reply to it. Two record types survive — identity-verification disputes and abuse reports — because a dispute erasable by deleting the account that caused it would make deletion a tool for hiding fraud. A company that countersigned an employment record keeps its own record of what it confirmed. Deleting a ClearHire account removes the record from ClearHire; it does not reach into a former employer’s files. ## Employment gap explainer https://clearhire.aoneahsan.com/employment-gap Add each period, say what you did with it, and get a resume line, a letter paragraph and an interview answer made of your own words. ## Questions https://clearhire.aoneahsan.com/faq Short answers to what people ask before they trust ClearHire — including the unflattering ones about employers who never reply and replies that take days. ClearHire is career tools, a resume builder, and employment history a named company can confirm. Most tools work with no account at all. A verified employment record proves that someone at your former employer confirmed the company, the job title and the dates from their own records. Nothing else. If nobody answers within seven days the record is marked expired — unconfirmed, never declined — and can be sent again. Free is not a trial and does not expire, and verified employment is on Free and stays there. Pro raises volume and convenience limits and never buys credibility. ## Feed https://clearhire.aoneahsan.com/feed Everything that changed on ClearHire, newest first — new writing and updated reference pages in one chronology. The ClearHire feed is one chronology of everything that changed: new writing and updated reference pages together, newest first, rather than a separate list for each. There is no newsletter and no tracking pixel. An RSS feed at /feed.xml carries the same entries and is generated on every build from the same content. ## Forums https://clearhire.aoneahsan.com/forums Questions about interviewing, resumes, offers and verification, answered by people who have been through them. Moderated by a person, with the rules written down before you post. Questions about interviewing, resumes, offers and verification — answered by people who have been through them. A person reads every report; nothing here is removed by a machine. Six sections, chosen so a question lands where the people who can answer it are already reading. Post counts are the whole section, not this week. Four rules, and what each one is for Nobody here can check a claim about a named individual, so a post that makes one is removed. A post about a company's process is fine. Recruiters and vendors are welcome to answer questions. Posting a vacancy here is removed and repeats cost posting access. No screenshots with names, email addresses or phone numbers still legible in them. Crop them or describe what they said. A reply that only goes after the person is removed whether or not the point underneath it was right. Written out because a report you cannot track feels like a report nobody read. ## Get involved https://clearhire.aoneahsan.com/get-involved Four things that actually help, none of which needs an account — and one thing this page used to collect and no longer does. The ClearHire team is not hiring, so this page asks for nothing. What helps instead is telling us where a page is wrong, reporting a bug, asking a former employer to confirm a role, or supporting the work. The previous version of this page was a sign-in-gated form that collected a name, an email address and an area of interest and wrote them to a table. There was no pipeline for those submissions to enter, and collecting personal data for something that is not happening is exactly what the about page calls out by name. ## How employment verification works https://clearhire.aoneahsan.com/help/verification What ClearHire asks a former employer to confirm, what it does not ask, and what appears on your record afterwards. Employment verification is ClearHire asking a company you say you worked for to confirm three facts from its own records: the company, the job title, and the dates. It is optional, it is one request at a time, and the company needs no ClearHire account — they answer from a link in an email. What the confirmation asserts is deliberately narrow, and clause 05 of the terms is the exact wording: it is not a reference, not a background check, not an identity check, and not a statement about why the employment ended. An unverified role still sits on your profile and still goes on a resume; it simply has no countersignature beside it. Asking a former employer to confirm a role. Pick the roles that matter to what you are applying for rather than every role you have held. The company receives a request naming exactly what is being confirmed, and answers yes, corrects a detail, or declines with a reason. Answering one as the company. You do not need an account and you are not signing up to anything. You are asked to check the claim against your own employment records and confirm, correct or decline — never for an opinion, a rating or a reason the employment ended. Your name, your role and the date are recorded with the answer and shown on the record, and that is stated before you answer rather than after. When nobody answers. A company has seven days. If nobody answers, the record is marked EXPIRED — unconfirmed, never declined and never false. Most requests that fail reach an inbox belonging to somebody who left. You can send it again, which starts a fresh seven days, and every attempt stays on the record rather than the first one being quietly forgotten. When the answer is no. A declined record is private: you, the company and ClearHire. It never appears on a public profile, is never shown to an employer, and is never counted against you anywhere in the product. Most declines are a disagreement about a date rather than a denial that you worked there — payroll often holds a start date HR does not. Choose the roles worth confirming. The ones that carry the claim you are making. Verifying everything you have ever done is work for you and for four companies, and it does not make the relevant role more confirmed. Send the request to a person who can check. Someone with access to the company's employment records. It must be an address on the company's own domain. A personal address cannot countersign employment, and a request that reaches nobody expires exactly like one that is ignored. Seven days run, and then the request expires. Not fails — expires, and the record says unconfirmed. That distinction is deliberate: silence is not an answer, so it is not recorded as one. Send it again if you want to. A fresh request means a fresh seven days. Every attempt is kept, because a record that hid its earlier attempts would be telling a partial story about itself. Dispute it if the company got it wrong. A person reads a dispute and replies. We will not change a company's answer without asking them, and we will never remove their record of what they confirmed — a confirmation that could be withdrawn without trace would be worth nothing to anybody reading it. Three roles, two answers and a silence Two companies confirm inside the week. The third never answers, so that record is marked expired — unconfirmed rather than rejected — and the role still appears on the profile without a countersignature. Nothing about the silence is shown to anyone or counted against the person. A date the company records differently The company corrects the start month rather than declining, because correcting is one of the three answers the form offers. The record shows the company's dates and who corrected them. Seven days, and then it expires as unconfirmed. Never as declined, and never as false. A decline is private to you, the company and us. It is not published anywhere, in any form. A confirmed record proves the company, the title and the dates — and who confirmed it, in what role, on what date. It proves nothing else, and clause 05 of the terms says so in more words. The company answering sees only the role they are confirming: not your other roles, not your applications, not your profile. Send requests before you need them. A company routing an unfamiliar request internally is slower than a person answering one. If the company no longer exists, the role stays unconfirmed. That is a limit of the product rather than a problem with you, and most people have several. What exactly does ClearHire ask my former employer? Three facts from their own records: the company, the job title, and the dates. Nothing else. It does not ask about performance, reason for leaving, salary, eligibility for rehire, or anything a reference would cover — and the request itself says so, so the person answering can see the scope before they reply. Does my former employer need a ClearHire account? No. They answer from the link in the request, in a browser, without signing up for anything. Requiring an account would mean the request depended on somebody at a company you no longer work for choosing to register, which is the point at which most verification systems quietly stop working. What happens if nobody answers? After seven days the request expires as unconfirmed, and that is a different state from refused. Nothing appears on your record claiming the role was disputed, because silence is not a denial — companies restructure, people leave, and inboxes are full. You can send a fresh request afterwards and each attempt starts its own seven days. Can I re-send a request that expired? Yes, as many times as you like, and every attempt is kept. Re-sending starts a fresh seven-day window rather than extending the old one, and the history of attempts stays on the record — which matters, because "asked four times over a year" is itself information about how hard you tried. What if the company says no? A decline is recorded privately and does not appear on your public record as a mark against you. It also does not confirm the role, so the entry stays unverified. A company can decline for reasons that have nothing to do with you — many have a policy of confirming nothing, and some no longer hold records that far back. Can an employer add something I did not ask them to? No. The answer is constrained to confirming, correcting or declining the three facts in the request. There is no free-text field for a former employer to attach an opinion, because a verification that could carry one would be a reference with fewer safeguards — and nobody would ever send the first request. Is verification required to use ClearHire? No. It is optional, per role, and an unverified history is a completely normal thing to have — most of the product works without it. Verification is there for when a confirmed fact is worth more to you than an asserted one, which is usually at the point somebody is deciding between you and someone else. ## Benefits guide https://clearhire.aoneahsan.com/insights/benefits What sits in a typical benefits package, what it is worth in cash terms, and which parts are usually negotiable. Employee benefits in 2026 cover health insurance (medical, dental, vision), 401(k) or pension matches, equity or stock plans, paid parental leave, paid time off and sick leave, flexible or remote work, professional development stipends, and mental-health support. The cash-equivalent value of a strong benefits package can equal 20–40% of base salary, which means evaluating offers on base alone consistently undersells the better package. This guide covers how to value, compare, and negotiate benefits in real numbers rather than headline impressions. Comparing two offers with very different benefits. Calculate cash-equivalent: employer 401(k) match + health-premium difference + PTO days × daily rate + equity grant ÷ vesting years + parental-leave value + signing bonus. Add to base for total comp. The headline-higher offer often loses on total. Quantifying the value of remote work. Estimate commute hours saved × hourly rate plus eliminated childcare and office-clothing costs. Most candidates find a 10–20% effective uplift from genuine remote-work benefits — meaningful but often invisible in offer comparisons. Negotiating benefits the offer did not include. Common asks once base is capped: signing bonus, additional PTO, remote-work allowance, professional-development budget, equity refresher. Frame each ask as helping you accept rather than as a demand. Understanding what "unlimited PTO" actually means. Unlimited PTO is often less generous than 4–5 weeks fixed because culture pressure reduces actual usage. Ask the recruiter what the average employee took last year. If the answer is "10 days", treat it as a 10-day plan, not unlimited. Working out what a benefit is worth to you specifically. The same package is worth different amounts to different people. Family health cover matters enormously with dependants and barely at all without them; a learning budget is real money to someone who buys courses and zero to someone who does not. Price each line against what you would otherwise spend, not against what the employer spends. Get the full benefits document, not just the offer summary. Recruiters summarize; the actual benefits document specifies waiting periods, vesting cliffs, contribution limits, and exclusions. Numbers in the summary often miss material limitations. Calculate cash-equivalent for each line item. Match × your contribution × likelihood you stay through vest. Health: difference between employer-paid premium and what you would pay individually. PTO: days × daily rate. Add cash-equivalent to base for total comp. Total = base + bonus target × hit rate + signing bonus + first-year equity vest + cash-equivalent of benefits. This is the number you compare across offers. Identify the negotiable benefits. Health and 401(k) are usually fixed by HR policy. Signing bonus, equity, PTO, remote allowance, and professional development are typically more flexible — these are where negotiation works. Negotiate the negotiable lines after the offer. Ask once, with specifics. "Could we look at adding a $5K signing bonus, an extra week of PTO, or a $2K professional-development budget to bridge the gap?" Pick one lever, not three. A candidate weighing $180K base + 4% match vs. $170K base + 6% match + $20K signing bonus Calculates total: offer A = $180K + $7,200 match = $187,200. Offer B = $170K + $10,200 match + $20K signing = $200,200 in Year 1. Offer B wins despite the lower headline base. A parent evaluating "unlimited PTO" vs. fixed 25 days Asks the recruiter what employees actually took last year — answer is 11 days. Treats unlimited as 11-day equivalent, which loses to 25 fixed days. Negotiates the 25-fixed offer instead. The cash-equivalent of benefits commonly equals 20–40% of base salary — never compare offers on base alone. "Unlimited PTO" is often less generous than fixed PTO; ask for the average actual usage. Equity in late-stage / public companies is real comp; in early-stage startups, treat it as upside lottery. Match the 401(k) contribution to capture the full employer match — not doing so is leaving free money. Parental-leave policy details matter more than the headline number — paid vs. unpaid, eligibility waiting period. How do I put a cash value on a benefit that is not cash? Price the thing it replaces. A health plan is worth what the equivalent cover would cost you privately, minus your share of the premium; a retirement match is worth the match itself, because it is money you would otherwise have to save from post-tax income; a learning stipend is worth what you would have paid for the course. Anything you would not have bought yourself is worth nothing to you, however much it costs the employer — a gym membership you will not use is not compensation. Is a bigger base always better than better benefits? No, and the gap is often larger than people expect. Benefits are usually pre-tax and always employer-funded, so a dollar of retirement match or premium contribution is worth more to you than a dollar of base pay after tax. The exception is anything with a vesting cliff or a use-it-or-lose-it condition: a benefit you have to stay three years to collect is worth its face value multiplied by the odds you actually stay. Which benefits are actually negotiable? The ones that are not administered as a company-wide plan. Start date, remote or hybrid arrangement, signing bonus, learning budget, equipment, extra leave and title are usually decided by the hiring manager or the recruiter and can move. Health plan design, retirement match percentage and the holiday allowance are typically set for everyone and cannot; asking for those signals you have not understood the structure, which costs you credibility on the lines that could have moved. What does unlimited PTO usually mean in practice? It usually means there is no accrued balance to pay out when you leave, and no number anybody can point to when they want time off. Whether it is generous depends entirely on what managers model. Ask two specific questions in the interview: how many days did the team take last year, and does anyone track it. A vague answer to both is the answer. Should I ask about benefits before or after the offer? Ask what the package contains during the process, and negotiate it after the offer. Knowing the shape early lets you compare fairly and avoid discovering at the end that the retirement match is zero; pushing on specific lines before anyone has decided to hire you shifts the conversation away from whether you are right for the role. The one exception is a benefit that would make the job impossible — a childcare constraint, a location requirement — which belongs in the first conversation. How do I compare offers in different countries or states? Compare what is left after tax and after the things the employer does not cover. A package with no health contribution in a country with public healthcare is not worse than one with a large contribution where cover is private and mandatory; a higher gross in a high-tax jurisdiction can be a lower net. Build the comparison as an annual net figure plus the cash value of the benefits, and write down the assumptions, because the assumptions are where two people looking at the same two offers disagree. ## Company culture https://clearhire.aoneahsan.com/insights/culture What a culture rating is measuring, what it cannot measure, and how to read one without over-trusting it. Company culture is the set of decisions, behaviors, and unwritten rules that determine how work actually gets done — separate from what the company says about itself in marketing materials. Culture mismatch is the leading reason for early voluntary departure; it is also the leading reason high performers stall. This guide covers how to research culture before applying, what red flags to watch in the interview process, the differences between remote-first and in-office cultures, and how long to give a new culture before deciding it is wrong. Researching culture before applying. Read company values plus 6+ months of employee reviews; look for repeating patterns, not single complaints. Check leadership tenure on LinkedIn for turnover. Ask culture-specific questions during interviews about decision-making and conflict resolution. Spotting interview-process red flags. Vague answers about work-life balance, evasiveness about turnover, same-day decision pressure, badmouthing of past employees, no diversity in leadership, ghosting between rounds. None is independently disqualifying; three or more together is. Choosing between remote-first and in-office cultures. Remote-first optimizes for written communication, async decisions, and outcome-based reviews. In-office leans on hallway conversations, real-time meetings, and presence-based perception. Match the model to how you work best, not which is trendier. Deciding whether a new culture is the wrong fit. Give 90 days for the basic rhythm and 6 months for a real read. If something feels seriously wrong (harassment, ethics issues, sustained 60+ hour weeks), act immediately — not all cultures get better with time. Reading a culture page for what it does not say. A careers page describes the company it wants to be. Read it for omissions instead: no mention of how disagreements are resolved, no named person accountable for anything, values that could belong to any company in any industry. What a company chooses not to be specific about is usually where it is least confident. Read 6+ months of employee reviews and look for patterns. A single complaint about a manager means little; ten reviews complaining about the same VP across two years is signal. Pattern-recognize across reviews rather than reading any single one. Check leadership tenure on LinkedIn. High turnover at director level and above is a real signal. If three of five VPs joined within the last 12 months, that is worth probing in the interview. Ask culture questions in the interview. "How are decisions made when there is disagreement?", "What does the company do well that other companies do badly?", "When did you last see a value live in action?". Answers matter more than questions. Talk to a current or former employee outside the interview. Reach out via LinkedIn for a 15-minute chat. People are surprisingly candid in 1:1 conversations they did not initiate. Single conversations carry more signal than ten interview answers. Decide based on accumulated evidence, not first impression. Make a written list of evidence for and against fit. Decisions made on gut alone are biased toward whichever interaction was most recent. Written evidence smooths the bias. A candidate noticing three red flags in one round Vague work-life balance answer, evasive turnover question, and same-day decision pressure. Declines the offer. Six months later, a friend at the company confirms the culture concerns. A candidate giving a new culture 90 days before judging First two weeks feel chaotic. By day 60, patterns become legible. By day 90, the candidate has a clear read and decides the chaos is intentional and energizing rather than dysfunctional. Single complaints in reviews are noise; repeating themes are signal. Look for patterns across 6+ months. High director / VP turnover is a leading indicator — leadership churn precedes broader culture shifts. Talk to one current and one former employee for the most balanced read. Give 90 days for rhythm, 6 months for full read; act immediately on serious red flags. Match remote vs. in-office to how you actually work, not which is currently fashionable. How many employee reviews do I need to read before the picture is real? Enough to see whether a complaint repeats, which in practice means six months or more of them rather than a fixed count. A single review tells you about one person's experience with one manager. The same complaint from five people across two years tells you about the company. Read for repetition and for what the positive reviews carefully avoid saying, which is often more informative than the negative ones. What is the difference between culture and perks? Perks are what a company buys; culture is what it rewards. A company can have excellent snacks and still promote only the people who answer messages at midnight, and that second fact is the one that will shape your week. When you research culture, look for decisions — who got promoted, what happened when a project failed, how disagreement is resolved — rather than for amenities. Are red flags in the interview process reliable? Individually no, together yes. Any one of a rescheduled interview, a vague answer about hours, or an interviewer who has not read your CV can be an ordinary bad week. Three or more in one process is a pattern, and the process is the part of the company most motivated to look good — it is the best behaviour you will see. Treat it as the ceiling, not the average. How do I ask about culture without getting a rehearsed answer? Ask for an instance, not a description. "How are decisions made when people disagree?" gets you the handbook; "tell me about a recent decision the team disagreed on, and how it landed" gets you the company. Follow-up questions about a specific story are hard to prepare for, which is exactly why they are worth asking. How long should I give a new culture before deciding it is wrong? Give ninety days for the rhythm and about six months for a real read, with one exception. Most new jobs feel chaotic for the first month because you do not yet know what is normal, and the things that irritate you in week two are often just unfamiliarity. Harassment, ethical problems and sustained unsustainable hours are not that, and none of them improve with patience — those are worth acting on immediately. Is remote-first culture better than in-office? Neither is better; they reward different things. Remote-first companies run on written communication, asynchronous decisions and outcomes you can point at, which suits people who write well and dislike being interrupted. In-office cultures run on conversation, real-time resolution and visible presence, which suits people who think out loud and build relationships face to face. Pick the one that matches how you actually work rather than the one that sounds more modern. ## Growth metrics https://clearhire.aoneahsan.com/insights/growth The company growth indicators that appear in job adverts and press coverage, and what each one actually tells you. Career growth happens on two axes: moving up inside a company, and moving across to another one. Internal growth is faster when your work is visible, when you own something end to end, and when somebody senior has said out loud what the next step requires. External moves often pay better and reset the ladder at the same time, which is a real cost people notice in year two rather than in month one. This page is about telling which of the two you are actually facing — because the honest answer is usually visible in whether anyone can name what would have to change for you to be promoted, and that is a question you can ask. Engineering a promotion you have stalled on. Make work visible (regular write-ups, demos), own a critical project end-to-end, mentor more junior teammates, partner with adjacent teams, and have an explicit promotion conversation with your manager naming the gap and the timeline. Asking for a raise without an offer in hand. Document outcomes (shipped projects, dollars saved or earned, processes improved), compare your salary to the market range, schedule a 30-minute meeting framed as career planning rather than negotiation, and ask for a specific number with reasoning. Choosing whether to switch companies. Switch when growth has stalled 12+ months, promotion paths are blocked, or external offers are 20%+ above current with comparable scope. Stay when you have momentum, a strong manager, and the next role is in reach within a year. Building network capital for long-term growth. Most senior roles never hit a public job board — they are filled via referrals. Maintain weak ties (occasional check-ins, sharing useful articles) over time. You do not need a transactional network, just a continuous one. Make your work visible. Weekly written updates to your manager. Quarterly demos to the broader team. Regular check-ins with your skip-level. Invisible work does not get rewarded; visible work compounds. Own a critical project end-to-end. End-to-end ownership beats partial contributions in promotion conversations. Pick a project you can drive from scope through ship, even if it takes 6 months. Half-finished work is not promotion-grade. Have the explicit promotion conversation. Schedule a 30-minute meeting with your manager. Ask: "What is the gap between my current scope and the next level?". Get specifics. Build a 6-month plan to close them. Review monthly. Test the external market periodically. Even if you do not plan to leave, take 1–2 calls per quarter with recruiters. Knowing your real market rate strengthens internal negotiation and exposes when you are being underpaid. Decide based on a year-out comparison, not 6 months. Switching for 10% pay and a worse manager is a bad trade in year 2. Compare projected scope, learning, and trajectory at year 1, not just the headline offer at month 0. An engineer stalled at senior for 18 months Asks for the explicit gap, owns one critical project end-to-end, builds three monthly demos, and gets promoted to staff at month 8. Total comp jumps 22%. A PM with a strong internal trajectory but a 30%+ external offer Compares year-1 and year-2 projected total comp at both. Internal trajectory wins year 2 because of equity refresher; declines the external offer despite higher year-1 cash. Six months later, the calculation pays off. Make the work visible. Quiet competence is indistinguishable from absence to anyone more than one desk away. Own something end to end. A contribution to five things reads as help; one finished thing reads as ownership. Ask what would have to be true for the next step, and write the answer down. A manager who cannot name it has told you something. Moving companies often pays better than waiting for an internal promotion — but by how much depends on your market and your level, and any single percentage you read is somebody else's population. Test the market occasionally even when you are happy. An offer you decline is information; an offer you need is leverage you no longer have. Compare the year-two position, not the month-one one. Pay, scope, the manager and what you would be learning — a raise into a worse job is a bad trade that takes a year to feel. Why do external moves usually pay more than internal promotions? Because an internal raise is negotiated against your current salary and an external offer is negotiated against the market. A company deciding what to pay you already has an anchor — what it pays you now — and a percentage increase from that anchor rarely reaches what a new employer would offer to win you from scratch. That is a structural feature of how both decisions get made, not a judgement about how much anyone values you. What does it actually take to be considered for promotion? Someone senior needs to have said out loud what the next level requires, and you need to be visibly doing it already. Promotions are usually confirmations of a change that has already happened rather than bets on one that might. If nobody has told you the criteria, that is the first conversation to have, and the answer is worth writing down so you can hold it up later. How do I make my work visible without being insufferable? Report outcomes rather than effort, and do it where decisions are made. A short written update naming what changed and what it was worth reads as useful; a running commentary on how hard you are working reads as noise. Writing things down also has a second effect that matters more than the first: it makes your contribution legible to people who were not in the room, which is most of the people who will be asked about you. Is it worth interviewing elsewhere if I do not want to leave? Yes, periodically, and it is the cheapest calibration available. Interviewing tells you what the market pays for what you can do now, which is information you cannot get any other way and which decays quickly. The caveat is honesty: do not take a process to the offer stage purely as leverage if you have no intention of considering it, because the person on the other side spent real time on you. When is the right time to switch companies? When you have stopped learning and the conversation about what comes next has stalled twice. One stalled conversation is a bad quarter; two is a pattern, and staying past that point tends to cost more than the move would. Compare a year out rather than six months out — a new job is worse than your current one for the first few months almost regardless of whether it was the right decision. Does staying at one company for a long time hurt a resume? Not by itself, but a long tenure with no visible change does. What a reader is looking for is progression: different scope, harder problems, more responsibility. Eight years in one company across three genuinely different roles reads well. Eight years doing the same job reads as eight years of the first year, and the fix is to describe what changed rather than to leave. ## Interview processes https://clearhire.aoneahsan.com/insights/interviews What a hiring process usually looks like by role, stage by stage, so an unfamiliar one is not a surprise. Interview performance follows from preparation more than talent. The candidates who land offers are not always the most experienced — they are the ones who arrive prepared with specific stories, researched questions, and rehearsed answers to predictable questions. This guide covers behavioral preparation (the STAR format and 6–8 stories that map to multiple competencies), technical preparation (30–50 problems plus 5 system designs), the universal opening question, the questions you should ask the interviewer, and how to follow up after. Preparing for behavioral rounds. Write 6–8 stories from the last 3 years using STAR (Situation, Task, Action, Result). Each story should map to multiple competencies. Practice telling each in 90 seconds out loud. Record on phone video and watch playback for filler words and run-ons. Preparing for technical rounds. Solve 30–50 problems in your target language. Focus on patterns: two pointers, BFS / DFS, dynamic programming, sliding window, top-K. For systems: practice 5 common designs (URL shortener, news feed, chat, rate limiter, file storage). Nailing "tell me about yourself". Use a 60–90 second structure: present role and scope, two or three career highlights tied to skills the role needs, the reason you are interested in this specific role. Skip childhood, school, and unrelated jobs unless directly relevant. Asking questions that signal genuine interest. Ask 2–3 of: "What does success in this role look like at 6 / 12 months?", "How is performance measured?", "What is the team's biggest current challenge?", "How would you describe the manager's style?". Avoid questions Google can answer. Following up so you stay top of mind. Thank-you email within 24 hours referencing one specific topic from the conversation. Restate one reason you are a fit. Confirm interest. Under 150 words. If the timeline they gave passes, follow up once. Build the story portfolio first. 6–8 stories spanning leadership, conflict, ambiguity, failure, mentoring, deadline pressure, cross-team work. Tag each story with the competencies it covers so you can reuse stories across questions. Write each story in STAR format. Situation (1 sentence context), Task (1 sentence what you owned), Action (3–4 sentences what you specifically did), Result (1–2 sentences with metrics). Action is the longest; Situation is the shortest. Practice out loud and time-boxed. Record yourself answering on phone video. Watch the playback for filler ("um", "like"), run-ons over 2 minutes, and missing context. Re-record until each answer lands cleanly in 90 seconds. Prepare 3–5 specific questions per interviewer. Generic questions ("what is the culture like?") signal generic preparation. Specific questions ("how did you decide to spin off the platform team last year?") signal real research. Send the thank-you within 24 hours. Reference one specific topic. Restate one reason you are a fit. Confirm interest. Under 150 words. Sent same-day if the interview was in the morning, next-day if late afternoon. A candidate with strong experience but inconsistent interview performance Builds 8 stories, records each on video, watches playback, re-records, and lands offers at 4 of 6 final-round companies — up from 1 of 5 the prior cycle. The change is preparation, not skill. A candidate doing 30 minutes of pre-interview research Reads recent news, leadership posts, and one engineering blog post. Mentions one specific recent shift in the conversation. Interviewer flags them as "clearly did the work" in feedback. A candidate who prepared six stories and was asked about a seventh competency Asked about handling ambiguity, which they had not prepared for, they reused the migration story they had built for conflict and led with the part where the requirements were unclear. It worked because the story was known well enough to be re-cut, which is the argument for depth over coverage. "Tell me about yourself" opens most interviews. Have a tight sixty-second answer ready rather than discovering it live. Record yourself answering questions on phone video. Playback reveals patterns you cannot hear live. Prepare 3–5 questions per interviewer; specific beats generic every time. Thank-you email within 24 hours; one specific topic; under 150 words; no exceptions. If the timeline they gave passes, follow up once — not twice. Two follow-ups is the cutoff. How many stories do I actually need prepared? Six to eight, chosen so each one can answer several different questions. Interviewers ask about conflict, failure, leadership, ambiguity and influence, and a single well-chosen project usually contains at least three of those. Preparing twenty shallow stories is worse than preparing six you can tell precisely, because under pressure you will reach for whichever one you know best anyway. What makes a STAR answer good rather than merely complete? The result, stated specifically, and the part where you say what you did rather than what the team did. Most answers spend too long on situation and task — the setup — and run out of time before the outcome, which is the only part the interviewer is actually assessing. Aim for roughly a quarter of the answer on context and the rest on action and result. Should I rehearse answers out loud or just think them through? Out loud, and timed. Thinking an answer through feels complete and takes about a third as long as saying it, which is why rehearsed-in-your-head answers run to four minutes in the room. Saying it aloud also surfaces the sentences that do not survive contact with speech, and those are the ones that make an answer sound recited. What should I ask my interviewer? Something only that person could answer. A question about the team's biggest current disagreement, or what they wish they had known before joining, gets you information and signals you have been listening. Questions answerable from the careers page cost you the slot and tell the interviewer you did not prepare, and the last five minutes are the part of the conversation you control most. Does a thank-you note actually matter? It matters at the margin, and the margin is where most decisions between two good candidates get made. Send it within a day, reference something specific from the conversation rather than thanking them generally, and keep it short. It will not rescue a bad interview; it occasionally tips a close one, which is a reasonable return on ten minutes. How do I answer a question about a gap or a short stint? Say what happened in one sentence, say what you did with the time, and move on. The length of the answer is the signal — a brief, unembarrassed explanation reads as a closed subject, and a long one invites more questions. Interviewers are checking whether it is a pattern and whether you can discuss it calmly, not looking for a reason to stop. ## Job board https://clearhire.aoneahsan.com/jobs Jobs on ClearHire, each marked with whether the employer has countersigned a former employee's record from its own files. Not a rating — one checkable fact. Every board lists jobs. This one can tell you who signs. The usual filters are here — title, location, pay, contract, experience. The one worth coming for is verified employer: companies that have countersigned at least one former employee's record, from their own files. It is not a quality rating and it is not an endorsement. It says one thing only: this company has answered a former employee in writing. There is no fifth state for “declined”. A company that answers a record is answering that record, not rating itself, and we will not turn one person's disputed dates into a badge on a job advert. A posting with no pay band shows none rather than a guess with a range attached. The band is what the employer published; ClearHire does not estimate pay. ## Levels, and what each one unlocks https://clearhire.aoneahsan.com/levels Six rungs. Everything unlocked is a feature inside ClearHire — a slot, a limit, a link. None of it is a signal to an employer. Six rungs. Everything unlocked is a feature inside ClearHire — a slot, a limit, a link. None of it is a signal to an employer. A level is never taken away, and losing a resume slot because your points fell would be an absurd way to treat someone mid-application. It does not make a record more verified, it does not move you up anyone's list, and it is not shown on your public profile unless you turn on the one line at level 6. Verification is a company answering a question about you — nothing on this page can substitute for that, and if it ever looks like it can, this feature is doing harm. ## Licensing https://clearhire.aoneahsan.com/licensing Run ClearHire as your own product — white-label web from $10,000, the Android app, the source, or an outright buyout at $36,000. Every figure is printed. ClearHire can be licensed to run as your own product. The white-label web platform is $10,000, the Android app is a $3,000 add-on that also takes 10% off the order, and a non-exclusive source licence is $5,000 and a further 5%. The two discounts are additive rather than compounded. An exclusive buyout is $36,000 flat — web, Android and the full source, exclusively — and is never discounted for the add-ons it already contains. Every one of the 111 features is printed with its own build value, between $35 and $250, because the argument for the bundle is arithmetic a reader can check: buying the platform piece by piece comes to more than the bundle price. A licence is unrelated to the Pro plan, which is an individual subscription. Nothing in a licence transfers a verified employment record: a record is a statement one company made about one person. ## Configure a licence https://clearhire.aoneahsan.com/licensing/configure Pick the package, the add-ons and the features, and see every line of the arithmetic — not just the total. The whole quote lives in the address bar. The licensing configurator builds a quote from the same catalogue the licensing page prints: the bundle, a custom package, or the exclusive buyout, with the Android and source add-ons and the discounts each unlocks. Every line item, the subtotal, the discount percentage and what it took off are shown, because a quote you cannot check is a number you have to trust. The whole selection lives in the URL, so a configured quote survives a refresh and can be sent to somebody else exactly as it was left. ## Making a LinkedIn profile do what a resume cannot https://clearhire.aoneahsan.com/linkedin-optimizer A resume is read once by someone who already has it. A profile is found by someone who does not know you exist — which changes what belongs in it. A resume and a LinkedIn profile are read in opposite directions. A resume reaches someone who already decided to look at you, and its job is to survive the next ten seconds. A profile reaches someone who has not decided anything, often through a search they typed, and its job is to be findable first and readable second. That difference explains almost every piece of advice that follows, and it is why copying a resume into a profile produces something that does neither job well: the resume's compression works against being found, and the profile's completeness works against being read quickly. This page is about what to change when the same career history has to do two different jobs. It is not about gaming a ranking algorithm nobody outside LinkedIn can see, and any page claiming to know that algorithm is guessing. You are not being found at all. Nobody is reading your profile because nobody is reaching it. That is a headline and skills problem, not a writing problem — the words a recruiter searches are rarely the words a job title uses. You are found and nothing follows. Views without messages usually means the top of the profile does not say what you do in words the reader recognises. The first two lines carry more weight than the rest combined, because they are what appears in a list. You are changing field. A profile can carry the explanation a resume has no room for. The About section is the only place in a job search where you get several paragraphs and nobody is timing you. Write the headline for a search, not for a title. The default headline is your current job title at your current company, which is exactly the string nobody searches. Replace it with what you do and what you work on, in words other people use. "Support engineer — escalations, incident triage, SaaS" is findable; "Senior Associate II" is not. Fill the skills list from the adverts, not from memory. Open five adverts for the role you want and write down every capability that appears in three or more of them. Those are the terms a recruiter filters on. Adding one you cannot defend in a conversation is worse than leaving it out. Rewrite the About section in the first person. A profile written in the third person reads as a press release about someone who is not in the room. Say what you do, what you are looking for, and one thing you are unusually good at. Three short paragraphs is enough; nobody finishes six. Cut every role older than about ten years to one line. A profile is a scroll, not a page, so length costs the reader more than it costs you. Recent roles get their detail; older ones get a title, a company and dates, which is all anyone reads that far down. Make the top of the profile survive being screenshotted. Photo, headline, location and current role appear together in search results, in messages and in shared links. That block is the profile most people will ever see. Everything below it is for the minority who clicked. A support engineer who was invisible in search Headline changed from "Senior Associate II at Northgate" to "Support engineer — escalations, incident triage, payments". The words came from four job adverts rather than from the company's internal grade ladder. The profile started appearing for searches it had never matched, because the words a recruiter types are the words in adverts. A profile with views and no messages The About section opened with three sentences about a philosophy of work. Replaced with what the person does, the two systems they know best, and what they are looking for. The change was to the first forty words, because that is what appears before the "see more" fold. The headline is the single highest-leverage field. It appears in search results, in messages, next to comments, and in every link anyone shares. Skills you cannot discuss for two minutes should not be listed. A filter that surfaces you for something you cannot do wastes an interview, which costs more than not being surfaced. A profile photo that looks like you on a normal day is better than a formal one that does not. The purpose is recognition, not impressiveness. Recommendations are the one part of a profile a reader treats as evidence, because you did not write them. Two specific ones are worth more than eight generic ones. Update the profile before you need it. A profile edited heavily in one week reads as a job search to anyone watching, including your current employer. Nothing on a profile is verified by LinkedIn, and everyone reading knows it. That is the gap employment verification exists to close, and it is why a confirmed role is worth more than a well-written one. Why is a profile written differently from a resume? Because the reader arrives differently. A resume reaches someone who already decided to look at you and has ten seconds; a profile reaches someone who does not know you exist and found you through a search. That makes the words people search for load-bearing in a profile and nearly irrelevant in a resume. What should the headline say? What you do, in the words someone looking for it would type. A job title alone wastes the most-read line on your profile, and a slogan wastes it entirely. The test is whether a stranger could tell from the headline alone what kind of work to bring you. I am found but nothing follows. What is wrong? Usually the gap between the headline and the rest. Being found is a search problem and being contacted is an evidence problem — if the first line promises something the profile does not then substantiate, a reader leaves. Check that the top third makes a claim and the rest of the page proves it. How much of my resume should the profile repeat? The structure, not the wording. The same roles and dates need to be there — a mismatch between the two is a real problem — but the profile has room to say why something mattered, which a resume does not. Copying a resume verbatim produces a profile that is accurate and inert. Does activity on the platform actually matter? It matters for being found again after the first time. Profiles that are entirely static are found through search alone; profiles attached to something a person wrote get found through the writing too. That is not an argument for posting daily, but it is an argument for having a few things attached to your name. How do I present a change of field on a profile? Lead with where you are going and let the history explain itself underneath. A profile is read top-down and the top is what decides whether the rest gets read, so a headline in the old field routes you to the old field's opportunities. The past roles do not need rewriting — they need a frame. ## What a personal brand actually means in a job search https://clearhire.aoneahsan.com/personal-brand Mostly it means being legible: consistent, specific, and easy to describe to someone who was not in the room. Very little of it is about self-promotion. The phrase "personal brand" invites a lot of nonsense, so it is worth reducing it to the thing that actually helps: whether someone who has met you once can describe what you do to someone who has not. That is the whole mechanism. Jobs move through people repeating a short description of you to other people, and the description they repeat is the one you made easy to remember. Everything else attributed to branding — a colour scheme, a posting schedule, a personal website — is a way of making that description consistent, and none of it works if the description itself is vague. This page is about arriving at a description that is specific, true, and short enough to survive being passed on. It is not about becoming a public figure, and most of what follows is invisible to anyone but the person doing the describing. People describe you inaccurately. A colleague recommends you for the wrong thing. That is a description problem, not a reputation problem, and it is fixable by being clearer about which part of your work you want more of. You do several things and lead with all of them. A person who does three things well is often described as doing none of them, because the listener cannot hold three. Leading with one does not discard the others; it gives the listener somewhere to start. You are changing field. The description has to carry the change, because otherwise the listener supplies their own explanation and it is usually less flattering than the truth. Write the sentence someone else would say about you. Not the sentence you would say. "She fixes support processes that are quietly broken" is a sentence a colleague can repeat. "Results-driven professional with a passion for excellence" is not a sentence anybody has ever said out loud. Test it on someone who does not do your job. If they can repeat it back a day later, it works. If they ask what it means, the words are yours rather than theirs, and the description will not travel. Make the visible surfaces agree with it. Your profile headline, the top of your resume and the way you introduce yourself should all be recognisably the same claim. Three different claims is not three chances; it is one confused listener. Pick evidence that a stranger can check. A confirmed employment record, a shipped project with a public URL, a talk anyone can watch. Evidence someone can verify without asking you is what turns a description into a reputation. Leave the rest alone. A logo, a colour scheme, a content calendar and a newsletter are all real work with real costs, and none of them helps until the sentence is right. Most people never need any of them. Three specialisms, no description A data analyst who also built dashboards and ran onboarding was recommended for whichever of the three the recommender happened to remember. Leading with "makes messy operational data usable" covered all three and gave the listener one thing to hold. A career change nobody could explain A teacher moving into product work kept being described as "a teacher who wants to change career", which is a description of a wish. "Turns confusing processes into something people can follow — used to do it in a classroom, now doing it in product" is a description of a capability, and it survives being repeated. The test is repetition, not admiration. A description someone finds impressive but cannot repeat does nothing for you. Specific is more memorable than senior. "Cut a support backlog in half" outlasts "seasoned leader" in anyone's memory. You are not choosing this once. The description changes as the work changes, and a description that has not moved in five years usually describes an older job. Consistency matters more than polish. The same plain sentence in three places beats three different well-written ones. Nothing you say about yourself carries the weight of something a company confirmed. That asymmetry is the whole reason verified employment exists, and no amount of branding closes it. If a piece of branding advice would embarrass you to follow, it is probably also making you less legible rather than more. Is a personal brand just self-promotion? No, and the confusion is what makes people avoid the useful part. The mechanism is legibility: whether someone who met you once can describe what you do to someone who has not. That description is what circulates when you are not in the room, and it forms whether you cultivate it or not. How do I find out how I am currently described? Ask three people who know your work to describe it in a sentence. It is an uncomfortable question and it is the only reliable way to see the gap, because your own summary is built from what you find interesting rather than from what other people noticed. If the three answers disagree, that disagreement is the problem. I do several things. Do I have to pick one? You have to lead with one. Leading with three means being remembered for none, because a description that has to carry three things does not survive being passed on. Pick the one you want more of, put it first, and let the others appear as depth rather than as alternatives. Do I need to post publicly to have one? No. Public writing is one way to make work legible and it is neither necessary nor sufficient. Doing visible work inside a company, speaking at internal forums, or simply being consistent about what you take on all produce the same effect. What matters is that the description exists and is accurate. How does this help when changing field? It is what stops the change reading as a retreat. During a change your history and your direction disagree, and without an explicit frame the reader picks the history. Saying what you are moving toward, and why the previous work is relevant to it, replaces their guess with yours. How long does it take to change how people describe you? Months, and it moves through the people who talk about you rather than through anything you publish. The lever is consistency — taking on the same kind of work, being introduced the same way, saying the same sentence when asked. It is slower than it sounds and more durable than anything faster would be. ## Plans and pricing https://clearhire.aoneahsan.com/pricing Free, Pro and Team compared, with every limit the server enforces. Verified employment is on the free plan and stays there. ClearHire has three plans. Verified employment — asking a former employer to confirm a role you actually held — is on the free plan and stays there, because it is the reason the product exists. Paid plans raise the limits and add shared seats; they do not add credibility. Free costs nothing and is not a trial. Pro is $90 a year, or $9 a month — $7.50 a month on the yearly plan, 17 per cent less. Team is $70 a seat a year with a 3-seat minimum, so $210 a year to start. Free: ai 25, resumes 30, letters 30, alerts 10, verifications 30, savedToolResults unlimited, exportsPerMonth unlimited, teamSeats not included, publishedLinks 30, savedTemplates 30. Pro: ai 300, resumes unlimited, letters unlimited, alerts 50, verifications unlimited, savedToolResults unlimited, exportsPerMonth unlimited, teamSeats not included, publishedLinks unlimited, savedTemplates 30. Team: ai 600, resumes unlimited, letters unlimited, alerts unlimited, verifications unlimited, savedToolResults unlimited, exportsPerMonth unlimited, teamSeats 3, publishedLinks unlimited, savedTemplates 30. Nothing is deleted when a plan ends. Anything over the new limit becomes read-only until you are back under it, and a countersigned employment record belongs to you rather than to a plan or to whoever paid for your seat. Paid plans are bought on the web. The Android app shows which plan you are on and applies its limits; it does not sell. ## Privacy https://clearhire.aoneahsan.com/privacy What ClearHire collects and what it does with it — every category, every third party, every Android permission, and the two records that outlive account deletion. The ClearHire privacy policy covers the website and the Android app. There is no iOS app and no browser extension, so nothing in it refers to one. Thirteen numbered clauses name every category of personal data collected and the feature that requires it, every third-party processor and whether it acts as a processor or an independent controller, and every Android permission the app declares with the reason for each. Two categories of record survive account deletion — an identity-verification dispute and an abuse report — and both are named in clause 07 rather than discovered afterwards. ## Browser extension privacy policy https://clearhire.aoneahsan.com/privacy-extension There is no ClearHire browser extension. This page answers an address that was published while one was being built, rather than leaving it to 404. There is no ClearHire browser extension. One was built and staged during the previous version and was never uploaded to any store, so it was never installed outside development. This address is answered rather than left to 404 because it was published and crawled. The policy that governs everything ClearHire actually does is the main privacy policy, which covers the website and the Android app. ## Professional development https://clearhire.aoneahsan.com/professional-dev How to keep growing once the job itself stops teaching you — choosing what to learn, proving it, and telling the difference between a credential that opens a door and one that does not. Professional development in 2026 covers skill-building outside your current role — courses, certifications, side projects, conferences, books, mentorship — that prepares you for future roles or compounds in your current one. The most useful professional development is tied to a target role you are working toward, not generic learning. 5–10 hours per week is the sustainable target while working full-time; more risks burnout, less produces visible drift over years. Compound interest on consistent small investment beats sporadic large investment. Many companies offer professional-development budgets; surprisingly few employees use the full amount available. Building skills toward a target promotion. Pick the gaps surfaced by /tools/skills-gap. Build in your top 3 skills consistently across 60–90 days. Ship visible artifacts (project, course completion with portfolio output, conference talk). Promotion conversations land better with visible artifacts than with course-completion certificates alone. Using your employer professional-development budget. Most companies offer $1K–$5K per year. Ask what your budget is; most employees do not know. Use it for a focused course, a conference, a book stack, or coaching. Annual budgets reset; unused budget rolls back to the company. Maintaining skills between roles. Between jobs is a high-leverage learning window. Use it on 2–3 deep skills with shippable projects rather than 10 shallow course completions. Output: a portfolio that visibly shifts what level of role you can target. Deciding what to stop learning. A development plan needs a subtraction as often as an addition. Something you started for a role you no longer want is costing the hours the current target needs, and dropping it explicitly is different from letting it lapse — one frees the time, the other leaves it half-spent and slightly guilty. Tie development to a target role. Generic learning produces drift. Specific learning toward a target role compounds. Pin the role first; let learning flow from the gap. Pick 2–3 focused skills. Above 3 skills, depth suffers. Below 2, the time investment does not produce visible change. Pair each skill with a course + project. Course is the on-ramp; project is the proof. Course-completion certificates rarely move the needle alone. Schedule 5–10 hours per week sustainably. Less than 5 produces drift. More than 10 risks burnout. The sustainable middle compounds across years. Use your employer budget annually. Ask about your professional-development budget. Spend it on focused outcomes (one focused course, one conference, one book stack). Unused budget benefits the company, not you. An engineer using employer budget on systems-design course + book stack $2K budget covers a senior-level course ($800), conference attendance ($1,000), and 5 books ($200). Output: shipped a side project, gave a internal talk, promoted to staff at month 14. Someone with a learning budget and no plan for it They asked their manager the three questions, found the budget reset in two months and covered conferences as well as courses, and spent it on one course tied to the role they were aiming at plus the book list for it. The budget had been available for three years and unspent for three years. Tie professional development to a target role; generic learning produces drift. Pick 2–3 focused skills; above 3, depth suffers. Course is the on-ramp; project is the proof. Recruiters care about projects. 5–10 hours per week is the sustainable target while working full-time. Use your employer budget annually — unused budget benefits the company, not you. Ask what the learning budget covers, when it resets and who approves it, in one message — most go unspent for process reasons rather than hard ones. One course paired with one finished thing beats three courses with nothing to show. How do I choose what to learn when everything looks relevant? Tie it to a target role and everything else falls away. Generic learning feels productive and compounds slowly; learning aimed at a role you can name has an obvious test — does this appear in the adverts — and an obvious stopping point. Without the target, the honest answer to "is this worth learning" is unanswerable. How do I use an employer learning budget that nobody explains? Ask what it covers, when it resets, and who approves it, in one message. Most budgets go unspent because the process is undocumented rather than because it is hard, and the answer is usually a name and a form. Ask early in the year — budgets that reset annually are hardest to spend in the last month. Is a course or a project better evidence? A project, in almost every case, with the course as the scaffolding that makes the project possible. A completed course tells a reader you spent time; a finished thing tells them what you can do and gives you something specific to talk about. The strongest pairing is one course and one thing built with it. How many hours a week is realistic alongside a job? The number you would still hit in a bad week, which is usually smaller than the one you would like. Sustained modest effort beats occasional intense effort for anything that takes months, and the plan that assumes your best week is the plan that stops in week three. Pick the floor and treat the rest as upside. How do I keep skills current between roles? Keep shipping something small and keep talking to people doing the work. Skills decay less from time off than from isolation — the thing that goes stale first is knowing what the current problems are, and that comes from conversation rather than from courses. A small regular output also gives the search something to point at. How should learning show up on a resume? As what it let you do, not as a list of courses. A line naming a course reads as an activity; a line naming the thing you built or changed reads as a capability, and the course belongs in a short section at the end if at all. The exception is a certification the field screens on, which belongs where a screener will find it. ## Common interview questions https://clearhire.aoneahsan.com/resources/common-questions The questions that come up in most interviews, what each one is really asking, and how to answer without a script. A small number of questions carry most interviews, and they are the same ones nearly everywhere: tell me about yourself, why this role, describe a conflict or a failure, what are your strengths and weaknesses, where do you want to be, and do you have any questions for us. Preparing those specifically is worth more than trying to anticipate everything, because the alternative is composing an answer live to a question you could have seen coming. What follows is what each one is actually asking — which is rarely what it appears to ask — and how to answer it without sounding like something you memorised. Drilling the universal openers. "Tell me about yourself" opens most interviews and is the answer people prepare least, because it sounds like small talk. It is not: it is where you decide what the rest of the conversation is about. Sixty to ninety seconds, structured — where you are now, two things worth knowing, why you are in this room. Building a failure or conflict story you can actually tell. Use a real one and a small one. An invented failure is audible, and a catastrophic one spends the interview on damage rather than on judgement. The part being assessed is what you changed afterwards, which is why a story with no lesson attached lands worse than the failure it describes. Adapting per role without rewriting everything. The stories stay the same; the emphasis moves. One example can answer a question about ownership at one company and about collaboration at another, depending on which beat you spend the time on. Preparing four flexible stories beats preparing twelve rigid ones. Drilling the six questions that carry most interviews. A small set of questions appears nearly everywhere, and each has a real underlying ask. Preparing these six well covers more ground than preparing thirty superficially, because most other questions are one of the six in different clothes. List the 10 most common questions for your role type. Tell-me-about-yourself, why-this-role, why-this-company, conflict, failure, leadership, strengths, weaknesses, 5-year-plan, plus 1–2 role-specific. Pin them. Draft 60–90 second answers using STAR or similar structure. For behavioral: STAR format. For "tell me about yourself": current role + 2 highlights + what you want next. For weaknesses: real weakness, not central to the job, with active mitigation. Practice each out loud and time-boxed. Answering in your head is faster and clearer than answering aloud, so the version you rehearse silently is not the version that arrives in the room. That gap is where interviews come apart, and the only way to find it is to hear yourself. Tailor each per role. Same core structure; different specifics per role. Tell-me-about-yourself for a fintech PM role emphasizes payments work; for a consumer PM role emphasizes consumer experience. Reuse structure; tailor substance. Practice transitions between questions. Real interviews chain questions ("you mentioned conflict — tell me about a time you disagreed with leadership"). Practice the chain, not just isolated answers. Smooth transitions signal preparation; awkward jumps signal scripted answers. A candidate drilling tell-me-about-yourself for a fintech PM role Drafts a 75-second answer leading with current PM role + two payments-related highlights + what they want next. Practices 5 times on video. Real interview: nails the opener; sets tone for a strong full conversation. Offer follows. A candidate using a real small failure for the failure question "I underestimated the timeline on a project last year by 3 weeks. Here is what I learned..." Honest reflection lands better than a manufactured "I am too much of a perfectionist" answer that interviewers see through immediately. A candidate who prepared the opener last They had six polished stories and no answer to "tell me about yourself", and spent the first three minutes of every interview recovering from a rambling start. Writing ninety seconds and timing it fixed the problem in one evening — and it was the question they had assumed needed no preparation. A small number of questions cover most behavioural interviews. Drill those rather than trying to anticipate everything. Memorise the structure, not the words. A rehearsed sentence is audible and a rehearsed shape is not. Sixty to ninety seconds is the target for an opener. Longer stops being an answer and becomes a monologue. Use one real, small failure. Inventing one is the thing an interviewer is best at detecting. Practise out loud and timed. The version in your head is faster and clearer than the one that arrives. Have questions of your own that you actually want answered. The ones asked to look interested are recognisable as such. What is "tell me about yourself" actually asking? It is asking why you are sitting there, in about ninety seconds. The mistake is treating it as a biography and starting at university; the useful answer is a short arc from what you do now, through what you have done that is relevant, to why this role. It is the only question you can fully prepare, which is why a weak answer to it is so costly. How do I answer the weakness question without a fake weakness? Name a real one that is not fatal for this job, and say what you do about it. Interviewers have heard "perfectionism" enough that it now reads as evasion. A genuine limitation plus a concrete mitigation answers the question they are actually asking, which is whether you can see yourself clearly. What makes a failure story work? Owning the decision and naming what you changed afterwards. The trap is choosing a failure that was somebody else's fault, which answers a different question, or one so small it reads as evasion. Pick something that genuinely went wrong, say what you would do differently, and show that you did it differently later. How do I answer "where do you want to be in five years"? Answer honestly at the level of direction rather than title. Naming a specific job you want in five years invites a comparison with the one on offer; naming the kind of problems you want to be working on says the same thing without the trap. If the honest answer is that you do not know, saying what you want to be better at is a real answer. Should I have different answers for different companies? Same stories, different emphasis. Rewriting your material per company is unsustainable and produces thin answers everywhere; re-cutting a story to lead with the part that matches this role takes minutes and works. The stories are the asset — the framing is the per-company work. What do I say when I genuinely have no example? Say so, then answer the nearest real thing. "I have not led a team, but I have owned this piece end to end and here is how I handled the coordination" is a good answer. Inventing an example is the worst option available, because follow-up questions are what interviews are made of. ## Company research https://clearhire.aoneahsan.com/resources/company-prep How to research a company before an interview — where to look, what to ask, and the red flags worth noticing. Company preparation is the 30–45 minutes of focused research that separates strong interviews from generic ones. The goal is three specific things you can reference in the conversation, not a memorized about-page summary. Generic research is invisible; specific research is memorable. Most candidates skip company prep entirely or spend the time on the wrong sources (the about page, generic press releases). The right sources: recent leadership talks, recent product launches, employee review patterns over 6+ months, and the company's own engineering / product blog. Pre-interview research the night before. 30–45 minutes spent surfacing 3 specific things to reference. Saves hours of generic skimming and produces concrete material for "why this company?" answers and your own questions. Validating cultural fit before accepting an offer. After offers come in, deeper company prep helps you decide. Read 6+ months of employee reviews; talk to one current and one former employee. Specifics surface; the offer's real shape becomes legible. Comparing two competitive offers. Same research depth on both companies surfaces different signals. The "research output" for each becomes input to your offer-comparison framework — culture, leadership, product trajectory, growth path. Researching to decide, not only to impress. The same forty-five minutes serves a second purpose most people waste. You are also deciding whether to work there, and the research is the only part of the process where you can look at the company without anyone performing for you. Write down what would worry you as well as what impressed you, before the interview makes you want the job. Read public values + recent press in 10 minutes. Values give you the framing they use; recent press tells you what is actually happening (launches, funding, leadership changes). Both inform conversation specifics. Check leadership tenure and recent moves. High turnover at director / VP level is a signal. Three of five VPs joining in the last 12 months is worth probing in the interview. Read 6+ months of employee reviews for patterns. Patterns repeating across 5+ reviews are signal; single complaints are noise. Note both positive and negative themes. Watch one recent leadership talk or interview. 30 minutes in the background while doing dishes. Surfaces specific quotable moments without feeling like research. Reference one specific thing in the interview. Skim 2–3 recent blog posts matching the role. For engineering: engineering blog. For PM: product launches. For design: design system or case studies. Pick the post that matches your role; quote one specific thing. A candidate doing 40 minutes of company prep Surfaces a recent funding round, a CTO talk on payments architecture, and a repeated employee theme about strong cross-team collaboration. References all three across the interview; interviewer flags as "clearly did the work" in feedback. A candidate spotting a red flag during prep Sees 3 of 5 VPs joined in the last 6 months. Probes politely in the interview; honest answer surfaces ongoing reorg. Candidate withdraws politely before investing more time. A candidate whose research changed the questions rather than the answers Forty minutes surfaced a recent reorganisation mentioned nowhere in the advert. They asked how the team's remit had changed since, got a candid answer about a scope that was still being settled, and accepted the offer knowing what they were joining rather than discovering it in month two. 30–45 minutes is the sweet spot. Less leaves you generic; more produces diminishing returns. Three specific things to reference — not ten. Density beats coverage. Single review complaints are noise; patterns across 5+ reviews are signal. Watch one leadership talk in the background; produces quotable moments without feeling like work. JD-grounded questions land better than generic ones — research feeds questions. Turn what you find into questions, not statements — a question that could only come from having read something starts a conversation; a recited fact ends one. Write down what worried you as well as what impressed you, before the interview makes you want the job. How long should company research actually take? Thirty to forty-five minutes is the useful range. Below that you arrive with the about page, which every other candidate also has; well above it you are refining detail that will not come up. The target is three specific things you can reference naturally, not coverage. Which sources are worth the time and which are not? Recent leadership talks, recent product or engineering posts, and employee reviews read for repeated themes. The about page and generic press releases are the ones to skip — they are written to be uninformative, and quoting them signals you did the minimum. One background-watched talk usually yields more usable material than an hour of skimming. What do I do with what I find? Turn it into questions rather than statements. Reciting a fact about the company proves you read something; asking a question that could only come from having read it starts a conversation, and the conversation is what people remember. Two or three such questions is plenty. How do I research a company that has almost no public footprint? Go to people instead of pages. A small or private company may have nothing published, and in that case one conversation with a current or former employee is the entire research. Failing that, read the job advert extremely closely — a small company's advert is usually written by the person you will work for, and it says a great deal about what they want. What red flags are worth noticing during research? Heavy turnover at director level and above, the same complaint repeating across two years of reviews, and public statements that contradict what you are told in the process. None of these is disqualifying alone. What makes them worth noting is that they give you something specific and polite to ask about, and the quality of the answer is the real signal. Should I mention that I did the research? No — demonstrate it and let them notice. "I read your engineering post on the payments migration, and I wondered…" does the work; "I did a lot of research on your company" does not. The reference is the evidence, and pointing at it weakens it. ## Interview tips, as a working reference https://clearhire.aoneahsan.com/resources/interview-tips Six sections you can work through in order, or open at the one you need. It is deliberately specific about which preparation changes an outcome and which only feels like work — most interview advice is confident about both and honest about neither. What to research, and what to skip Research has sharply diminishing returns, and most guides do not say where the cliff is. Two hours of the right reading is worth more than a day of the wrong kind. Worth the time: What the company sells, and who pays for it. If you cannot say this in one sentence, keep reading. The job description, line by line — most interview questions are visible in it. Two or three things you have done that map onto those lines, with numbers where you have them. Who is interviewing you, and what they do. A hiring manager and a peer want different answers. Rarely worth the time: Memorising the leadership team, unless you are meeting them. The funding history, unless you are asking about runway — in which case ask directly. Rehearsing answers word for word. Recited answers sound recited, and the first unexpected follow-up removes the script. The twenty-four hours before At this point new material rarely helps. The job is to remove the things that go wrong for mechanical reasons. Confirm the time, the timezone and the joining link. The most common avoidable failure, and the least forgivable one. Re-read your own resume. You will be asked about a line you wrote two years ago and have not thought about since. Prepare two questions to ask. Section 04. Having none reads as indifference even when it is nerves. Test the camera and microphone you will actually use. Not a different device. Ten minutes of a broken microphone is ten minutes of your slot. Learn the interviewers' career histories in detail. Knowing their role is useful. Knowing their last four jobs is unsettling if it surfaces. Rehearse answers word for word. It costs you the ability to answer the question you were actually asked. Answering with a structure Most people do not fail behavioural questions because their work was weak. They fail because the answer arrives without a shape, so the interviewer cannot tell what the person actually did. A structure fixes that, and STAR is the common one: Situation, Task, Action, Result. The value is not the acronym — it is that it forces the two parts people skip: what specifically you did, and what changed as a result. Question. Tell me about a time you disagreed with a decision. Situation. We were two weeks from a launch and settlement failures were sitting at 3.1%. Task. The plan was to ship and fix afterwards. I thought that was the wrong order. Action. I wrote up the failure modes with the cost of each, took it to the lead, and asked for one week. I was explicit that it was my call to make the case and theirs to decide. Result. We took the week. Failures went under 0.4% and the launch moved by five days. I was wrong about the cause twice before finding it. The last sentence is doing real work. An answer where nothing went wrong reads as an answer that has been sanded down. Questions worth asking them The end of an interview is the one part you control completely. A good question is one whose answer would actually change whether you take the job. What does the first ninety days look like? Vague answers here are a real signal about whether the role is defined. Who was the last person in this role, and where did they go? Promoted, moved sideways, or left — all three tell you something. What is the part of this job people find hardest? Invites an honest answer without asking anyone to criticise their employer. What happens next, and by when? Practical, and it gives you a date after which following up is reasonable. Remote and panel interviews Both change the mechanics rather than the substance, and both have a small number of specific failure modes. Remote. Look at the camera when you finish a point, not at the faces. Leave a beat before answering — latency turns a normal overlap into an interruption. Have the job description open off-screen; nobody minds, and it beats guessing. Panel. Answer to the person who asked, then include the rest of the room before you stop. Write the names down as they introduce themselves. A panel is usually assembled from people with different concerns, so expect the same answer to be probed from two directions. If an interview needs an adjustment — extra time, questions in advance, a different format — asking for it is normal and is routinely granted. Ask the recruiter rather than the panel. Afterwards Send a short note within a day if you want the job. Three sentences: thank them, name one specific thing from the conversation, confirm you are interested. A long follow-up does not improve on a short one, and a template one is visible from a distance. If the date they gave you passes, following up once is reasonable. Following up three times is not, and it is remembered. If you are rejected, asking for feedback is worth one message. Most companies will not give specifics — usually for legal reasons rather than unkindness — so treat a non-answer as a non-answer rather than a verdict. How much should I prepare for a first-round screen? Enough to answer “why this company” and “why this role” without hesitating, and to describe two pieces of your own work in detail. A first-round screen is usually checking that you are real, available and interested. Is it acceptable to say “I don't know”? Yes, and it is usually better than the alternative. Say what you do know, say how you would find out the rest, then stop. Interviewers are calibrated on bluffing and it is one of the easiest things to spot. Should I ask about salary in the first interview? Asking for the band is reasonable at any stage and saves both sides time. Negotiating the number before an offer exists generally does not help you. Does any of this depend on the country I am in? Some of it. Norms around salary questions, references and follow-up vary, and this page is written from a general perspective rather than a jurisdiction-specific one. Where a local convention conflicts with something here, the local convention wins. ## Practice mode https://clearhire.aoneahsan.com/resources/practice Timed practice against realistic prompts, so the first time you say an answer aloud is not in the interview. Practice that helps has three properties: it happens out loud, it is timed, and you listen back to it. Each one closes a different gap. Answering in your head is faster and clearer than answering aloud, so the version you rehearse silently is not the version that arrives in the room. A timer is what turns a comfortable four-minute answer into the ninety seconds an interviewer is actually waiting through. And a recording catches the filler, the trailing sentences and the missing context that you cannot hear while producing them. None of this needs an account or a tool — a phone and a stopwatch are the whole apparatus, and ClearHire records nothing. Final-week preparation for a specific interview. 3–5 sessions in the days before the real interview. Record each. Watch playback. Identify two patterns to fix; rehearse the same questions again. Improvement between take 1 and take 3 is the actual gain. Maintenance practice during a long search. 1–2 sessions per week keep skills sharp without burning out. Rotate between behavioral, technical, and systems-design rather than focusing on one type. Maintenance compounds over months. Pair practice with a peer or mentor. 70% solo with recording for efficiency; 30% with a partner for social pressure that mimics real interviews. Both have value; together they outperform either alone. Practising the week before a specific interview. Narrow it: the three competencies that role emphasises, the questions the format implies, and the two stories you will lead with. Broad practice at this stage adds nothing — you are not building material any more, you are making the material you have retrievable under pressure. Pick a question type and time-box. Behavioral: 90-second timer. Technical: 30-minute coding session. Systems-design: 45-minute session. Without time pressure, practice is too easy to be useful. Answer out loud, even if alone. Speaking forces you to confront filler, run-ons, and missing context. Internal answers do not produce the same gains. Record the session. Phone video or audio. Playback reveals patterns invisible in real time — filler words, trailing endings, repeated structures. Watch playback and self-grade harshly. Use a simple rubric: clarity of structure, time management, specificity of examples, recovery from a stumble. Self-grade harshly; the real-interview bar is higher than your gut suggests. Re-do the same question after review. Two attempts on one question teach more than one attempt on two questions. The improvement between take 1 and take 2 is where real growth happens. A candidate doing 4 systems-design mocks before a final round Records each. Identifies pattern of starting with implementation details before clarifying requirements. Fixes in mocks 3 and 4. Lands the offer; interview feedback specifically calls out the systems-design discussion. A candidate doing maintenance practice during a 3-month search Runs 2 sessions per week. By month 3, behavioral answers run a tight 75 seconds with no filler. Real-interview performance noticeably better than month 1. Someone who timed their answers for the first time Their strongest story ran to four and a half minutes, and the interviewer in the previous round had cut it off. Trimmed to two, it kept the result and lost the setup, and it was the answer that came up in the offer feedback. Out loud, timed, and listened back to. Each property closes a different gap, and the third is the one people skip. A handful of sessions before one interview does most of the work; the gain is between the first take and the third, not in the tenth. The quality of the review matters more than the number of sessions. Self-grade harshly. The bar in the room is higher than it feels at your desk. Mostly alone with a recording, sometimes with a person. The recording is efficient; the person supplies the pressure. ClearHire records nothing and stores nothing from this. A phone and a stopwatch are the whole apparatus. Time every answer at least once — most run long, and the interviewer's attention is the constraint that does not negotiate. Listen back to one recording. It is the least pleasant part and it changes more than another hour of practice. Why does practising out loud matter so much? Because the version you rehearse in your head is not the version you will say. Silent rehearsal is faster, more fluent and better organised than speech, so it consistently overestimates how ready you are — and the gap shows up exactly once, in the room. Saying an answer aloud is the only way to find the sentences that fall apart. How long should an answer be? Around two minutes for a behavioural question, and you will not know whether yours is until you time it. Most unprepared answers run long, most over-prepared ones run longer, and the interviewer's attention is the constraint neither respects. Timing is the fastest correction available. Do I really need to listen back to a recording? Yes, and it is the part everyone skips because it is unpleasant. Listening back is the only feedback loop that shows you the filler, the trailing sentences and the point where you started explaining something twice. Ten minutes of listening changes more than an hour of additional practice. How much practice is enough before an interview? Enough that the structure is automatic and the wording is not. Practising until you can find each story instantly is preparation; practising until you have a memorised script is over-preparation, and it is audible. For most people that is a handful of timed run-throughs rather than a week of them. Is practising with another person better than practising alone? For the last stretch, yes, because a person asks the follow-up. Alone you answer the question you expected; a partner interrupts, asks what you actually did, and finds the soft part of the story. Use solo practice to build the answers and a partner to stress them. What should I practise during a long search with nothing booked? A small amount, regularly, on the stories rather than on any specific company. Skills here decay from disuse and the recovery is slow, so one short session a week keeps the material live at almost no cost. It also means an interview that appears with three days' notice is a top-up rather than a rebuild. ## Salary calculator https://clearhire.aoneahsan.com/salary/calculator Arithmetic on the number you type. It estimates no market rate and invents no figure. ## Cost of living https://clearhire.aoneahsan.com/salary/cost-of-living How to compare what a salary is worth in two cities, and why the headline difference is usually the smallest part of the answer. ClearHire has no cost-of-living calculator and holds no cost-of-living data, so this page is the method rather than a machine. Comparing two cities is arithmetic anyone can do once they know which four numbers to get: housing, tax, transport and everything else — in that order of size, for almost everybody. The reason people get this wrong is not the arithmetic; it is comparing the headline salaries and stopping, because that is the one number both offers put in front of you. A move that raises pay by a fifth and raises rent by half is a pay cut that reads as a promotion. Evaluating a remote job offer at a different pay rate. Some companies pay one global rate; some pay locally. The calculator shows whether moving to a cheaper city (with location-adjusted pay) actually nets out as better or worse than staying in your current city. Negotiating a relocation salary. When a company asks you to move, they should adjust salary for the new city's cost of living. The calculator gives you the number to ask for. Without it, candidates routinely accept salaries that are real-terms pay cuts disguised as moves. Comparing offers across metros. A $200K offer in NYC and a $170K offer in Austin can be roughly equivalent in purchasing power. The calculator surfaces the difference; the headline number alone misleads. Get the real housing number, for your actual situation. Not a city average — the rent for the size of place you would actually take, in the area you would actually live. This is the largest line for most people and the one where a city average is most misleading, because averages include neighbourhoods you would not move to. Work out the tax difference on the two gross figures. Often the second-largest line and the easiest to forget, because it never appears in either offer. Where the two places have different systems entirely, this is where a comparison quietly stops being like-for-like. Add transport, honestly. A car you would need in one city and not in the other is a large recurring cost that nobody puts in a spreadsheet until it has been paid for a year. Estimate everything else as a single line and stop refining it. Food, utilities, childcare, insurance. It is real and it is smaller than the three above, and chasing precision here while guessing at rent is effort in the wrong place. Compare what is left, and then compare the things that are not money. Whatever remains after the four lines is the honest difference. Then set it against the parts no calculator holds: who you would be near, what the work is, and how easily you could leave if it went wrong. A candidate considering a move from Chicago to NYC Current $150K in Chicago. Calculator shows $215K equivalent in NYC. Offer comes in at $190K — a real-terms pay cut. Candidate negotiates to $205K and accepts; without the calculator, would have accepted $190K thinking it was a raise. A remote candidate moving from SF to Austin while keeping SF pay Current $200K in SF. Austin equivalent: $135K. Candidate keeping $200K in Austin is effectively a 50% pay raise in real-terms purchasing power. The math behind the move is what makes one-rate remote so valuable. ClearHire holds no cost-of-living data. This page is a method, and the numbers have to come from where you would actually live. Rent for the place you would take, not the city average. The gap between those two is where most comparisons go wrong. Tax is invisible in an offer and frequently the second-largest line. A remote role paid at one rate is worth more in a cheaper place — that is the whole arithmetic, and it is also the arithmetic the employer is doing. Do the comparison before the conversation. A relocation figure is much harder to move after you have said the first number. What is left over matters more than what comes in. Two offers with the same headline can leave very different amounts. Why is a cost-of-living index not enough on its own? Because an index describes an average household and you are not one. Housing dominates the comparison for almost everybody, and what you will actually pay depends on where you would live, with whom, and how much space you need — none of which an index knows. Use an index to decide whether a comparison is worth doing, then do the four-number arithmetic for your own situation. Does ClearHire calculate this for me? No, and the page says so at the top. ClearHire holds no cost-of-living data and runs no such calculator; what it offers is the method, which is four numbers and a subtraction. Anything that presented itself as a calculator here would be putting a confident interface over data that does not exist. Which four numbers actually matter? Housing, tax, transport and one line for everything else, in that order of size for almost everybody. People get this wrong by refining the fourth — comparing grocery baskets across two cities — while getting the first one from an average rather than from a real listing for a place they would actually live. The first number is usually larger than the other three combined. How do I handle tax when the two places tax differently? Compare net, not gross, and compare it annually. A higher gross in a jurisdiction with higher income tax, a local tax, or mandatory contributions can be a lower net, and that difference is invisible in the offer letter. If either place taxes something the other does not — social contributions, a city tax, health premiums deducted at source — that belongs in this number rather than in the fourth line. Should I take a pay cut to move somewhere cheaper? Only after comparing what is left rather than what is offered, and then only if the non-money comparison also holds. A lower salary in a cheaper city can leave you better off month to month and worse off in absolute savings, which matters if you are saving toward something. Do the arithmetic first, then weigh the things that are not money — they are usually the reason the move is on the table at all. How does a remote role at a different pay rate change this? It turns the comparison into one between your actual costs and their pay band, which is a simpler question than comparing two cities. If the employer pays a location-adjusted rate, ask which location it is adjusted to and whether it is reassessed if you move. That single answer is worth more than any index, because it tells you whether the number is stable. ## Salary negotiation https://clearhire.aoneahsan.com/salary/negotiation How to open the conversation, what to say when a number comes first, and what is negotiable besides base pay. The salary negotiation guide covers when to negotiate, how much you can realistically negotiate, and what to do when the company says the offer is final. The single most important rule: negotiate after you have a written offer in hand, never before. Negotiating before the offer signals price-shopping. Once the offer is on the table, you have leverage — companies have invested time in you and want a yes. For most non-executive roles, 5–15% on base salary is realistic, plus signing bonus and equity. Smaller for entry-level, larger for senior or specialized roles. Negotiating a base salary increase. Counter with a specific number, not a range, on the first counter. "Based on the market data I have for this role and level, I am targeting $X" — back the ask with data, not feelings. Negotiating non-base levers when base is capped. Signing bonus, additional equity, extra PTO, remote-work allowance, professional-development budget. Often more flexible than base. Pick one lever, not three; multiple asks cut response rate. Walking back gracefully when the recruiter declines. "I hear you — let me think about it overnight and get back to you tomorrow." Never accept or decline in the same call as the counter. Time creates leverage; impulsivity destroys it. Deciding your number before the conversation starts. The number you will accept, the number you will ask for, and the point at which you walk are three separate decisions, and all three are easier to make before anyone is waiting for an answer. Write them down with the reasoning. In the conversation itself you are reading them out rather than working them out, which is the whole advantage. Wait until you have a written offer. Negotiating before the offer signals price-shopping. Once the offer is in writing, you have real leverage. Research the band before responding. Use /salary/calculator + 1–2 outside sources. Know the realistic range for the role + level + location. Bring data. Counter once with specifics. Specific number 5–15% above the offer with a specific reason. Single counter — going back-and-forth weakens position. Negotiate non-base levers if base is capped. Signing bonus, additional equity, PTO, remote allowance. Often more flexible. One lever, not three. Close cleanly. When you accept, do it in writing within 1–2 days. Confirm all negotiated terms. A clean close starts the relationship on the right foot. A candidate negotiating a $5K base increase Counter phrasing exactly as practiced. Recruiter says base is capped. Candidate uses non-base lever — asks for $10K signing bonus instead. Recruiter approves. Net Year 1 gain greater than the original ask. A candidate countering once, with a reason Offered below the range they had researched, they replied with the two sources, the level they had been hired at, and a single number. The recruiter came back with most of the gap closed and a signing bonus for the rest. The counter took one message, and the reason it worked is that it was answerable. Negotiate AFTER you have a written offer, never before. 5–15% on base is realistic for most non-executive roles. Counter with a specific number, not a range, on the first counter. Pick ONE non-base lever when base is capped — multiple asks cut response rate. Never accept or decline in the same call — buy a day for thinking. Silence after a counter is normal and is not a refusal — recruiters check with the hiring manager, and that takes days. Get every verbally agreed line into the written offer before you resign anything. How much can I realistically expect to move a base salary? Enough to be worth asking, and less than the internet implies. A counter grounded in a specific band and a specific reason moves offers often; a counter grounded in what you would like rarely does. The size depends on where the original number sat in the band, which is why the research comes before the counter — if the offer was already at the top, the movement will be in the other levers instead. What do I say when they ask for my expected salary first? Give a researched range for the role rather than your current pay, and say what it is based on. Your current salary is a fact about your last employer, not about this job, and anchoring on it is how an underpaid role follows you into the next one. If they press for a single figure, name the number you decided in advance and say you are flexible on the shape of the package. Is it safe to negotiate, or can an offer be withdrawn? One polite, specific counter is normal and almost never costs an offer. What does cost offers is negotiating in bad faith — accepting verbally and then re-opening, inventing a competing offer, or repeatedly countering the same line after a clear no. Ask once, ask well, and be prepared to accept the answer. What is negotiable when they say base is capped? Signing bonus, equity, start date, title, review timing, remote arrangement, learning budget and holiday, roughly in that order of how often they move. A capped base is frequently a real constraint — bands are set above the hiring manager — and treating it as a bluff wastes the goodwill you need for the levers that are genuinely available. Ask which of them has room; recruiters will usually tell you. Should I negotiate an internal promotion the same way? The mechanics are the same and the timing is not. An internal raise is decided in a cycle, against a budget that was allocated months earlier, so the conversation that matters happens well before the number is written. Make the case when the planning happens, not when the letter arrives, and bring the same specifics you would to an external negotiation. How do I close the conversation once we have agreed? Confirm the whole package in writing and stop negotiating. Restate base, bonus, equity, start date and anything agreed verbally in one short message, and ask for the updated letter. Continuing to push after agreement — or raising a new line once the paperwork is moving — is the one behaviour that reliably sours a start. ## Salary ranges https://clearhire.aoneahsan.com/salary/ranges How pay varies by role, level and industry, why a single published range is rarely the whole picture, and where to get one — because ClearHire does not publish salary data. ClearHire does not publish salary ranges, and this page will not invent one. What it can usefully do is explain how a range is built, why two sources disagree about the same job, and how to read one without over-trusting it — because the mistake that costs money is not picking the wrong number, it is treating any single number as the market. A range is an aggregate of a set of people who chose to report, at some point in the past, under a job title that may not mean the same thing at two companies. Every one of those qualifiers moves the figure, and none of them is visible on the chart. Setting a target before you apply. Decide the number, and the reason for it, before anyone asks. A figure you can justify survives being questioned; one you picked off a chart does not, and the question always comes. Reading a recruiter's range. A stated band tells you what the company has budgeted, not what the role is worth. Where it sits against two independent sources is the useful signal — and if it sits well below both, that is information about the company rather than about you. Understanding why two sources disagree. Job titles are not standardised, so the same word covers different jobs at different companies. Where two sources diverge sharply, the title is usually doing different work in each — which is worth knowing before an interview, not after an offer. Building a defensible number rather than a hopeful one. A number you can explain survives a follow-up question; a number you picked does not. Write down the two sources, the level you are targeting, and the adjustment you made for location and package shape. The written version is what you read from when the conversation happens, and the act of writing it usually changes the number. Be specific about the role, the level and the place. "Senior backend engineer, Lahore" produces something usable. "Engineer" produces a number so wide it can support any position you already held, which is how a range gets used to confirm a decision rather than to inform one. Find the sample size and the date, or discount the source. A range with neither is a rumour with axes. Twelve months is old in a moving market, and a handful of reports is a handful of people rather than a market. Read two sources that disagree, not one that agrees with you. Where two independent sources overlap is the part worth relying on. Where they diverge tells you the title means different things at different companies, which is itself useful before an interview. Convert base into the whole package before comparing. Base alone undersells most office roles once a bonus, an employer pension contribution and anything with a number on it are counted. The total-package calculator does that arithmetic on figures you type; it looks nothing up. Decide your number before the conversation, and write down why. A figure you can justify survives being questioned. A figure you picked from a chart does not, and the question always comes. A senior PM checking the band before negotiating Range for senior PM in target metro is $180K–$230K base. Recruiter offers $190K. Candidate references the data and counters at $215K. Recruiter approves $205K. Without the data, candidate would have accepted the initial offer. A candidate spotting a below-market recruiter range Recruiter range: $130K–$150K. ClearHire data + Glassdoor: $160K–$185K for the level. Candidate politely pushes back; recruiter raises ceiling to $165K. Worth the 30 seconds of validation. ClearHire publishes no salary dataset. Any page here that appears to quote one is wrong and we want to hear about it. A single published range is one sample of one population, aged by however long since it was collected. Two sources that agree are worth more than one that flatters you. Job titles are not standardised. "Senior" at a forty-person company and at a four-thousand-person company are different jobs with the same word on them. Base is not the package. Run the arithmetic before comparing two offers, not after accepting one. A range tells you what a role paid other people. What it pays you is decided in a conversation, and the number is only one of the things being decided. Why do two salary sources disagree about the same job? Because they are usually measuring different populations and calling them the same thing. One may be self-reported by people who chose to report, another drawn from job adverts that list a band they intend to hire below, another from a survey of a specific industry in a specific year. None of that is visible in the headline number. Two sources disagreeing is the normal case, and the useful information is in why. Does ClearHire publish its own salary data? No. ClearHire holds no compensation dataset and this page will not invent one — it explains how ranges are built and how to read them, and points you at sources that do collect data. Saying so plainly matters more than it might seem: a page that implied it had numbers would be the most useful-looking and least trustworthy thing on the site. What should I look for before trusting a published range? The sample size, the date and the exact definition of the role. A range built on a handful of responses is noise; a range from three years ago is describing a different market; and a title means different things at different companies, so a range for a title without a level attached is nearly meaningless. If a source will not tell you those three things, discount it rather than using it carefully. Is the range in a job advert the real range? It is the range they are allowed to advertise, which is usually wider than the range they intend to pay. Many employers post a band spanning two levels and hire in the lower half. Treat the top of an advertised band as reachable rather than expected, and ask early which level the role is scoped at — that question narrows the band far more than any negotiation will. How do I compare a range against an actual offer? Convert both into the whole package before comparing. A base at the bottom of a band with a real bonus, a match and equity can beat a base at the top with none of those, and comparing base against base gets that backwards. Build one annual figure for each, write down what you assumed about bonus attainment and vesting, and compare those. What if I cannot find any range for my role? Triangulate from adjacent roles and ask people who do the job. Very specific or very new roles often have no published data at all, and the honest answer is a wider range with lower confidence rather than a precise number with none. Two conversations with people actually doing the work will usually beat any dataset you can find for a niche title. ## One box, four kinds of answer https://clearhire.aoneahsan.com/search Jobs, companies, career tools and writing. Results stay in their own groups rather than being merged into a single list — a ranking that puts a job posting above a guide has invented a comparison nobody can check. Jobs, companies, career tools and writing. Results stay in their own groups rather than being merged into a single list — a ranking that puts a job posting above a guide has invented a comparison nobody can check. Within a group, a match in the title outranks a match in the body, and a more recent thing outranks an older one when the match is otherwise equal. That is the whole rule. Nothing here is promoted, nobody pays to appear higher, and there is no personalisation — two people searching the same word get the same page. To put a guide above a job you would need a number saying how much more useful the guide is. That number does not exist, so blending the lists would mean inventing it and then presenting it as a result. Profiles are not in these results. Searching candidates is an employer product with its own rules about who can be found and who has agreed to be — talent search, which is part of Pro. A closed posting stops appearing here on the day it closes. It is not hidden from you specifically — it is gone from the index for everyone. ## Search companies https://clearhire.aoneahsan.com/search/companies Search the ClearHire company directory by name, industry or city. Every listing carries one checkable fact: whether the company answers verification requests. The directory is searched by name, by industry and by city, so a city name often lands better than a company name you are half sure of. A company directory is usually a list of logos. This one records one extra fact, and it is the only fact ClearHire can actually observe: whether the company answers when somebody asks it to confirm a role from its own records. Search and filtering happen on this page. Nothing you type is sent anywhere. A countersignature count is a count of records, not of employees. A company with 3,000 staff and one countersigned role has been asked once. ## Search jobs https://clearhire.aoneahsan.com/search/jobs Search jobs by title, skill, company, location, pay and contract — and filter to employers that answer verification requests. Every board lists jobs. This one can tell you who signs. Every board lists jobs. This one can tell you who signs: whether the employer has countersigned a former employee's record from its own files. Hybrid is not remote, and a board that pretends otherwise wastes a week of someone's life — so the remote filter hides hybrid as well as on-site. A saved search keeps the whole address bar, filters included. Turning alerts on emails you when something new matches it. Searching happens against the postings themselves. A posting with no band is not hidden by default — plenty of good ones omit it — but you can insist. ## Sitemap https://clearhire.aoneahsan.com/sitemap Every public page on ClearHire, grouped by what you came for, with search across page names, addresses and descriptions. The ClearHire sitemap lists every public page on the site, grouped by what you came for — career tools, interview resources, company insights, pay and offers, career planning, and the pages about ClearHire itself. Four machine-readable files sit beside it for search engines and AI crawlers: sitemap.xml, robots.txt, feed.xml and llms.txt. All four are generated from the same route registry on every build, so they cannot drift from the list a person reads. ## Ten layouts. The same words come out of all of them. https://clearhire.aoneahsan.com/templates A template decides where your experience sits on the page, how much of it fits, and whether a parser can find it. It does not decide what you have done. Read what each one is for before you commit a resume to it. Five are free and stay free. Five are Pro, and Pro buys layout and volume — <1>verified employment is the same on both plans, because credibility is not something a plan should be able to sell you. The preview is the layout's block structure, drawn to A4 proportions. It is not a photograph of a finished document, because your document does not exist yet. Column (Free). Skills and tools live in a narrow left column so the experience prose is not carrying a list of forty technologies. Countersign (Free). Ledger with a countersignature column: each verified role carries its confirmation on the same line, and unverified roles simply do not. Docket (Pro). Thesis compressed into two columns for a hard page limit. New, and it shows: nobody has rated it yet. Dossier (Pro). A header block and a real summary paragraph, for the readers who want the argument before the evidence. First (Free). Education above experience and a real projects block, so a short work history is not the first thing the page apologises for. Folio (Free). The tightest layout here. It fits more, and it reads as a record rather than as a pitch — which suits some readers and not others. Index (Pro). Two dense columns. It fits the most of any layout here, and it is the one most likely to need an ATS check before you send it. Ledger (Free). One column, ruled sections, nothing decorative. The layout every parser reads correctly and no reader complains about. Margin (Pro). Dates sit in their own rail against a hairline, so the shape of a career is legible before a word of it is read. Plain (Free). No rules, no columns, and no styling a parser has to guess at. The safest layout to send into a system you know nothing about. Thesis (Pro). The only layout here that expects to run past two pages, with a numbered publications section that keeps its numbering across a page break. Switching template moves your words; it never edits them. A weak bullet is weak in all ten. The <1>career tools are where the wording gets worked on. Two-column layouts are read correctly by most systems and badly by a few, and we cannot tell you which one an employer runs. Run the <1>ATS check on the export. A Pro layout is a layout. The verified mark comes from a named company countersigning a role, and it looks identical on the free templates — <1>how that works. Every template exports to PDF and DOCX. On Free the export carries a small ClearHire mark in the footer; on Pro it does not. That is the whole difference in the exported file. ## Terms of use https://clearhire.aoneahsan.com/terms What you agree to, and what ClearHire claims. Clause 05 states exactly what a verified employment record asserts — and the six things it does not. The ClearHire terms of use are thirteen numbered clauses covering accounts, acceptable use, content ownership, verified employment, plans and payment, and liability. Clause 05 is the one that matters. A countersigned employment record is a statement by a named individual at a named company that, according to that company’s own employment records, you held a stated job title between stated dates. It is not a reference, not a background check, not an identity check, and not a statement about why the employment ended. An unanswered request expires as unconfirmed rather than as declined or false, and a declined record is private to you, the company and ClearHire. ## Career tools https://clearhire.aoneahsan.com/tools Fifty-three free career tools — resume scoring, cover letters, salary estimates, interview preparation. Most of them want nothing from you. The ClearHire tool catalogue is fifty-three browser-based career tools grouped by what you are trying to do: writing a resume, preparing for an interview, working out what a role should pay, or deciding what to do next. Most run entirely in your browser and need no account. An account is only required where a tool has to keep something for you — a saved resume, a tracked application, a pinned list. These are guidance, not verdicts. A resume score is one reading of one document by one published rubric; no tool here can tell you whether a company will call. What ClearHire can prove is separate, and it lives in verified employment. ## Action verbs https://clearhire.aoneahsan.com/tools/action-verbs A working list, grouped by what the verb actually claims about you. ## ATS check https://clearhire.aoneahsan.com/tools/ats-checker Paste a resume, get a score out of 100 and the specific lines that cost you points. ## Benefits calculator https://clearhire.aoneahsan.com/tools/benefits-calculator Puts a number on the non-salary part, so two offers can be compared on one scale. ## Bio generator https://clearhire.aoneahsan.com/tools/bio-generator Three lengths of the same bio, from one set of facts you supply. ## Brand statement https://clearhire.aoneahsan.com/tools/brand-statement One sentence that survives being read aloud. Most first drafts do not. ## Bullet point generator https://clearhire.aoneahsan.com/tools/bullet-generator Turns what you did into a line that leads with the outcome instead of the duty. ## Business card https://clearhire.aoneahsan.com/tools/business-card A card layout you can print. Your details only — nothing is stored. ## Career pivot https://clearhire.aoneahsan.com/tools/career-pivot Which parts of your experience travel to a different field, and which do not. ## Career quiz https://clearhire.aoneahsan.com/tools/career-quiz Twelve questions and a reading, not a personality type. You can disagree with it. ## Career timeline https://clearhire.aoneahsan.com/tools/career-timeline Lays your roles out in order so gaps and overlaps are visible before someone asks. ## Cold outreach https://clearhire.aoneahsan.com/tools/cold-outreach A short first message that says why you, why them, and what you are asking for. ## Company research https://clearhire.aoneahsan.com/tools/company-research How to find out what a company is actually like, and which sources are worth your time. It looks nothing up for you and invents no figures. ## Counter-offer letter https://clearhire.aoneahsan.com/tools/counter-offer A reply that names a figure and keeps the door open if the answer is no. ## Elevator pitch https://clearhire.aoneahsan.com/tools/elevator-pitch Answers "tell me about yourself" in under thirty seconds, one template set. ## Email templates https://clearhire.aoneahsan.com/tools/email-templates One set, not two. Thank-yous, follow-ups, withdrawals and the awkward ones. ## Experience letter https://clearhire.aoneahsan.com/tools/experience-letter A letter asking a past employer to confirm a role in writing. Different from a reference. ## First job guide https://clearhire.aoneahsan.com/tools/first-job-guide How to apply with no work history, without pretending you have one. ## Follow-up reminder https://clearhire.aoneahsan.com/tools/follow-up-reminder Works out when a follow-up is reasonable, and writes the one you send. ## Format validator https://clearhire.aoneahsan.com/tools/format-validator Flags the layout choices that survive a human reader and confuse a parser. ## GPA converter https://clearhire.aoneahsan.com/tools/gpa-converter Arithmetic between grading scales, with the conversion it used shown. ## Industry analyser https://clearhire.aoneahsan.com/tools/industry-analyzer Which sectors your answers point at, and what would have to be true for that to work. ## Industry trends https://clearhire.aoneahsan.com/tools/industry-trends How to read a sector for yourself. It publishes no forecast of its own. ## Internship resume guide https://clearhire.aoneahsan.com/tools/internship-resume What goes on a resume when the work history is short, and what to stop apologising for. ## Interview questions https://clearhire.aoneahsan.com/tools/interview-questions One question bank, not three. Grouped by what the interviewer is actually testing. ## Interview scorecard https://clearhire.aoneahsan.com/tools/interview-scorecard Write down what happened while you remember it. Scored against one rubric, not a mood. ## Interview tracker https://clearhire.aoneahsan.com/tools/interview-tracker Keeps dates, people and notes per interview — so it needs somewhere to keep them. ## Job description analyser https://clearhire.aoneahsan.com/tools/jd-analyzer Separates the requirements that are real from the ones every ad copies. ## Keyword scanner https://clearhire.aoneahsan.com/tools/keyword-scanner Which words from a job ad appear in your resume, and which do not. ## LinkedIn headline https://clearhire.aoneahsan.com/tools/linkedin-headline Fits the character limit and still says something. Counts as you type. ## LinkedIn messages https://clearhire.aoneahsan.com/tools/linkedin-messages Connection notes and follow-ups that do not read as a mail merge. ## Mock interview https://clearhire.aoneahsan.com/tools/mock-interview A run through real questions at your own pace, with a place to write each answer down. ## Negotiation scripts https://clearhire.aoneahsan.com/tools/negotiation-scripts Wording for the conversation, filled in with your number rather than a suggested one. ## Offer comparison https://clearhire.aoneahsan.com/tools/offer-compare Two offers, the same rows, one total each. The weighting is yours to set. ## One-page optimiser https://clearhire.aoneahsan.com/tools/one-page-optimizer Ranks what to cut first when a two-page resume has to become one. ## Reference request https://clearhire.aoneahsan.com/tools/reference-request Asks someone properly, and makes it easy for them to say no. ## Relocation calculator https://clearhire.aoneahsan.com/tools/relocation-calculator Adjusts an offer by the cost figures you supply. It ships no cost-of-living database. ## Resignation letter https://clearhire.aoneahsan.com/tools/resignation-letter Short, dated, and no burnt bridges. One template set, not two. ## Resume compare https://clearhire.aoneahsan.com/tools/resume-compare Two versions side by side, scored against the same rubric so the comparison means something. ## Skills gap https://clearhire.aoneahsan.com/tools/skills-gap The distance between where you are and a role you want, written as steps. ## STAR method https://clearhire.aoneahsan.com/tools/star-method Four beats, in order, with worked examples and somewhere to practise. ## Total compensation https://clearhire.aoneahsan.com/tools/total-comp Base, bonus, equity and benefits added up, with each assumption stated beside it. ## Knowing what to ask about your rights at work https://clearhire.aoneahsan.com/workplace-rights Not legal advice, and it cannot be: employment law is jurisdictional. What this page gives you is the questions worth asking and where the real answers live. This page is not legal advice and cannot be. Employment law differs by country, often by region within a country, and frequently by the exact wording of a contract — so a page that told you what you are entitled to would be wrong for most of the people reading it, and wrong in the direction that causes harm. What a page can usefully do is name the questions that turn out to matter, describe the documents that answer them, and point at the kinds of organisation whose job it is to give a real answer for where you actually are. Every heading below is a question rather than a statement, deliberately. If you need to know your position, the answer comes from your contract, your local labour authority, a union if you have one, or a qualified employment lawyer — and it is worth getting before you act rather than after. Something happened and you do not know if it was allowed. A change to hours, a withheld payment, a dismissal. The first useful step is almost always reading the contract and writing down dates, not asking the internet. You are about to sign something. A contract, a settlement, a non-compete. This is the cheapest moment to get advice and the most common one to skip it. You are leaving and want to leave cleanly. Notice, handover, references, and what happens to work you made. Most of this is in the contract you signed, and most people have not read it since. Find and read the contract. Not the offer letter — the contract, plus any staff handbook it refers to. Handbooks are often incorporated by reference, which means their terms bind you even though nobody handed you one. Whatever you are trying to establish, this is where it starts. Write down the sequence, with dates. What happened, when, who was present, what was said and in what channel. Contemporaneous notes are worth more than a recollection assembled later, and every process you might use will ask for exactly this. Keep the paper trail somewhere that is not the company's. People lose access to a work account on the day the relationship ends, which is usually the day the emails matter. Forward what is yours to keep — being careful not to take anything confidential that is not. Find the right kind of answer for where you are. A national labour authority, a workers' advice service, a union representative, or an employment lawyer. Which of these is available and useful depends entirely on your jurisdiction, which is why this page names the categories rather than an organisation. Check the time limits before anything else. Almost every employment process has a deadline, and some of them are short. It is the single question worth asking first, because it is the only one where a delay closes the door regardless of the merits. A disputed final payment The contract's notice clause and the dated handover email between them settled what was owed, without anybody needing to interpret a statute. Most disputes that feel legal are answered by a document somebody already has. A non-compete presented at signing Whether such a clause is enforceable varies enormously by jurisdiction, and the answer given by a colleague in another country was confidently wrong. An hour with someone qualified locally is the difference between a guess and a position. Ask about time limits first. Merits can be argued later; a missed deadline usually cannot. Put important things in writing, politely, and keep a copy outside the company's systems. A handbook referenced in a contract is generally part of it. Ask for a copy, and ask which version applies. Advice from a colleague in a different country is worth exactly nothing on a question of law, however confidently it is given. Free is not the same as unqualified. Many jurisdictions have a real advice service; find out whether yours does before paying anyone. ClearHire records what a company confirmed about your employment. That is a fact about dates and a job title — it is not evidence about a dispute, and it does not substitute for advice. Can this page tell me what my rights are? No, and any page that claimed to would be wrong for most of the people reading it. Employment law differs by country, often by region, and frequently by the exact wording of your contract. What this page offers is the questions worth asking and where to take them — which is genuinely useful and is not the same thing as an answer. Something happened at work and I do not know if it was allowed. What now? Write down what happened, with dates, before anything else. Memory reorganises itself surprisingly fast and a contemporaneous note is worth far more than a recollection later — to a lawyer, to HR, and to you. Then find out which rules apply where you work, because that determines who you even ask. Who should I ask? Someone whose advice is specific to your jurisdiction and your contract. Depending on where you are that may be a union, a government employment service, a legal clinic, or an employment lawyer, and many offer a first conversation free. Advice from a colleague in another country is worse than no advice, because it sounds authoritative and is not. Should I read something before I sign it? Yes, and the parts worth reading are usually the ones about leaving rather than joining. Notice period, restrictive covenants, intellectual property and what happens to unvested equity are where the surprises live, and they are hardest to change after signature. If a clause is unclear, asking what it means in practice is a normal question. Is it worth raising something formally? That is a decision only you can make, and it is worth making with information rather than in the moment. Formal processes have time limits in most places, so a decision deferred indefinitely can become a decision made. Finding out the deadline early keeps the option open, which is different from exercising it. How do I leave cleanly? Give the notice the contract requires, put the important things in writing, and take copies of what is yours before your access ends. Most of what goes wrong at the end is administrative rather than adversarial — an unclaimed expense, an unclear final payment, a reference nobody agreed. Handling those in writing while you are still there is much easier than afterwards.