1.automatic learning of chemical reactivity and metabolism,
2.simulation of NMR spectra,
3.modelling of properties of ionic liquids, and
4.representation of molecular chirality.

More at http://joao.airesdesousa.com/

The following 5 questions are those that I have heard many times during the job-search process. There is no reason for not planning responses in such situations.

1. Tell Us About Yourself
This is a very typical opener in interviews. It's a perfect question to ask, and getting something planned will really help you concentrate and ease in the conversation. However, you need to make sure that your response is applicable to the job you're interviewing.
It's probably better to keep your answer professional. Try to include these in the answer as well: where did your love of science and bioinformatics come from? How the heck did you end up in this field? Why programming and scripting ?

2. What is your plan for your bioinformatics career? / How do you look at yourself in five years? / How are your personal objectives to accomplish these goals / What are the plan for your research fundings ?

Your CV/resume has already impressed the selection panel if you have been invited for an interview. The questions from the bioinformatics interview team provide an incentive for you to market yourself and illustrate the work in question with the most appropriate knowledge.

3. What do you understand about the job description/What would your suggested research path be if you were a successful candidate?
Summarize the specifics of the advertised bioinformatics position in your own words. Follow on with some suggestions of how you want to extend your research and create your own projects within the community.

4. Will you work as a group or do you want to work on your own?
This requirement can vary from jobs to job, so when addressing, be alert. A company/research PI may need a bioinformatician that is able to work on a single project autonomously, or they may need a person who can help direct and organize a team. In your response, refer to the job description.

5. What particular methods have you used to date with your experiments?
You might have experience with all the laboratory techniques described in the job description, but stress the ones you highly experienced with. Highlight your professional abilities and stress that you are extremely capable of mastering new techniques with others ...

At the end of the day, remember that you're questioning the jury as well as they're interviewing you. You will ought to think of any questions you would like the interview panel to pose. This indicates that you have done your homework and serious about the position.

All the best for your future job interview.

The First time when you login to the remotehost from a localhost, it will display the host key not found message and you can give “yes” to continue. The host key of the remote host will be added under .ssh2/hostkeys directory of your home directory, as shown below.

localhost$ ssh -l jit remotehost.example.com

jit@remotehost.example.com password:

remotehost.example.com$

The Second time when you login to the remote host from the localhost, it will prompt only for the password as the remote host key is already added to the known hosts list of the ssh client.

localhost$ ssh -l jit remotehost.example.com
jit@remotehost.example.com password:
remotehost.example.com$

For some reason, if the host key of the remote host is changed after you logged in for the first time, you may get a warning message as shown below. This could be because of various reasons such as 1) Sysadmin upgraded/reinstalled the SSH server on the remote host 2) someone is doing malicious activity etc., The best possible action to take before saying “yes” to the message below, is to call your sysadmin and identify why you got the host key changed message and verify whether it is the correct host key or not.

localhost$ ssh -l jit remotehost.example.com

jit @remotehost.example.com's password:
remotehost$

4. Debug SSH Client:

Sometimes it is necessary to view debug messages to troubleshoot any SSH connection issues. For this purpose, pass -v (lowercase v) option to the ssh as shown below.

Example without debug message:

        localhost$ ssh -l jit remotehost.example.com
        warning: Connecting to remotehost.example.com failed: No address associated to the name
        localhost$

Example with debug message:

        locaclhost$ ssh -v -l jit remotehost.example.com
        debug: SshConfig/sshconfig.c:2838/ssh2_parse_config_ext: Metaconfig parsing stopped at line 3.
        debug: SshConfig/sshconfig.c:637/ssh_config_set_param_verbose: Setting variable 'VerboseMode' to 'FALSE'.
        debug: SshConfig/sshconfig.c:3130/ssh_config_read_file_ext: Read 17 params from config file.
        debug: Ssh2/ssh2.c:1707/main: User config file not found, using defaults. (Looked for '/home/jit/.ssh2/ssh2_config')
        debug: Connecting to remotehost.example.com, port 22... (SOCKS not used)
        warning: Connecting to remotehost.example.com failed: No address associated to

5. Escape Character: (Toggle SSH session, SSH session statistics etc.)

Escape character ~ get’s SSH clients attention and the character following the ~ determines the escape command.
Toggle SSH Session: When you’ve logged on to the remotehost using ssh from the localhost, you may want to come back to the localhost to perform some activity and go back to remote host again. In this case, you don’t need to disconnect the ssh session to the remote host. Instead follow the steps below.

