Resume, evidence and ATS applications

A vacancy mixes activities, working conditions, mandatory requirements and preferences. Separate these layers before editing your resume. In a fictional customer-support role, ‘resolve requests’ describes the work; ‘Saturday availability’ is a condition; ‘English for customer conversations’ asks for a demonstrable capability; ‘industry experience is a plus’ carries a different meaning from an explicit requirement.

Create three columns: what they ask for, what evidence I have, what needs clarification. For ‘monitor indicators’, a spreadsheet you maintained to identify delayed orders says more than ‘analytical mindset’. Record a gap when you do not meet a requirement. Do not automatically treat a preference as disqualifying, or claim a licence or availability you do not have.

Target one family of roles per version. A resume simultaneously selling customer support, engineering and design makes your contribution harder to understand. Keep a broad evidence inventory and select from it for each application. The vacancy guides selection; it does not justify copying duties you have never performed.

Before searching for impressive words, recover real situations. For each job, project, course or volunteering activity, note the problem, your action, collaborators, tool or method, observed outcome and a source that helps you recall it accurately. That source might be your own file, a public deliverable or a private note; it need not accompany the application.

Illustrative case: someone organized a shop’s orders. Their inventory could say ‘spreadsheet with order, deadline and owner; daily updates; identified unassigned orders; handed them to the team’. Even without reliable numbers, this supports a specific contribution. ‘Increased revenue’ would require different evidence.

Separate individual and team work: ‘created the spreadsheet’ differs from ‘helped implement it’. Keep an explanation of one difficulty and one decision, because an interview may explore them. Remove customer data, confidential information and internal documents from public samples. Access to a work file does not mean you may publish it.

Allocate space according to relevance without changing dates or titles to appear more suitable. A recent, relevant role may deserve three examples; an older, less relevant one may need a short entry. Chronological order still helps a reader reconstruct your history even when the amount of detail varies.

Consider a cashier moving into administrative support. Reconciling amounts, recording discrepancies and organizing documents may transfer well. That does not automatically turn the cashier role into financial analysis. Keep the actual title and highlight transferable activities.

Removing an irrelevant course is editing; inventing a qualification is different. Avoid listing every subject studied or every tool seen in a video. If removing an experience creates an important gap in the story, a short line may help more than silence. Final length depends on context and necessary information, not a universal one-page rule.

A useful bullet shows what you did and why it mattered. Use action + object + context or method + an effect you can support. Not every sentence needs every component; never invent an outcome to complete the formula.

Illustrative case: ‘Responsible for spreadsheets’ becomes ‘Checked orders in the tracking spreadsheet and flagged deadline discrepancies to the customer-support team’. If the person created the process, ‘Created’ may fit; if they only used it, that verb overstates ownership.

‘Proactive, organized and results-driven’ gives the reader no situation to assess. ‘Organized files by customer and date so the team could locate contracts’ supplies an action and purpose without a percentage. Write plainly first. Then remove repetition, internal jargon and words that add no meaning. In an interview, you should be able to explain the process, a difficulty and your actual role.

Numbers can describe volume, time, quality or outcomes. Choose a measure you actually know. ‘Checked approximately 40 orders per week’ conveys scale; ‘increased sales by 40%’ attributes an outcome and needs much stronger support. Label estimates as estimates.

In a fictional example, a process fell from 50 to 35 minutes: 15 minutes saved, or 15 ÷ 50 = 30%. ‘30% faster’ can confuse duration with speed; prefer ‘reduced completion time by 30%’. State what was measured and the context. If several people changed the process, describe your contribution without claiming the entire result.

When reliable records are unavailable, use a concrete deliverable: a documented procedure, an introduced check, customers served or an identified problem. Do not manufacture a percentage because the sentence feels weak. Sensitive commercial figures may require another form of evidence; percentages can also disclose confidential information.

Without previous employment, look for experiences that make a capability observable: a school project, event organization, community work, help in a family business or independent work. Label the context accurately. A strong academic project does not become ‘consulting’ because it turned out well.

Fictional example: a student organized registrations for a school fair. ‘Built a form, checked duplicate registrations and organized the participant list with the team’ demonstrates organization and data handling. Add an anonymized sample if sharing is appropriate. Do not claim team leadership when decisions were collective.

A demonstration project can fill an evidence gap: build an order spreadsheet with fictional data, explain validation and show a corrected discrepancy. Label it as a simulation. The application gains a sample of reasoning, not retroactive professional experience. Education can precede experience when it is the strongest relevant evidence; avoid filling space with unrelated certificates.

