SShortSingh.
Back to feed

Developer Rejected 2 Minutes After Applying, Blaming Automated Degree Filter

0
·22 views

A developer applying for a junior solutions engineer role received an automated rejection roughly two minutes after submitting their application. Despite lacking a STEM degree — listed as a requirement — the applicant had hands-on experience building a custom inventory management system integrated with WooCommerce for a real business client. The project involved API integrations, database work, multi-device synchronization, and deployment, going well beyond portfolio or tutorial work. The near-instant turnaround strongly suggests an automated applicant tracking system filtered out the candidate before any human reviewed their tailored resume, cover letter, or written responses. The incident reignites debate over whether 'skills-based hiring' rhetoric in tech is undermined when degree requirements remain as hard automated filters at the top of the pipeline.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Hackers target France's national blood bank

Cybercriminals have attacked France's national blood bank, according to a report from the Telegraph. The article itself is only a link, so details such as the date, the extent of the breach, and whether any data was stolen or services disrupted cannot be confirmed from the available material. Discussion of the story on Hacker News has drawn modest attention, with 11 points and 4 comments at the time it was captured. Further reporting would be needed to establish the scope and impact of the intrusion.

0
ProgrammingDEV Community ·

Keeping postal codes as strings in Python fixture round trips

Postal codes can look numeric, but converting them to numbers drops leading zeros that cannot be restored by converting back to text. Codes with letters and spaces, such as Canadian-style formats, also need to be preserved exactly. A tutorial demonstrates an offline Python 3.10+ check using only the standard library to verify a JSON address export against a CSV file with a ZIP column. The check confirms that postal values remain strings, source references are retained, and each CSV row matches its JSON record field by field. The fixtures are invented for testing purposes and are not real postal reference data.

0
ProgrammingDEV Community ·

Developer fixes PWA sign-in bug in calorie tracker, asks readers to test the app

A developer building the ForkCount calorie tracker explains how they fixed a bug that broke the app when installed as a progressive web app, which involved changing login redirects and disabling URL session detection in Supabase. Despite 258 followers on dev.to, the developer reports zero app signups and asks readers why they haven't tried the free, card-free app. The post invites readers to sign up, describes the app's calorie target and BMR features, and asks users to report bugs with their device details. The developer notes that recent additions include photo logging, a barcode scanner, and streaks, while email verification and offline mode are still in progress. The post notes that the developer is 13 years old and built the app with Google AI Studio.

0
ProgrammingDEV Community ·

AppConfig feature flags let Lambda teams roll out changes gradually with automatic rollback

AWS AppConfig feature flags allow switches in Lambda functions to change behavior without redeployment, applying updates in stages rather than to every function at once. The article contrasts this with Parameter Store, where a value change reaches all functions as soon as their cache expires, leaving no safety net for risky features. AppConfig adds schema validation, staged rollout strategies, and rollback triggered by CloudWatch alarms. The author argues Parameter Store suits harmless, rarely changing settings, while AppConfig suits switches that alter behavior. The walkthrough builds a cinema pricing API with CDK and TypeScript, including a gradual rollout and a kill switch.