Address
Form of work Title: Technical Lead/Application Developer
Location: Jamaica Plain, MA
Duration: Multi Year Renewable Contract
Hours: 37.5 Hours per week
Overview:
Provides analytical support for conceptualization, development, and implementation of complex systems of multiple inter-linked programs. In-depth knowledge of all phases of client/server applications technology. Responsible for the analysis, design, coding, debugging, testing and documentation of computer programs. Broad experience in programming graphical user interfaces (GUI). Extensive knowledge and skill with object-oriented programming, relational database structures and Structured Query Language (SQL). May act as team or project leader on major applications projects.
Context:
The Technical Lead serves a critical and vital role on the Lab Information Management Systems technical team (LIMS Team). The lead aspect is important in defining the role. The Technical Lead holds the key to the technical growth of the team by growing themselves technically and leading-by-example and modelling best practices. The Technical Lead advises management on setting the technical direction of the team and the project, establishes the technical vision with the development team and works with them to turn it into reality.
Technical Role:
The Technical Lead must act as an SME on all new and existing DPH LIMS systems and other related application-specific processes: Technical application support for the DPH disease surveillance system using VB.Net WinForms, C#, .Net Framework 3.0 or greater, .Net Core, C1 component or any 3 rd party .net components, TFS, Azure, Java, SQL script, Oracle, Selenium and Eclipse in Windows and UNIX environments. Assists in the development and implementation using WebLogic application server, XML, SFTP and SOAP. Assists in database design and database reporting process, using Oracle, SQL Server, BI, Jasper and SQL reporting services. Support ancillary applications and data feeds including Electronic Laboratory Reporting system (ELR), Rhapsody and others and create and maintain related technical documentation.
Ownership:
The Technical Lead must lead technical projects, work-streams, and activities. They must take ownership of technical issues: shepherding them through to resolution and marshaling technical resources including staff, tools and documentation to meet project and operational objectives.
Modeling:
The Technical Lead must provide an example to technical team members on how to: troubleshoot issues, deal with customers professionally and with integrity, be accountable to the customer, stakeholders, team members and the project manager. They must encourage good intra-team relations, sharing of work tasks and knowledge. They must be willing to handle tasks themselves, share tasks jointly with other team members, and delegate and assign tasks fairly and equitably among team members.
Coaching:
The Technical Lead must be consistently sharing technical knowledge, coaching, mentoring, and directing technical team members to resources and opportunities for professional growth including shadowing the Technical Lead. Ideally, for every practicing Technical Lead there should be at least one team member identified informally by management as the Technical Lead "in training " who can serve as a back-up.
Communications:
The Technical Lead must be adept in all forms of communications: Writing concise technical explanations, requirements and technical specifications, and emails/texts as well as clear verbal communications in meetings, teleconferences, and training. They must be capable of translating complex technical issues into logical, concise, and understandable communique for varied audiences. They must exemplify an understanding of the lines of authority withinthe technical team, ensuring proper escalation of issues and risks and informing management, and technical team members on a need-to-know basis.
Expertise:
Act as an SME on all new LIMS and other related application-specific processes: Do a deep-dive on technical areas and then teach other team members.
Technical Issues:
They must keep on top of all open and emerging technical issues: documenting, tracking and keeping the Project Manager informed. Enhance existing functionalities in DPH LIMS Systems using the Admin Console as well as .NET, .Net Core, VB.Net, C#, SQL, SSRS, Oracle, and JAVA. Document and standardize incoming and outgoing data feeds. Should provide a weekly technical status update.
Application Upgrades and Releases:
Keeps close monitoring of all minor and major software updates and releases: Planning, managing technical risk, advising management, and leading the technical effort.
Code Review:
Institute and participate in recurring code review sessions.
On-Call:
The Technical Lead on the LIMS Team must be available as the first line of response to any technical issue or emergency that occurs during the formal workday or after hours.
Escalation:
Exemplify an understanding of lines of authority within the technical team ensuring proper escalation of issues and risks and informing management, and technical teams' members on a need-to-know basis.
EDUCATION AND EXPERIENCE:
EXEPERIENCE DESIRABLE:
Location: Jamaica Plain, MA
Duration: Multi Year Renewable Contract
Hours: 37.5 Hours per week
Overview:
Provides analytical support for conceptualization, development, and implementation of complex systems of multiple inter-linked programs. In-depth knowledge of all phases of client/server applications technology. Responsible for the analysis, design, coding, debugging, testing and documentation of computer programs. Broad experience in programming graphical user interfaces (GUI). Extensive knowledge and skill with object-oriented programming, relational database structures and Structured Query Language (SQL). May act as team or project leader on major applications projects.
Context:
The Technical Lead serves a critical and vital role on the Lab Information Management Systems technical team (LIMS Team). The lead aspect is important in defining the role. The Technical Lead holds the key to the technical growth of the team by growing themselves technically and leading-by-example and modelling best practices. The Technical Lead advises management on setting the technical direction of the team and the project, establishes the technical vision with the development team and works with them to turn it into reality.
Technical Role:
The Technical Lead must act as an SME on all new and existing DPH LIMS systems and other related application-specific processes: Technical application support for the DPH disease surveillance system using VB.Net WinForms, C#, .Net Framework 3.0 or greater, .Net Core, C1 component or any 3 rd party .net components, TFS, Azure, Java, SQL script, Oracle, Selenium and Eclipse in Windows and UNIX environments. Assists in the development and implementation using WebLogic application server, XML, SFTP and SOAP. Assists in database design and database reporting process, using Oracle, SQL Server, BI, Jasper and SQL reporting services. Support ancillary applications and data feeds including Electronic Laboratory Reporting system (ELR), Rhapsody and others and create and maintain related technical documentation.
Ownership:
The Technical Lead must lead technical projects, work-streams, and activities. They must take ownership of technical issues: shepherding them through to resolution and marshaling technical resources including staff, tools and documentation to meet project and operational objectives.
Modeling:
The Technical Lead must provide an example to technical team members on how to: troubleshoot issues, deal with customers professionally and with integrity, be accountable to the customer, stakeholders, team members and the project manager. They must encourage good intra-team relations, sharing of work tasks and knowledge. They must be willing to handle tasks themselves, share tasks jointly with other team members, and delegate and assign tasks fairly and equitably among team members.
Coaching:
The Technical Lead must be consistently sharing technical knowledge, coaching, mentoring, and directing technical team members to resources and opportunities for professional growth including shadowing the Technical Lead. Ideally, for every practicing Technical Lead there should be at least one team member identified informally by management as the Technical Lead "in training " who can serve as a back-up.
Communications:
The Technical Lead must be adept in all forms of communications: Writing concise technical explanations, requirements and technical specifications, and emails/texts as well as clear verbal communications in meetings, teleconferences, and training. They must be capable of translating complex technical issues into logical, concise, and understandable communique for varied audiences. They must exemplify an understanding of the lines of authority withinthe technical team, ensuring proper escalation of issues and risks and informing management, and technical team members on a need-to-know basis.
Expertise:
Act as an SME on all new LIMS and other related application-specific processes: Do a deep-dive on technical areas and then teach other team members.
Technical Issues:
They must keep on top of all open and emerging technical issues: documenting, tracking and keeping the Project Manager informed. Enhance existing functionalities in DPH LIMS Systems using the Admin Console as well as .NET, .Net Core, VB.Net, C#, SQL, SSRS, Oracle, and JAVA. Document and standardize incoming and outgoing data feeds. Should provide a weekly technical status update.
Application Upgrades and Releases:
Keeps close monitoring of all minor and major software updates and releases: Planning, managing technical risk, advising management, and leading the technical effort.
Code Review:
Institute and participate in recurring code review sessions.
On-Call:
The Technical Lead on the LIMS Team must be available as the first line of response to any technical issue or emergency that occurs during the formal workday or after hours.
Escalation:
Exemplify an understanding of lines of authority within the technical team ensuring proper escalation of issues and risks and informing management, and technical teams' members on a need-to-know basis.
EDUCATION AND EXPERIENCE:
- Bachelor's degree in computer science, Computer Information Systems, Information Management or related field or equivalent work experience.
- Ability to drive complex system integration projects and transition businesses to new application platforms.
- Minimum 5 years of experience in an Application Lead role. Experience in:
- SDLC
- Solution assessment and validation.
- Technical Requirements / Specifications Development and Management.
- 8+ years of professional experience doing Microsoft SQL Server (2008, 2012 or greater) database management & database administration.
- Expertise with relational database design, capacity planning, security, and other distributed data issues.
- 5+ years of experience with T-SQL and PowerShell Scripts, ETL is required.
- Strong working knowledge of query, index and DB I/O performance tuning, and Stored Procedures and SQL coding is required.
- Ability to manage all DB maintenance plan activities including backups, indexing, integrity and consistency checks, etc.
- Troubleshooting and resolving database blocking and deadlocking issues, replication issues, log shipping issues, connectivity issues, security issues, Data issues etc.
- Possessing a strong understanding of database administrator methodologies.
- Understanding of project management and the software development lifecycle.
- Experience working in a PMO environment.
- Experience working with software vendors.
- Possessing a strong understanding of testing methodologies for functional, systems, integration, performance, and user acceptance.
EXEPERIENCE DESIRABLE:
- Experience working in the Healthcare Industry.
- Experience working for State Agencies.
- Experience working in a Lab environment.
