DEV Community: Anshu Sharma

Building a developer first temporary email service

Anshu Sharma — Thu, 23 Apr 2026 18:25:51 +0000

I built a disposable email API for developers

While working on multiple side projects, I kept hitting the same bottleneck:

Testing email flows is painful.

You don’t want to use your personal inbox
Test emails clutter everything
Most temp mail services are not API-friendly

So I built: 👉 Devmail

What it does

Generate disposable email addresses instantly
Receive emails in real-time
Access inbox programmatically via API

Why this matters

If you're building:

authentication systems
SaaS products
automation scripts

You need a reliable way to test:

OTP flows
verification emails
transactional messaging

Key features

No signup required
Lightweight API
Fast inbox refresh
Developer-first design

Example use case

You can integrate it into automated tests:

create temp email
trigger signup
fetch verification email
extract token
complete flow

Looking for feedback

I’m actively improving this and would love input:

missing endpoints?
performance issues?
feature requests?

Drop your thoughts 👇

I Bought anshu.uk — Turning My Name into a Searchable Asset

Anshu Sharma — Wed, 15 Apr 2026 14:02:33 +0000

Most developers treat portfolios as a side project.

I decided to treat mine like infrastructure.

👉 Live: https://www.anshu.uk/

🧠 The Problem: You Don’t Exist on Google

Search “Anshu” and you’ll see:

Academics
Brands
Random social profiles
Completely unrelated people

There are hundreds of people with the same name across industries.

If you don’t actively build your presence, Google assigns your identity for you.

⚙️ The Strategy: Treat Your Name Like a Product

Instead of building just another portfolio, I approached this as:

“How do I rank my name like a startup ranks its product?”

So I bought:

Anshu Sharma | Software Engineer | Golang • MERN • Microservices • Kafka • Temporal

Engineering scalable backend ecosystems using Golang, MERN, Kafka, Temporal, and cloud-native tooling.

anshu.uk

Short. Clean. Memorable. Brandable.

🏗️ What I Built

The site is not just a portfolio — it’s a central identity hub.

According to the live site, it positions me as a:

Software engineer focused on scalable, production-grade systems (Golang, MERN, microservices) ([Anshu Sharma Portfolio][1])

Core components:

👨‍💻 About → clear positioning
🧠 Tech stack → Golang, Kafka, Temporal, distributed systems
🚀 Projects → proof of execution
🔗 External links → authority signals

Everything points back to one thing:

“This is the Anshu you’re looking for.”

🔗 My Digital Identity Stack

To reinforce search signals, everything is interconnected:

GitHub → https://github.com/anshu4sharma
LinkedIn → https://www.linkedin.com/in/anshu24/
Resume → https://www.anshu.uk/anshuresume.pdf
Website → https://www.anshu.uk/

This creates a closed-loop identity graph, which helps Google understand:

All these profiles belong to the same person

🔗 Why a Personal Domain Matters

1. You control your SEO surface

Platforms like LinkedIn or GitHub:

You don’t own them
You don’t control ranking

Your domain = your authority layer

2. Google understands entities, not just pages

When everything links together:

anshu.uk → GitHub → LinkedIn → Articles → Backlinks

Google starts treating you as a single entity

3. It compounds over time

Unlike social media:

Blog posts rank for years
Backlinks increase authority
Your name becomes searchable

📈 The Real Goal (Not Just a Portfolio)

I’m not trying to “have a website”.

I’m trying to:

Rank for “anshu developer”
Then “anshu golang”
Eventually just “anshu”

This is a long-term SEO play (6–12 months minimum).

🧱 What Most Developers Get Wrong

They:

Build a portfolio once
Never update it
Don’t distribute content
Don’t build backlinks

Result:

Dead site. Zero traffic. No discoverability.

🚀 My Execution Plan

Phase 1 — Foundation

Domain + portfolio
Clear positioning

Phase 2 — Content Engine

Write about:
- Microservices
- Kafka / Temporal
- Backend scaling

Phase 3 — Distribution

Dev.to
Medium
GitHub
Communities

Phase 4 — Backlinks

Guest posts
Open source
Mentions

🧠 Key Insight

You don’t become searchable by accident.

You become searchable by:

Repetition
Authority
Distribution

⚠️ Reality Check

This is not a hack.

No shortcuts
No instant ranking
No AI spam

This is:

Consistent output + strategic positioning

📌 Final Thought

If your name is common, you have two options:

Compete randomly
Systematically dominate your niche

I chose the second.

If you’re a developer and don’t own your name yet:

You’re building on rented land.

Why ATS rejects 70% of resumes

Anshu Sharma — Tue, 27 Jan 2026 07:01:55 +0000

Most resumes don't fail because candidates lack skills. They fail because Applicant Tracking Systems never properly read them.
Modern hiring pipelines are optimized for scale, not nuance. Before a human ever evaluates your experience, an ATS scans, parses, scores, and frequently discards your resume based on structure, keyword alignment, and machine readability. The result is a silent rejection loop impacting an estimated 70% of applicants.
This exact failure pattern is what resume.anshu.uk is designed to surface.
Where Things Break Down

Parsing Failure Non-standard layouts, multi-column designs, icons, tables, and graphics routinely confuse ATS parsers. If the system cannot correctly extract your name, role history, or skills, the resume becomes functionally unusable. resume.anshu.uk explicitly tests for these parsing breakdowns.
Keyword Misalignment ATS platforms rank resumes against job descriptions using keyword relevance. Strong experience phrased differently than the posting can score poorly, even when the candidate is objectively qualified. The ATS Resume Analyzer on resume.anshu.uk highlights missing and weak keyword matches before submission.
Formatting Compliance Issues PDFs exported from design tools, inconsistent headings, unconventional section titles, and embedded fonts regularly cause parsing errors. Visually impressive resumes are often technically fragile. resume.anshu.uk evaluates formatting risks that commonly trigger automated rejection.
Signal Dilution Overloaded skill sections, vague summaries, and generic phrasing reduce keyword density and weaken relevance scoring. ATS systems reward clarity and structure, not creativity. This signal-to-noise imbalance is directly measured by resume.anshu.uk. The Real Problem Candidates optimize for humans. Hiring systems optimize for machines. The gap between those two priorities is where most resumes are lost. Tools like resume.anshu.uk exist specifically to close that gap. The Solution: Validate Before You Apply ATS Resume Analyzer Get instant feedback on your resume's ATS compatibility. Available at resume.anshu.uk, the analyzer evaluates:

Parsing accuracy
Keyword alignment
Structural compliance
ATS readability risks

It delivers actionable insights designed to reduce automated rejections and improve shortlisting probability, without guesswork.
👉 Try it here: https://resume.anshu.uk
Who Built It
resume.anshu.uk is developed and maintained by anshu.uk, a software engineer focused on building practical, automation-aware tools that align candidates with modern hiring systems rather than outdated resume advice.
In a hiring market driven by automation, ATS optimization is no longer optional. Treat compatibility as a baseline requirement, not an afterthought.