Technical Skills I can offer
A shortlist of offerings that could be beneficial to your team or company.
An Interpreted server-side language. Used widely around the web to quickly deploy websites and web services. One of my go to tools for working with data interchange between the back-end and front-end user interfaces.
If your website is running slow, you could be driving your potential customers away with frustration. Having sturdy design in your infrastructure will ensure speedy page loading times, around the clock.
DNS is used to make sure your websites are being seen around the globe. DNS caching, AnyCast DNS and distributed DNS are integral parts of the web and something that I have had fine-grained experience with. DNS Lookup times are important.
I have had years of experience jumping onto Ubuntu, CentOS, RedHat systems and understanding the details which make each system different. This includes using SELinux/IP Tables/Samba/FTP/ssh keychains/SSL/Nagios and more.
Relational databases are multi-faceted animals. I've utilized PostGreSQL, MySQL, MSSQL, SQLite each for their respective technical benefits. I have designed SQL benchmarking tests and replication clusters to obtain optimal read/write efficiency.
I have used MongoDB in a few live projects to find out the benefits. For flat objects and datasets, NoSQL Databases such as this are awesome. I don't think it scales for Relational data though. It does for flat files, and is exactly what i used it for.
There was a time when I cursed the fall of the Flash player. There seemed to be a gap in the interactive web space, especially for mobile devices. Now that gap has been filled in spectacular fashion with HTML5 and the Canvas/Audio APIs. Using JS to port things over from AS3 (both being ECMAScript variants) has made it even more viable!
I rarely use xml for my own projects these days. I am much more of a JSON advocate, but that's not to say that XML isn't important. It has been implemented in a lot of places for data-interchange in 3rd-party systems, so learning it was integral to what I do. When starting new projects that don't have XML interchange contracts, I'll champion JSON!