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

Location

Location: classified. Send a pigeon.

Skills

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.

Case studies

Two pieces of client work described on his portfolio: a logistics alerting automation and a pricing integration. Both are self-reported client work with no public code.

Case StudybeginnerClient work, Apr 2025 – Jan 2026

Cargo Stagnation Alerts

Scheduled FlowsSales CloudLightning Web Components

A Scheduled Flow automation for a logistics client (OTS Astracon, per his work history). It watches for cargo records whose status updates have stalled and sends dispatchers an automatic alert. He also built LWC components and page layouts to streamline dispatcher work in Sales Cloud.

It turns a real operations pain point (stalled shipments nobody notices) into a scheduled check. That problem-first framing is what an admin-to-developer hire needs to show.

  • Scheduled Flow monitoring stalled logistics updates

  • Automatic dispatcher notifications

  • Paired with custom LWC components for the dispatch team

Case StudyintermediateClient work, Jan 2023 – Feb 2025

REST API Quote Sync

Apex calloutsREST APIOpportunities & QuotesFlow

An integration between Salesforce Opportunity and Quote records and a third-party pricing service, built with custom Apex REST callouts. His work history places it at Virtusa, alongside multi-step Flows for the Opportunity and Quote workflow.

Apex callouts to an external pricing system go beyond configuration work and are the kind of integration task a Platform Developer I role expects.

  • Custom Apex REST callouts to a third-party pricing service

  • Synced Opportunity and Quote data

  • Delivered alongside Flow-based quote workflow configuration

Ready to build your portfolio?

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

Salesforce Developer Roadmap