Salesforce Developer

Manoj Kumar Selvakannan Portfolio

Admin-to-developer portfolio (4+ years across Maxval Group, OTS Astracon, Virtusa, and Seven Hills) documenting named projects like a Cargo Stagnation Alerts scheduled-flow system and a REST API quote-sync integration, with ADM 201 earned and Platform Developer I in progress.

Apex TriggersFlow AutomationExperience CloudREST Integration

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

Projects named by the business problem, not the feature

"Cargo Stagnation Alerts" and "REST API Quote Sync" give a hiring manager something concrete to ask about, unlike a generic "built a Flow" description.

2

Honest sequencing of certifications

Listing Platform Developer I as "in-progress" next to an earned Administrator credential is an honest trajectory signal rather than overclaiming.

3

A quantified automation count

Stating "30+ Flow automations deployed" gives scope to admin/dev hybrid work that's often described only vaguely.

What Salesforce Developers can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • Name your projects by the business problem they solved, not the feature you built — "cargo stagnation alerts," not "built a scheduled flow."

  • List in-progress certifications honestly alongside completed ones — it shows a trajectory without overstating where you are.

  • If your work spans admin and developer tasks, quantify both sides (automations deployed, integrations built) rather than picking just one.

Ready to build your portfolio?

Follow the Salesforce Developer roadmap — skills, projects, and timeline to get hired.

Salesforce Developer Roadmap