Floorplanning, place-and-route, timing, and power-aware implementation.
Digital Physical Design Engineer
Open for focused projects
Anas Hawamda
Physical design support for teams that need clean closure.
Floorplanning, P&R, timing closure, and verification-informed engineering review.
Methodical execution, documented tradeoffs, and clear handoffs.
Case studies, technical writing, and scoped support for reliable delivery.
Practice
Practical engineering help with the reasoning left visible.
I work best on ambiguous technical problems where clean decisions, reviewable artifacts, and calm execution matter.
Base
Ramallah
Mode
Remote-friendly
Blend
DV + PD
Strength
Quality-first
Latest focus
Shipping robust physical designs
Floorplanning, timing closure, and power-aware implementation with a DV-honed eye for quality.
PPA
Balancing perf, power, area
Timing
STA & closure discipline
DV roots
Methodical, test-first mindset
"Quality means doing it right when no one is looking."
What you will find here
Project case studies, engineering notes, and a small collaboration practice built around clarity.
What I value
Thoughtful execution, calm problem-solving, and documentation that removes ambiguity.
Best fit
Teams that care about signal quality, delivery discipline, and review-ready work.
About
Engineer first. Systems thinker always.
I work at the intersection of implementation detail, verification discipline, and communication that reduces confusion for the next person in the loop.
Current lens
Calm execution, clean handoffs, and documentation that other engineers can actually use.
I'm a Computer Engineer focusing on digital physical design: floorplanning, P&R, timing, and power optimization. I bring a former design verification background, pairing implementation with a test-first mindset.
Digital physical design engineer with practical verification roots.
Turning messy technical constraints into cleaner implementation choices.
Floorplanning, timing analysis, optimization tradeoffs, and engineering communication.
Technical notes and blog posts that make complex work easier to follow.
Selected Work
Projects with process behind them.
A rotating set of engineering, tooling, and product experiments presented as clearer case studies instead of a generic thumbnail wall.
Notes & Writing
Technical writing with an editorial rhythm.
Thoughts on engineering practice, verification craft, and the kind of documentation that helps teams move faster with less confusion.
Recommendations
What trusted collaborators say.
Notes from teammates, leads, and clients who have seen the work up close and can speak to how it feels to collaborate.
Collaboration
Services with a clearer offer.
Small, focused engagements tailored to reviews, build support, and technical problem-solving where the main value is clarity plus execution.
How I like to work
Focused engagements with clear scope and honest tradeoffs.
Whether it is a targeted review or a hands-on project, I optimize for fast clarity, documented decisions, and momentum that keeps compounding.
- Clear goals before execution starts
- Direct communication around constraints and tradeoffs
- Deliverables that leave a team more self-sufficient
Best for strategy
$50/hour
Consultation
Targeted reviews, technical guidance, and focused problem-solving sessions.
Best for delivery
Starting at $500
Freelance Project
Scoped implementation work with steady updates, documented decisions, and practical outcomes.
Client Notes
What collaboration feels like
Connect
Bring a clear problem. I will meet it directly.
Share the goal, the constraints, and where the bottleneck lives. The more context you include, the better the first reply can be.
Get in touch
Let's build silicon that closes
Share your physical design challenges: floorplanning, timing closure, or power/area tradeoffs. I also bring prior DV experience for end-to-end quality.
Email
anashawamda@gmail.com
Location
Ramallah, Palestine - Remote-friendly
Response
Replies within 1-2 business days
Best for
Reviews & scoped builds
Timezone
Remote collaboration
Project Brief
Tell me what you're building.
A useful first message usually includes the problem, current constraints, timeline, and what "better" looks like for your team.