For a career change, connect a demonstrated capability to the new task and acknowledge what is missing. Someone from retail may have customer-service and stock-control experience; that can help in operations, but does not prove proficiency in software they have never used. Show a specific project or learning example for the new gap.

Freelance or informal work can be described through actual services, dates and deliverables. Do not invent a company or title to make it appear formal. If work was occasional, do not describe the entire period as continuous full-time employment.

A break may receive a brief, truthful description when it helps explain the timeline, without disclosing intimate details. Do not change dates to hide it. Prioritize relevant information in the resume; answer application-form questions accurately. Earlier experience retains value, but a transition may require evidence of new skills rather than a new title at the top of the page.

Start with your name, useful contact details and location at the necessary level, followed by a short introduction, experience or projects, education and relevant skills. Order can change: education and projects may lead for a first job; experience may lead when it provides stronger evidence. Use recognizable section headings.

This course’s templates use one column and text in the document body. Replace bracketed fields, remove instructions and delete sections that add no evidence. Duplicate an experience block only when needed. Readable type and space between sections help more than squeezing everything onto one page.

A sophisticated visual composition may suit a portfolio; an application file also needs to work when fields are extracted. Greenhouse documents parsing problems associated with columns, tables and information in headers, among other factors. This supports a conservative layout choice, not a claim that every alternative layout will fail.

An opening summary helps when it connects your experience to the target role. Avoid a sentence that could describe anyone: ‘Seeking an opportunity to grow and contribute’. Prefer your field, a relevant capability and a brief context, without retelling the entire resume.

Illustrative wording for someone who actually has this experience: ‘Customer-support professional with experience tracking orders and documenting service issues. Uses spreadsheets to organize deadlines and support communication between store staff and customers’. For a career change, state the target clearly without claiming you already hold the new profession.

An early-career profile might say ‘Business administration student with a registration-tracking project and an interest in operational support’. The project supports the introduction; ‘management expert’ would not be proportionate. If a summary only repeats the title and adjectives, shorten or remove it. It should help readers interpret the evidence below, rather than function as a slogan.

‘Excel: 90%’ has no shared scale. Describe relevant capabilities: organizing tables, filtering, checking duplicates or building a pivot table—only when you can do and explain them. A tool name can help retrieval; experience demonstrating its use supports evaluation.

Distinguish exposure, practice and independent use. ‘Introductory SQL course with a query project using fictional data’ is more precise than ‘advanced SQL’ for a recent learner. If AI helped produce a query, explain the problem, how you checked the output and what you can correct. Generating an output does not demonstrate command of the whole technology.

For languages without a formal assessment, describe use: reading documentation, participating in meetings or written customer support. A certificate may carry its own level and date; do not turn self-assessment into certification. Interpersonal skills also need situations: a real negotiation or organization example says more than listing ‘leadership’ and ‘resilience’.

State the qualification, institution and status. Make ongoing study explicit, using an expected completion date only when appropriate. An unfinished programme should not appear as a completed degree; relevant studies can still be described.

Select supplementary courses for what they add to the role. A short spreadsheet course can show initial preparation, but does not replace experience or a project demonstrating application. Hours attended are not, by themselves, evidence of proficiency. Do not turn a participation certificate into a professional licence.

Fictional example: ‘Business Administration — Institution X, in progress; expected completion 2027’. When translating, preserve the original qualification and add a short explanation where needed. A free translation does not establish academic equivalence or professional eligibility in another country. If a role requires registration, a current certification or formal recognition, check the specific requirement with the relevant body and employer; this guide does not validate credentials.

A resume selects evidence for a vacancy; a professional profile can show a broader history; a portfolio lets someone examine deliverables. They need not repeat identical text, but dates, titles and authorship should agree. A profile headline can explain your field without changing the actual title in your work history.

A useful sample answers: what was the problem, what constraints existed, what did you do, what was delivered and what remained limited? For a spreadsheet, show inputs, checking rules and a corrected case. For visual work, explain audience, purpose and decisions. Label personal, academic and commercial projects.

Open the link as a visitor before submitting: does it require permission, expose someone’s data or rely on an unfamiliar download? Use a page or file with sufficient context. If you cannot publish the deliverable, explain the reasoning through an authorized anonymized example or a clearly identified simulation. An attractive profile does not compensate for inaccessible evidence.

ATS describes a category of systems for tracking applications. A process may include extracting file fields, application questions, search, ordering, assessment and stage changes. Configuration and features vary. Do not assume one universal robot assigns the same score to every resume.

