Writing an effective MS Access developer resume

[scottfarcus]

After almost 10 years developing MS Access applications for the government, I'm attempting to write an effective resume to begin my job search. I've single-handedly designed, tested and implemented over 40 small to medium sized applications to handle everything from classified document management to personnel tracking to event planning. Most of these systems were fairly complex with pages of VBA code, automation and FE/BE structure to allow concurrent users.

I'm having a terrible time verbalizing the work I've done with Access while making it sound impressive to companies using larger, more robust systems like SQL Server or Oracle.

With the stigma that comes with Access, I would love to know how Access resumes could be written to accurately portray the ability to design logical schema, design intelligent interface and define system requirements while conveying that the skill to perform these tasks translates to other systems as well.

Can anyone here (PatHartman, ghudson, et al) provide:

A) a sample resume for an Access developer?
B) sample language to include in an Expert Access Developer resume?

I thank all of you, in advance, for your time and any assistance you can provide.

Happy coding!

 

[CharlesWh]

did you get a template? I'd like one too.

 

[Lightwave]

Haven't got an example afraid but what I would probably do..

Have the main resume which is fairly standard.

And then produced an additional case study of a database that I was particularly proud of. Would indicate with screen shots pictures and an indication of structure how it is used and what the benefits of its use have been. You might be able to alter the case study according to your target. Eg if it was going to someone like Pat Harman might want to concentrate on detail whereas non database knoledgable people might just want pretty pictures.

 

[dkinley]

Think about it like this ... different human languages all say the same thing except with minor nuances, so I'd probably take a standard DBA/Coder template because everything you do in Access is being done in other languages.

So is someone who holds themselves out as an .ASP programmer better than a MS Access/VBA programmer?

The simple answer is depends and the dependancy would hinge on size and scope of the projects.

Taking this approach I would list the highlights of the projects that I completed and demonstrate the benefit ($$$/time/resources saved). That way my resume would appeal more to the business minded reviewer and then in the interview sell my skills based on the '.ASP has to use the same logic, etc., except with a slight twist on the syntax' and in 3 months I will be a better asset than the .ASP programmer that has only completed very small projects.

Last but not least, do something small in the language they are calling for and list it so the resume will pass the HR flunkie who doesn't know much and get the resume into the hiring managers hands and you get the call.

Carry screenshots or a thumbdrive with working apps on them for the demonstration portion of the skills and make remarks like 'Oh, translate to .ASP? No problem!'

-dK

 

[ions]

You can make a website outlining your work and screen shots. I find this very effective. Also since you are an expert I would consider contracting.