The Q and A

On 4 February I wrote that the day before I had walked to Hayes Valley. I thought I had left early but by the time I got to the cafe I realized I had not.  Many people were converging on the courtyard room when I arrived and I noted that by the time The project manager had returned from his desk with the meeting code the seats beside me had been filled.

The manager did a quick intro for the modeling group and noted there was as of yet three jobs to fill. After this the data manager spoke. I noted that her presentation with significant of a more qualitative discourse. I noted that it was similar to my research in fact. She began to describe the structure of the databases she needed to build and it became clear that my skills would be useful to her.

When the Q and A started there were a lot of questions. Notably a man wanted to know if his existing data bases would be affected.  The data manager said that they wouldn't be.  Another person asked if they had started with the questions. The data manager was very apologetic at this point because her sample had not taken in everyone and the project manager cut in to make that clear.

After this the modeling manager started describing his relationship with a contracting agency. He described modeling processes. I had received an email at this point about a job so I composed an email back using an old resume. I wasn't certain how useful that would be but she didn't reply.

The administrator had come in by this point and I noted that she had seen me. I tried to follow the modeling manager but the thread was lost. There were a lot of people asking pertinent questions about the programs. I wasn't certain who they were and what they did.

There was a break and I spoke to the lady beside me. She wanted to know how I had ended up at the discussion. I described my skill set and explained how I had met one of the analysts at the agency.

When the discussion began again the lead developer was talking. He explained what python was and how it differed from a spreadsheet solution. Then he explained what it was capable of doing using an example project.

He described 35 years worth of data and processes and then explained how he made a script to do the process and presented the results.  When he finished it was clear that the people who benefited from that process liked it very much. However everyone else thought that it needed to change. I thought this was ironic because it was clearly a proof.

The questions went on and on but the administrator cut it short. I then tried to talk to the project manager but ended up with the modeling manager. He was very open but acted like my interaction was unusual. I also tried to engage the data manager then. She was with the administrator who introduced me to the project manager and everyone else.

The consensus was that I should spend some time interacting with all four people in the group over the next week or two. I noted that I was very appreciate of of this. The developer said I should email him and the project manager said he remembered me.  The administrator said it was likely going to be a few months before anything was decided regarding jobs. However, it felt like my rating was going to make me good fit for any opening.

Later I went to the bar for their happy hour. Once I was there the project manager waved at me. I sat initially with the modeling manager but ended up talking with the data manager. Her team had only existed for a short time. She had spent 20 years working in industry. We discussed methodology and general ideas before I decided I was dragging.

I spoke to the lead developer when I went for another beer. At the bar I just accepted that this was just my lot so returned and sat across from the modeling manager and his coworker. It was awkward then but things were winding down. I made ready to go and said bye to everyone.

This series of experiences are ideas and memos I have written down about my career or job interests. This Notes Series is meant to describe in brief my epiphanies, discoveries or simply encounters for future reference.