Ninety seconds is the average time a recruiter spends on an application they decide to consider. It is also a generous estimate.
For applications that do not pass an initial relevance check — a scan that happens in the first 10 to 15 seconds — the recruiter never reaches 90 seconds. They move to the next application. The decision is not deliberate. It is pattern recognition operating at speed on a person who has 180 more applications to process today.
There are five specific mistakes that trigger this pattern reliably. They are not obscure errors. They appear in the majority of resumes. And they are all fixable.
Mistake 1: The opening statement is about what you want, not what you offer
The summary or objective statement at the top of most resumes is written from the candidate's perspective: what kind of role they are looking for, what kind of environment they want to work in, what kind of growth opportunity they are seeking.
This is the wrong framing for a document whose entire purpose is to answer the question a recruiter is asking: why are you the right person for this specific job?
The recruiter already knows what you want. You applied. What they need to know immediately is what you bring.
Compare:
"Experienced software engineer seeking a challenging role in a fast-paced environment where I can leverage my skills and grow professionally."
versus:
"Backend engineer with 6 years building high-throughput payment infrastructure at fintech scale. Specialized in distributed transaction systems, event-driven architecture, and incident response at sub-second latency requirements."
The first sentence tells the recruiter nothing about what hiring you would mean for their company. The second one tells them exactly who you are and whether it maps to what they need. They will know within two sentences whether to keep reading.
Mistake 2: Responsibilities instead of outcomes
The most common structural error in resume bullet points is describing what you were supposed to do rather than what actually happened.
"Responsible for managing the backend API infrastructure" is a job description. It tells the recruiter what your role was. It does not tell them what you accomplished in that role, whether you did it well, or how the company benefited from having you in it.
"Rebuilt the API gateway from synchronous REST to async event-driven architecture, reducing p99 latency from 1.2 seconds to 180ms and supporting 3x traffic growth during peak season" is an outcome. It shows scope, shows specific technical choices, shows measurable impact, and shows the kind of engineer you are — someone who shipped things that mattered.
The rule: every bullet point under a role should describe a change you caused, not a task you performed.
This is the hardest change for most people to make because it requires actually sitting with the question of what changed because you were there — and for many engineers, particularly those who worked on long-running infrastructure projects where outcomes were diffuse and slow, that answer is not immediately obvious. Make it obvious. The recruiter cannot infer it.
Mistake 3: A skills section that is a wall of 40 tools
Most skills sections in engineering resumes list everything the candidate has ever touched, in no particular order, with no indication of depth or recency.
The result is a section that contains true information and conveys almost none of it. A recruiter scanning a skills section that reads "Python, Java, Scala, Go, Rust, JavaScript, TypeScript, React, Angular, Vue, AWS, GCP, Azure, Kubernetes, Docker, Terraform, Ansible, PostgreSQL, MySQL, MongoDB, Redis, Kafka, Spark, Hadoop, TensorFlow, PyTorch, scikit-learn, pandas, NumPy, Git, Jira, Confluence, Figma, Tableau" learns nothing about which of those skills you actually use, which ones you are expert in, and which ones you list because you did a two-hour tutorial four years ago.
The fix is to organize your skills section by category and depth. Primary skills — the ones you work with daily and could interview on at depth — go first and explicitly. Secondary skills — genuinely proficient but not your primary stack — go second. Tools and frameworks that you know well enough to use but would not position yourself around go last or get dropped entirely.
A skills section that communicates depth is more valuable than one that communicates breadth. The recruiter is hiring for specific requirements. Make it easy for them to see you meet those requirements rather than making them search through noise.
Mistake 4: Dates that create an unexplained gap
Employment gaps are not inherently disqualifying. Recruiters have seen the last several years of the tech job market. They understand that layoffs happened at scale, that visa situations create gaps, that health situations and family situations and personal decisions are real.
What creates friction is an unexplained gap that a recruiter has to ask about in a screen they have not scheduled yet.
If there is a meaningful gap in your work history — more than a few months — address it briefly on the resume itself. Not a full explanation. One line. "2024: Career transition following company acquisition/layoff. Completed X and Y during this period." Or simply a brief consulting note or freelance line covering the period.
This costs you two lines of resume real estate and eliminates a question mark that may be preventing your application from clearing a basic threshold check.
Mistake 5: A format that breaks ATS parsing
This one is mechanical but it is still killing applications in 2026.
Multi-column layouts, text inside tables, headers formatted as images, embedded text boxes, decorative graphics — all of these create parsing errors in ATS systems. The ATS extracts text it can read and discards the rest. A recruiter then sees a candidate profile with missing information, which reads as incomplete.
The recruiter does not know your original document was well-formatted. They see what the ATS extracted. If that looks sparse or disorganized, your application is at a structural disadvantage before your actual experience is evaluated.
The entire format specification for ATS compatibility: single column, standard section headers (Work Experience, Education, Skills), no tables, no text boxes, no images, no decorative elements, exported as a standard PDF with selectable text. That is it. Every piece of formatting beyond this is a risk with no upside.
The audit you should run before your next application
Take your current resume and check it against these five points before you submit another application. Most resumes fail at least two of them. Many fail all five.
The resume decode on JobsGlitch runs this audit automatically and adds a layer of ATS-specific analysis: it scores your resume against the actual job description you are targeting, surfaces the keyword gaps the ATS would catch, and identifies the positioning issues that would create friction at the human review stage.
It takes 60 seconds and requires no account.
Audit your resume free before your next application →
POST 6 (Track 1)
Remote Engineering Jobs: Which Companies Are Actually Remote vs. Just Pretending
Primary keyword: remote engineering jobs Secondary keywords: remote software engineer jobs 2026, which companies are truly remote, remote work tech jobs Slug: remote-engineering-jobs-which-companies-actually-remote-2026 Meta description: "Remote" means different things in different job listings. ATS data from 152K+ remote roles reveals which companies genuinely support distributed work — and which are running bait-and-switch. Estimated read time: 8 min
"Remote" is the most inconsistently used word in the current job market.
It appears on job listings where the role requires you to be in the office three days per week. It appears on listings for roles that require candidates to be within 50 miles of a specific office for "occasional in-person collaboration." It appears on listings that are marked remote during the application process and then shift to hybrid requirements during the offer negotiation. And it appears on listings for genuinely distributed roles where you will never be expected to set foot in a company office.
These are not the same job. They affect your compensation (cost-of-living adjustments), your career trajectory (visibility in distributed teams, promotion dynamics), your daily working life, and your flexibility to live where you choose. Conflating them because they all say "remote" in the title is a significant mistake.
JobsGlitch has 152,000+ remote and remote-eligible roles in its index, pulled directly from ATS platforms. Here is what that data shows about what "remote" actually means in practice — and which companies mean it.
The taxonomy: what remote actually means in 2026 job listings
Fully remote, location-agnostic: The role can be performed from anywhere. No geographic restrictions beyond timezone windows. No expectation of in-person attendance for any purpose. This is the standard most candidates assume when they see "remote" in a listing, and it is the least common form.
Fully remote, geography-restricted: The role is remote but restricted to specific countries, states, or time zones. Common reasons include tax complexity (US companies often list remote as "US only" due to state-specific payroll and benefits requirements), regulatory requirements (financial services roles with specific jurisdiction rules), and security clearance requirements. Remote but not location-agnostic.
Hybrid with a strong remote bias: You are expected to be in-person periodically — quarterly offsites, team on-sites, major events — but the default working mode is distributed. The in-person requirement is episodic rather than weekly.
Hybrid with a weak remote component: You are expected to be in-person two or three days per week. The job description calls this "flexible" or "hybrid-remote." In practice, you need to live within commuting distance of the office and the remote days are an accommodation, not the operating model.
Office-first with remote days: The role is fundamentally office-based with occasional work-from-home permitted. Sometimes listed as "remote eligible" in job aggregators because of a configuration in the ATS that technically allows it.
The first three categories are genuine remote jobs. The last two are not, regardless of how they appear in search results.
How to read a remote job listing accurately
Several signals distinguish genuine remote roles from hybrid roles mislabeled as remote.
Presence of a specific office location in the listing. If a "remote" job listing prominently features a specific city and address, the likelihood of meaningful in-person expectations is high. Fully remote roles at genuinely distributed companies rarely anchor the listing to a specific office.
The phrase "in our [City] office." If this phrase appears anywhere in the job description, the company has an office expectation regardless of what the top-line listing says.
Geographic compensation tiers. Companies with genuine location-agnostic remote posture often have explicit geographic compensation tiers in their listings — higher pay for San Francisco and New York, lower pay for lower-cost markets. This transparency is a positive signal. Companies that list "competitive salary" with no geographic differentiation are often not planning to adjust for location in a meaningful way, or the role has in-person requirements that override the remote designation.
Mention of "on-site" or "in-person" for any purpose. "Must be available for occasional on-site work" is language that ranges from meaningless to a quarterly offsite expectation to a de facto hybrid requirement. Ask specifically before accepting any offer.
The company's general remote posture. Companies that are genuinely remote-first have consistent remote culture infrastructure: async communication norms, documented processes, distributed team structures. If the company's about page, team page, and job listings all show a single city headquarters and in-office team photos, the "remote" listing is likely not fully remote.
Companies with genuine fully-remote engineering cultures
Based on job listing patterns in our index and publicly documented remote policies:
Stripe has maintained a strong remote engineering culture since expanding their distributed team model. Their job listings are explicit about geographic requirements and compensation tiers. The company has invested in async communication infrastructure at a level that reflects genuine remote-first values.
GitLab is the most cited example of a fully distributed company and their engineering roles are genuinely location-agnostic. Their public handbook documents their remote operating model in depth. Every claim in their remote listings is backed by observable organizational practice.
Automattic (WordPress.com) has operated as a fully distributed company for over a decade. Their engineering roles are remote without geographic restriction. Their internal culture around async communication and documentation is more developed than nearly any other company of their size.
Vercel has a strong remote engineering culture and hires globally for most engineering roles. Compensation is competitive and the remote posture is genuine rather than nominal.
Cloudflare is hybrid for some roles and remote for others — the distinction is real and clearly marked in their listings. Their fully remote roles are genuinely remote.
HashiCorp (now part of IBM) built their engineering organization as distributed-first. The organizational integration with IBM creates some uncertainty about future remote posture, but currently their engineering listings maintain their historically strong remote culture.
Companies that frequently list remote but require meaningful in-person presence
This requires naming carefully — remote policies at specific companies change frequently and vary by team. Rather than listing names, the patterns to look for:
Large tech companies that returned to office mandates in 2023 and 2024 but continue to list individual roles as remote often have inconsistent remote policies at the team level. A role at Google listed as remote may be genuinely remote on one team and expected to be in-person on another. The listing is accurate at the job-description level but does not reflect how the team actually operates.
Consulting firms and services companies that list engineering roles as remote often have client-site requirements that are disclosed only late in the process. The role is genuinely remote from the company's office, but requires frequent travel to client locations.
Series B and C startups that list roles as remote while headquarters is rapidly expanding often have an implicit expectation that remote employees will relocate or spend significant time in-person as the company scales. This is rarely explicit in the listing.
What to ask before accepting a remote offer
The right time to clarify remote expectations is before the offer stage, not after.
"Can you walk me through how the team operates day-to-day — what does a typical week look like for someone in this role?"
"Are there any recurring in-person requirements for this role — whether that's team offsites, company all-hands, or client visits?"
"How does the company handle performance reviews and career advancement for distributed team members compared to those in-office?"
These questions are not confrontational. They are necessary. And any company with a genuine remote culture will answer them clearly.
Search 152K+ remote engineering roles indexed directly from ATS platforms →
Remote job data sourced from JobsGlitch's direct ATS index of 1.09M+ active listings.