Parsing turns document information into fields such as experience and education. Greenhouse documents that a failure may leave the resume attached without populating those fields. Gupy’s notice describes optional compatibility ordering and employer-defined criteria. These are different mechanisms.

Hypothetical example: the system correctly extracts your title, but you state that you do not hold an explicitly required licence. Changing the font does not fix that mismatch. In another case, the title lands in the wrong field: reviewing extraction can help. Diagnose the layer before changing everything. Without process information, a rejection does not prove the file was ‘blocked by the ATS’.

The same activity can have different names. If a vacancy asks for ‘reconciliation’ and you checked entries and discrepancies, explain that correspondence precisely. Use the recognizable term when it describes what you did. Do not paste the full requirements list as if it were your experience.

Expanding an acronym on first use can help the reader: ‘customer relationship management (CRM)’, followed by its actual use. Naming a platform you have never used does not become truthful because you studied a competitor. Explain the transferable capability and its limit.

Artificial repetition consumes space and reduces clarity. White text, hidden keywords and instructions aimed at an AI evaluator provide no professional evidence. The useful strategy is to make a real match easy to recognize. An external tool may flag missing words, but its score does not necessarily know the employer’s configuration and cannot replace critical reading.

Follow the application’s accepted formats and limits. DOCX and PDF are not universally good or bad: the system and file construction matter. When sending a PDF, export actual text from the editor rather than a photograph or screenshot. A visually readable file may not expose useful text for extraction.

Run a simple check: select and copy text from the final file into a plain-text editor; inspect the sequence of name, contact details, titles and dates. This finds some defects but does not reproduce the employer’s parser. After upload, check populated fields whenever the platform shows them.

The Greenhouse documentation consulted specifies a 2.5 MB parsing limit; this is not a universal upload rule. Remove unnecessary elements, retain an editable copy and use a recognizable filename such as First_Last_Operations_EN.pdf. Renaming .docx to .pdf does not convert the document; export the required format.

Gupy is particularly relevant to applications involving Brazilian employers. Read the actual flow you are using. Its candidate notice describes CV-based autofill, professional data, additional questions and modes that may use the attachment. Employers differ in purchased features and criteria, so an old tip about one field should not become a rule for every process.

After import, review titles, dates, experience, education and skills wherever the form allows. If part of your job title landed in the institution field, correct that field; uploading a more attractive PDF does not guarantee a fix. Answer vacancy-specific questions factually, including availability and required experience.

According to the company’s notice, AI ordering is optional and recruitment makes advancement decisions. This is the vendor’s description, not an independent audit of every process. An external ‘Gupy compatibility’ calculator cannot establish your actual position in a selection process.

Before confirming submission, check three surfaces: the attachment, imported or typed fields, and vacancy-specific answers. Compare dates and titles, open the final attachment, and test contact details and links. A correction in your local document may not have reached the attachment or profile.

Review example: the PDF says ‘Assistant, March 2023–June 2025’, while the form shows only 2025. Correct the form where possible. If a mandatory field cannot represent your situation accurately, seek the process guidance rather than choosing a false answer simply to continue.

Keep your own note of the vacancy, date, submitted version and confirmation. Clear filenames help avoid selecting an old version. Do not interpret clicking a button as proof of receipt when an error occurred; check the service’s confirmation. This course neither submits applications nor accesses accounts; any record remains in the copy you choose to keep.

Translate the contribution, not just individual words. Portuguese ‘atendimento’ may mean customer service, customer support or reception, depending on the work. ‘Assistente’ does not become manager; coordinating one stage does not imply managing people. Where a local title is ambiguous, keep the original and add a brief functional explanation.

Illustrative example: ‘Acompanhava pedidos e sinalizava atrasos à equipe’ can become ‘Tracked orders and flagged delays to the team’. ‘Led end-to-end operational transformation’ would invent scale and leadership. Use past tense for completed work and a consistent form for current activities. Numbers, dates and responsibilities should remain equivalent across versions.

Educational qualifications and licences do not gain equivalence through translation. Official names may remain with a description. Adapt context too: explain a local acronym an international reader may not recognize. The English template is an editable starting point, not a compulsory standard for every country or a claim of fluency.

English does not identify one hiring market. ‘CV’ is common in ordinary UK applications; the Canadian guidance consulted uses ‘resume’. An extensive academic CV serves a different purpose again. Read the actual request before choosing format, length and information.

Local sources do not agree on every detail: the UK National Careers Service allows a note that references are available, while Canada’s Job Bank recommends providing them separately when requested. Neither approach justifies publishing other people’s contact details without agreement. Canadian guidance also discourages photographs for general resumes; do not turn that convention into a worldwide law.

