$ psql -h dallas.tx -U recruiter -d ahmad_db
connected. ssl: on · role: read_write · timezone: America/Chicago
ahmad_db=# SELECT * FROM candidates WHERE builds = true AND sells = true;
Headshot of Ahmad Abdel-Rahman

Ahmad
Abdel-Rahman

SOLUTIONS ENGINEER · DALLAS, TX

I've built enterprise data platforms from the inside and sold them from the outside. I speak both languages fluently.

125% QUOTA · FY2018-22 GCP + DATABRICKS CERTIFIED (1 ROW RETURNED)
SCROLL
ahmad_db=# SELECT * FROM
who_i_am;

Start with the person.

Before the resume, here's who you'd actually be working with.

  • I'm a proud husband, which is my favorite full-time job.
  • I'm a music nerd. I spend my weekends connecting with local artists and digging into music I'm passionate about.
  • I'm a builder. Tech runs through my everyday life: Python scrapers that surface new artists for me, AI agents that handle my research and busywork, little scripts for every recurring annoyance. If I do something twice, I automate it.
(3 rows) · Time: 0.8 ms
Ahmad interviewing two artists in a vintage record and clothing shop
talking_music_with_local_artists.jpg
Ahmad and his wife in DUMBO, Brooklyn, with the Manhattan Bridge behind them
my_favorite_full_time_job.jpg
builder_mode.mp4
ahmad_db=# SELECT * FROM working_style;

I translate, then I build.

  • Five years at the USPTO taught me to explain deeply technical subject matter to lawyers, inventors, and executives, clearly and under pressure.
  • I genuinely enjoy discovery. The best demos I've given started with listening instead of a slide deck.
  • I don't hand-wave the technical part. I've run the pipelines, owned the migrations, and carried the pager, so my architecture recommendations come from production experience rather than datasheets.
  • Comfortable in front of C-suite and comfortable in the terminal, usually in the same meeting.
(4 rows)
Front page of US Patent 10,449,634 B2, examined by Ahmad Abdel-Rahman as Assistant Examiner
us_patent_10449634_b2.pdf · see: assistant_examiner · 1 of 40 granted
ahmad_db=# SELECT metric, value, source FROM
the_record;

Numbers that held up.

Quota, revenue, and platform outcomes I can walk you through line by line.

the_record · results LIVE
#metricvaluesource
1Production quota, FY2018-220%uspto
2Pipeline throughput gain across production systems0%cvs_health
3Runtime reduction on enterprise cloud migration, zero data loss0%cvs_health
4Annual revenue growth contributed0%findur_presales
5Enterprise client stakeholders managed as technical liaison0+findur
6Business units coordinated on a single enterprise migration0cvs_health
7Years translating deep tech for lawyers, inventors & execs0uspto
8Certifications: GCP Professional DE · Databricks Associate0verified
(8 rows) · Time: 14.2 ms
2018
USPTO
2023
FINDUR
2024
CVS HEALTH
NEXT
YOUR TEAM
ahmad_db=# SELECT * FROM
the_work;

From examining patents to running the platforms enterprises bet on.

I took an unusual path: I learned to communicate under pressure first, sell second, and build third. Most SEs go the other way, and it shows in my demos.

WHERE company = 'cvs_health' LIVE
CVS Health
Data Engineer · Sep 2024 to Present
  • Primary technical lead on an enterprise Teradata → GCP migration, coordinating requirements, risk, and sequencing across 8 business units to deliver a 20% runtime reduction with zero data loss.
  • Partnered with senior leadership to ship production data products powering predictive modeling, Vertex AI analytics, and C-suite dashboards.
  • Automated ETL/ELT with Apache Airflow and Informatica, lifting pipeline throughput 30% across production systems.
  • Established data quality and governance controls for regulated, auditable delivery to every downstream consumer.
(4 rows)
WHERE company = 'findur'
Findur
Sales Engineer · Jul 2023 to Aug 2024
  • Owned the technical pre-sales cycle end-to-end: structured discovery, tailored architectures, and live demos to C-suite and technical audiences, contributing to 15% annual revenue growth.
  • Led proof-of-concept engagements that differentiated the product and moved enterprise opportunities through the funnel to close.
  • Built Python pipelines for user-behavior analytics that drove a 10% engagement lift and informed roadmap priorities.
  • Primary technical liaison between engineering and 10+ enterprise stakeholders across multi-month cycles.
(4 rows)
WHERE company = 'uspto'
United States Patent & Trademark Office
Patent Analyst · Jun 2018 to Jul 2023
  • Primary point of contact for patent attorneys, agents, and inventors, presenting findings and guiding stakeholders toward patentable subject matter at 125% of production quota (FY2018-22).
  • Authored formal Office Actions translating nuanced technical and legal analysis into clear, actionable guidance for Fortune 500 IP teams.
  • Five years of consultative, high-stakes communication. It's the same muscle technical pre-sales runs on.
(3 rows)
ahmad_db=# SELECT category, tools FROM
toolbelt;

Tools I've actually shipped with.

Every tool below has shipped something real: an enterprise migration, a live demo, or a weekend build.

toolbelt · results
categorytools
cloud_and_data
GCPBigQueryDataprocDatabricksVertex AIAzure Data FactoryMicrosoft FabricTeradata
pipelines
Apache AirflowInformaticaETL / ELT
ai_and_analytics
AI/ML PlatformsPredictive ModelingLLM ToolingExecutive Dashboards
languages
PythonSQL
presales_craft
Technical DiscoverySolution ArchitectureProof of ConceptLive DemosExecutive Presentations
certifications
GCP Professional Data EngineerDatabricks Associate Data Engineer
(6 rows) · Time: 2.1 ms
ahmad_db=# EXPLAIN ANALYZE SELECT trust FROM
deal;

I run deals like I run pipelines.

Messy inputs, clean outputs, nothing silently dropped. Discovery extracts what actually matters, architecture turns it into one clear answer, and a live proof on their own data is what loads the trust. Then it runs on a schedule: renewals.

ambiguous asks extract() transform() load() ✓ trust
query plan LIVE
                 QUERY PLAN
---------------------------------------------
 Deliver  (renewals follow)
   -> Prove  (live demo, their own data)
      -> Simplify  (one clear answer)
         -> Discover  (what matters)
            Scan on requirements
            (rows=50, loose_ends=0)

 Planning:  one good discovery call
 Execution: faster than you'd think
(1 row: trust)
ahmad_db=# INSERT INTO
your_team
(name, role) VALUES ('Ahmad', 'Solutions Engineer');

Let's Connect.

INSERT 0 1
ahmad_db=# COMMIT;
ahmad.arahman95@gmail.com