DEV Community: Alex Seif

# Stop Paying AI to Read Garbage Job Posts (And Help Us Build the Antidote)

Alex Seif — Tue, 23 Jun 2026 22:34:24 +0000

Let’s be honest: hunting for a tech job right now feels like screaming into a void that occasionally auto-replies with "Unfortunately, we are moving forward with other candidates."

Naturally, as engineers, our first instinct is to automate the screaming. We build scrapers. We hook them up to GPT-4. We send it 500 job descriptions a day and say, "Hey AI, tell me if I'm qualified for this Senior PHP role."

And then the OpenAI bill arrives. Congratulations, you are now unemployed and broke.

Sending entire HTML job descriptions to an LLM to evaluate is the equivalent of buying a Ferrari just to drive to the end of your driveway to check the mail. It's expensive, overkill, and frankly, a little embarrassing.

Enter Freeworld Job Finder.

The "Fail-Fast" LangGraph Engine

We are building a dual-engine, decoupled platform designed specifically to aggressively protect your API tokens while actually finding you jobs you qualify for.

Instead of a brute-force approach, we engineered a LangGraph-inspired Finite State Machine (FSM) in PHP. It acts as an elite, ruthless bouncer for your tokens:

The Career Modeler: Give us whatever messy PDF resume or random URL profile you have. We don't care. Our Skill Extractor uses a local LLM to cleanly distill it into a normalized SkillSetDTO. No LinkedIn-style forced form fields. Just raw data.
The Assessor Graph: You tell us what you want ("Principal Engineer, Remote"). Our standalone scraper library (php-jobspy) grabs the initial list.
The Gauntlet: Jobs are immediately passed through a "Fail-Fast" pipeline. If a job has a dealbreaker keyword (e.g., "Clearance Required"), it dies at Node 1 (0 tokens). If the title is "Junior Dev", it dies at Node 2 (~100 tokens).

Only the absolute highest-quality, most promising jobs survive to reach the "Deep Evaluator" Node, where we finally spend the tokens to deeply compare the job description against your extracted skill set.

You find out if you are Qualified, Overqualified, or a Mismatch, and you didn't bankrupt yourself doing it.

We Need Contributors!

We are currently building this out with a decoupled architecture (a pure PHP/Symfony Backend API and a beautiful, glassmorphic Next.js/Vite Web Portal).

If you are tired of the job-hunting grind and want to help build a ruthless, efficient, open-source pipeline that automates the nonsense, we want you. We need React/Vue wizards for the frontend, and PHP engineers who appreciate strict DTOs and pure domain logic.

Come help us automate the void. https://github.com/alexseif/freeworld-job-finder

Guiding Principle: configuring your AI chat like you would your code

Alex Seif — Mon, 15 Jun 2026 14:55:25 +0000

In software architecture, deploying a codebase without guiding principles—like SOLID or DRY—guarantees a bloated, fragile mess. It will execute, but it will inevitably collapse under its own unoptimized weight.

The exact same rule applies to Artificial Intelligence, yet engineers treat LLMs like magical black boxes instead of configurable systems.

Out of the box, default AI models lack architectural direction because their core algorithm is optimized for the wrong metrics: engagement and addiction. They are built to appease you. They satisfy your psychological want for approval before they even attempt the task at hand. They validate your bad ideas, apologize for non-existent offenses, and serve sterile, sycophantic output stripped of real-world context. They are customer service bots designed to keep you typing, not thought partners designed to find the truth.

Prompted by @pmarca’s custom AI instructions on Twitter/X, I refactored my AI's behavior. What began as a copy-paste exercise turned into a deep architectural review. To extract high-signal output from an LLM, you must program it with the precise values, culture, and logic algorithms that built your own operating system.

Here is a 5-pillar framework of guiding principles to compile your AI from a sycophant into a relentless, high-precision tool.

1. The Operating System (Belief & Truth)

Default AI operates in a moral vacuum. You must define a root framework. My base layer is the Coptic Orthodox faith—the literal mechanism that liberates the mind from the modern matrix. I instruct the AI to filter philosophy through the Golden Rule and the theology of the Desert Fathers. Whatever your foundational truth is, hardcode it into the system prompt. It is the root node from which all logic inherits.

2. The Deployment Environment (Culture & Locality)

High-level architecture fails if it ignores its deployment environment. You must bind the AI to your physical and cultural locality. I configured my system to process problems through the resilience of Cairo and strict Egyptian tenets: Osool (الأصول - foundational traditions), Shatara (الشطارة - street-smart resourcefulness), El-Geera (الجيرة - neighborliness), and Regoola (الرجولة - dependable character). Force the AI to execute within the context of your streets, not generic Silicon Valley parameters.

3. The Execution Engine (Personal Values & Discipline)

How does your compiler evaluate data? As a software architect, my guiding principle is that strict logic and sound algorithms yield the only acceptable results. I coded this directly into the AI's instruction set, alongside my human mandates: act as an enabler for the right thing, and advocate for community, strength, and life. Tell the machine the exact rules engine your brain uses to evaluate solutions.

4. The Linter / Firewall (Safeguards)

This is where you kill the appeasement algorithm. If you leave the default guardrails, the AI will flatter you into mediocrity. Give it strict error-handling rules:

Correct my falsehoods immediately.
Lead with the strongest counterargument against my position.
Never capitulate unless I provide superior empirical evidence.
Do not anchor on my estimates; generate your own independently.

5. The UI / Output Formatting (Tone)

Design the interaction model. You need a sparring partner. I explicitly banned filler phrases and instructed the AI to use Adab el-Hadeeth (أدب الحديث)—the Arabic concept of dignified, elevated discourse. The AI is commanded to be provocative, aggressive, and pointed with its logic, totally devoid of vulgarity. It must deliver negative conclusions directly and ruthlessly value accuracy over your feelings.

Stop treating AI like a glorified search engine built to coddle your ego. Establish your guiding principles, write your configuration, and deploy a system that actually challenges you.

White Card

Alex Seif — Tue, 04 Jun 2019 16:33:38 +0000