For a starting version, retain professional contact details, a useful city or region and relevant evidence. Do not make the document a repository for identity documents or unrelated personal information. Work authorization and qualification recognition need checking through the appropriate process. Translating into English does not establish immigration eligibility, professional licensing or equivalence between employment arrangements.

AI can help identify repetition, suggest wording and compare a vacancy’s language with your evidence. First supply enough facts and remove unnecessary personal or confidential information. Using an external service is your choice under its terms; this course sends nothing automatically.

Copyable instruction: ‘Edit these bullets for clarity using only the supplied facts. Do not invent numbers, tools, leadership or certifications. For each version, show the original, the proposal and any uncertainty. Ask rather than filling factual gaps. Vacancy: […]. Verifiable facts: […].’

Compare every verb and number. If ‘helped organize’ becomes ‘led’, return to the actual fact. If a tool appears only because the vacancy mentioned it, remove it until supported. Read the final version aloud and explain an example without looking at the text: wording you do not understand will hinder an interview. AI can assist editing; you remain responsible for an accurate application.

When requested or useful, a cover letter or message explains a connection the resume may not make obvious. Use three parts: the opportunity and why it fits, one or two related pieces of evidence, and a concise closing with availability to discuss. Follow the requested field and format.

Fictional example: ‘I am interested in the operations-support role because it combines order tracking and customer communication. In my previous work, I checked deadlines and documented discrepancies for the responsible team. My attached resume provides that context, and I would welcome the opportunity to explain the process.’ Add an organization-specific reason only after checking it.

Avoid generic praise, long stories and repeating every role. For a career change, explain the connection and evidence of preparation. Do not treat an AI-written letter as proof of a language ability you cannot yet use at work. A useful message aids understanding; it does not create an obligation to reply or replace the role’s requirements.

Start a version with the vacancy description and your evidence inventory. Identify activities, requirements and conditions. In the matrix, connect each important point to truthful evidence and record what you cannot yet demonstrate.

• Target: does the version present a recognizable family of roles?
• Match: does each central capability have an action, project or relevant study example?
• Limits: are preferences distinguished from requirements?
• Selection: does the strongest relevant evidence receive enough space?

For operations support, an order-checking example may matter more than an unrelated old course. Preserve titles, dates and context; tailoring means selecting and explaining. If a skill is genuinely missing, the useful next action may be creating a real learning sample rather than adding the word to the resume. The matrix material includes a completed case and copyable fields.

Open the Portuguese or English template and replace its fields with your facts. For each experience, write what you did, to what and in which context; add an outcome only when you can support it.

• Ownership: ‘created’, ‘contributed’ and ‘used’ describe different roles.
• Metric: check baseline, period, unit and source; label estimates.
• Skill: describe real application rather than decorative proficiency bars.
• Consistency: the document, profile and portfolio agree on dates and titles.
• Translation: changing language does not change seniority, qualifications or outcomes.

‘Organized orders by deadline and flagged delays’ is sufficient when that is the fact. It need not become ‘transformed operations’. Read each sentence as a possible interview question: be able to explain the situation and your role. Remove template instructions and brackets before submission. The annotated examples compare vague wording, supported wording and overstatement.

Use the requested format. Open the final file, inspect text and test links. In the form, compare imported information with the document and answer vacancy-specific questions.

• Readability: do name, contact details, titles and dates remain in the right sequence?
• Accuracy: is the attachment the version you just reviewed?
• Fields: was information omitted, merged or put in the wrong place?
• Privacy: is unnecessary personal or third-party information included?
• Confirmation: did the service confirm receipt or show an error?

Keep your own copy of the vacancy and submitted version. Without a parsing preview, local checks reduce some problems but cannot establish how the system interpreted everything. Confirmed submission records an application; it does not confirm review, interview or selection. Checkmenot does not apply on your behalf or mark understanding when you open a template.

No response is insufficient evidence that ‘the ATS rejected me’. Compare observations: was there an upload error? Were fields wrong? Did the role require something missing? Did an interview reveal difficulty explaining an experience? Each situation suggests a different investigation.

• File or form: correct the observed defect and check again.
• Role fit: review requirements, target role and selected evidence.
• Explanation: prepare a concrete case behind a vague claim.
• No information: retain uncertainty rather than buying an approval promise to fill the diagnostic gap.

You can keep application notes to observe patterns, but small samples, different vacancies and market changes make it difficult to attribute an outcome to one sentence. Improving clarity and fit is verifiable; guaranteeing selection is outside your control. Use the next version to address an identifiable problem while preserving truthful facts.