?

Log in

No account? Create an account

Previous Entry | Next Entry

Sep. 3rd, 2005

I had lunch with a friend of mine yesterday to talk about job searching, startups, etc. One thing she suggested is that I might be applying for the wrong types of jobs. She suggested that I apply for project management jobs, even though I've never had a project management title. I actually have applied for some jobs like that, but haven't gotten any interviews or even phone screens. I get more responses for software engineering jobs.

I think it will be somewhat of a stretch to make myself look like a strong candidate for a project management job. It's been a long time since I've had anything remotely resembling project management responsibility. I had some at SRI, a bit more at TIS (but I declined taking on the role formally because I didn't feel I could handle the politics and my technical responsibilities), and some at AV. (I might have been promoted and had people reporting to me who actually did the development of the log processing code, but the management that was interested in promoting me was replaced when Compaq took over. Shortly after, I was moved out of (what was) site ops into (what became) business ops, which is about the time I sensed that my career was starting to decline.)

My friend also suggested that I take some project management classes at Stanford. In general, I don't think this sort of thing is relevant to today's tech company. Maybe for very large (bureaucratic) companies, but not the fast-moving types of companies that are prominent today. She actually started getting agitated when I said that I would prefer to go to my chorus' first rehearsal instead of attending one of the fast track talks. Honestly, I don't think I would learn anything at the talks that I can't learn from reading about it in books or on the web. Furthermore, the first rehearsal is important because music is passed out that night, music dues are paid for, some Board-related business may be discussed, etc. It sets the tone for the quarter. And frankly, I just get a lot of satisfaction from participating in my chorus. I feel like my efforts are noticed and appreciated. I can see my efforts reflected in how many people turn out for the concerts; how appreciative our French guests are; how the chorus is improving, etc. So I feel justified in wanting to attend the rehearsal. Anyway, I was taken aback by how agitated she got; it wasn't as if I was demanding that she give me advice or solutions; in fact, I was just sort of looking for ideas. As it turns out, she has some issues with being out of work, feeling passed over, etc.

Maybe I have just hit the glass ceiling in my software engineering career. It's possible my friend has hit the glass ceiling as well, as a lot of what she says reminds me of women I have known who've expressed similar frustrations trying to take their careers beyond a certain point.

Comments

gconnor
Sep. 4th, 2005 01:53 am (UTC)
As far as project management, I suggest looking up Manny Ventura from our AV days (now at Y I think) -- and asking him some key questions about project management and what skills and experience people look for in that area. Or phone up David B. and ask the same questions.

I've been on both sides of interviews. When I am being interviewed, I'm being alert to the technical details, but I'm also using it as a tool to "sell myself" on a subjective level. I love talking about myself, and I am very good at reading people and I can shift gears if I sense that the person I'm talking to is not having a good time.

Usually when I am interviewing someone else, I don't usually bring technical questions, because technical prowess is not the most important thing to me. When I am considering 5 or so candidates that have "similar" experience and skills, I'm not going to be looking for someone who has the very best experience and skills -- usually they all meet the minimal and recommended requirements before getting to the interview stage. What I'm really going to look for are signs that the candidate is somewhat passionate about the subject area, and has some pride in his work. So, I usually ask something a bit vague like "Give me an example of when you had a conflict with someone over work and how you handled it" or something that gets them to talk about a specific experience.

Interviewing is a really subjective thing, and people tend to do it way differently, so I don't think any one piece of advice is really the best -- if I had to choose only one piece of advice, it's "keep going to them" because doing lots of interviews is a good way to get better at them. If you don't feel very comfortable talking about yourself, practice, practice, practice.
gregbo
Sep. 4th, 2005 03:02 am (UTC)
I pretty much understand what David B. and Manny do, based on attending ops-swat meetings, etc. I actually had an interview at Y! sometime last year for a position similar to Manny's. I didn't get the job. That sort of thing really isn't my area of expertise anyway, so it doesn't really surprise me that I would be turned down for such a job.

If I've been giving the impression that I'm having trouble talking about myself, that wasn't my intent. I don't think that's the problem. I'd say based on what's happened so far, on the interviews, I rank as strong (but not one of the strongest candidates) based on questions that are asked that I have to recall from memory. If it was a work situation, I would rank as excellent because it wouldn't be necessary for me to memorize everything. If I needed to consult a man page or book, no one would care (and possibly not even know). There is also the possibility that I am just not a good fit for the positions I interviewed for, regardless of skills (demonstrated or otherwise).

What I'd really like to know is how I differ from the people who actually got the positions I was turned down for.

gconnor
Sep. 4th, 2005 06:32 am (UTC)
If I've been giving the impression that I'm having trouble talking about myself, that wasn't my intent.

No, that wasn't a reference to you specifically, just that talking about myself is something that I happen to do well. I think based on the times I have talked to you, you are comfortable talking about yourself. You are sort of shy, but not to the point of hampering your ability to communicate.

If you are going to interviews where you get a LOT of technical questions, my observations probably won't help much, because you're probably in a different league altogether. Most interviews that I can remember have had one or two technical questions and the rest were in the "talking about myself" category. For the types of interviews I usually do, my goal walking into it is to broadcast confidence, excitement about the job, and pride in my previous accomplishments, but in a highly-technical interview you probably have a slightly different agenda.

Good luck!
gregbo
Sep. 4th, 2005 05:43 pm (UTC)
Hmmm ... I would've thought you'd had more technical questions. You interviewed at several places I interviewed at (e.g. G, Y!) for similar types of jobs (e.g. people on Y!'s Abuse team interact with sysadmins regularly, and several people in that group were sysadmins in previous jobs). Even space_parasite had a fair amount of technical questions, especially at G.

Latest Month

July 2018
S M T W T F S
1234567
891011121314
15161718192021
22232425262728
293031    

Page Summary

Powered by LiveJournal.com
Designed by Tiffany Chow