i. Login to remotehost from localhost: localhost$ssh -l jit remotehost
ii. Now you are connected to the remotehost: remotehost$
iii. To come back to the localhost temporarily, type the escape character ~ and Control-Z. When you type ~ you will not see that immediately on the screen until you press and press enter. So, on the remotehost in a new line enter the following key strokes for the below to work: ~

    remotehost$ ~^Z
    [1]+  Stopped                 ssh -l jit remotehost
    localhost$

iv. Now you are back to the localhost and the ssh remotehost client session runs as a typical unix background job, which you can check as shown below:

    localhost$ jobs
    [1]+  Stopped                 ssh -l jit remotehost

v. You can go back to the remote host ssh without entering the password again by bringing the background ssh remotehost session job to foreground on the localhost

    localhost$ fg %1
    ssh -l jit remotehost
    remotehost$

Bioinformatics

High-throughput and high-dimensional data analysis

Microbiome data analysis (Main focus)

Next-generation and third-generation sequencing data analysis for genomics

Gene expression data analysis

Machine learning for biological data

Biomarkers identification

Database and web-application for biological data

More at
https://sites.google.com/mail.kmutt.ac.th/kanthida-k/home?authuser=0

Address of the bookmark: https://www.biostarhandbook.com/

Personal Genome Variation: SVs
Human Genome Annotation: Processing Next-Gen Sequencing Data
Comparative Genomics: Pseudogenes as Molecular Fossils
Protein Structure and Function: Macromolecular Motions
Analysis of Diverse Networks
Genomics at the Forefront of Data Science

Lab page: http://www.gersteinlab.org/

https://bioalgorithms.ucsd.edu/research4.html

Why Bioinformatics Matters More Than Ever

Every day, our world generates massive amounts of biological data—from genome sequences to microbiome profiles to real-time pathogen surveillance. Hidden within these datasets are the answers to some of the greatest challenges humanity faces: emerging diseases, antimicrobial resistance, environmental stress, genetic disorders, sustainable agriculture, and more.

Bioinformatics isn’t just a skill.
It’s the language of the future of biology.

By mastering it, you give yourself the power to:

Decode genomes and understand life at its most fundamental level

Identify patterns no microscope could ever reveal

Predict disease outbreaks before they occur

Accelerate drug discovery with computational precision

Contribute to open-source tools that empower scientists worldwide

You don’t just follow science—you drive it.

Every Expert Was Once a Beginner

Many newcomers feel intimidated. Command-line interfaces. R scripts. Python packages. Next-generation sequencing data. Complex machine learning models.

But here’s the truth: every bioinformatician started exactly where you are now—curious, unsure, but excited.

No one writes perfect code on day one.

No one understands genomics pipelines immediately.

What makes you a bioinformatician is not perfection, but perseverance.

When your script throws a cryptic error…
When your data refuses to format…
When your pipeline runs for 6 hours only to crash…

Remember: this is part of the journey.
Every error teaches you. Every retry strengthens you. Every breakthrough energizes you.

Bioinformatics Is Not Just a Career—It’s a Mindset

It’s the mindset of:

Problem-solving.

Continuous learning.

Turning chaos into clarity.

Seeing what others can’t.

Bioinformaticians are detectives of biological complexity. You sit at the intersection of innovation, using tools that can shape public health, medicine, agriculture, and ecology. Few fields give you such direct impact on the world.

Your Contribution Matters

As you work on your script, pipeline, genome, or model, remember:

Somewhere, your analysis might contribute to:

A new therapy

A faster diagnostic test

A better understanding of a pathogen

A more resilient crop

An open-source dataset that helps thousands

A discovery that rewrites textbooks

Your code may be small, but its ripple effect is powerful.

The Future Is Bioinformatics—And You Are Part of It

The world is shifting. Wet labs are integrating AI. Hospitals rely on genomic insights. Farmers use gene-level predictions. Governments monitor disease in real time. Students launch pipelines that become global tools.

This is a golden era—and you are not late.
You are exactly where you need to be.

Keep Pushing. Keep Learning. Keep Discovering.

Bioinformatics is a journey filled with challenges, but also with unmatched rewards.

So the next time you feel stuck, frustrated, or overwhelmed, remember:
You’re building the science of tomorrow.

Be proud. Stay curious. Keep going.
Your work matters more than you think.